![](\"\/extraview-media\/images\/ag\/fields_and_layouts\/data_dictionary_tabs3.png\")
<\/p>\nThe Data Dictionary is the central place where all field definitions are stored and maintained. The data dictionary is found within the System Configuration administrative menu.<\/p>\n
<\/p>\n
Data Dictionary screen tabs<\/span><\/p>\n These are the fields within ExtraView that are used within all processes. There are two types of fields, built-in fields and users defined fields (UDF\u2019s). Built-in fields are provided as part of all ExtraView installations. Although you may modify various attributes of built-in fields, such as their title and their default value, you should never delete an built-in field. You may create as many UDF\u2019s as you require for your installation. There is no limit on the number of UDF\u2019s that may be created. All fields have four basic properties, their scope, a fixed name, a title and a display type. It is the display type<\/p>\n that gives a field most of its functionality. See later in this section for a complete explanation of all the field types. Once any UDF is defined in the data dictionary it will behave the same as if it were an inbuilt field. You will be able to attach permissions to the field, place it on any layout, report on the field, etc. End users will not be able to detect the difference between an inbuilt field and a UDF. When viewing a list of fields in the data dictionary, you will only see the fields in the Business Areas and Projects to which you have permission. This typically includes all the fields which are global in their scope.<\/p>\n As a technical point, there is no real limit to the number of UDF\u2019s you create. In addition, creating a UDF does not result in any change to the underlying database schema. There is no system degradation in creating a large number of UDF\u2019s.<\/p>\n Expression fields are used in reporting to derive or calculate the value of a reporting column. Each expression may have a default expression which is then automatically used on any report which contains the expression field. Expression fields also have a range of display types, although this range is more limited than a field display type. You may define any number of additional expression fields, or reuse the same expression fields for different purposes on different reports.<\/p>\n This section is where field screen elements that are not database fields can be defined or altered. Buttons for menubars are also maintained within this tab. Once again, it is unlikely that the administrator will remove fields from this section. Labels can also be added as User Defined Fields, so it is unlikely that the administrator will add new fields to this section of the data dictionary.<\/p>\n These fields are for the inbuilt screens within ExtraView. A few additional supporting fields in this area affect screen displays. Administrators should not need to add or remove entries from this section, but can rename the individual screens within their installation.<\/p>\n Fields found in this area pertain to options having to do with the user\u2019s current, active ExtraView session. Fields defined in this section are principally used in reporting<\/p>\n This is an informational section which displays the names of fields which are used internally within the ExtraView software. These names may not be used as User Defined Field names.<\/p>\n These fields generally are those that manage functions involving calculations of some kind, such as the internal data\/time stamping functionality.<\/p>\n This core component of ExtraView controls many of the attributes of each field, such as:<\/p>\n It is often useful for the administrator to document the purpose of any field within their system. To achieve this, add a global attribute to any field, with the type of ADMIN_NOTES. The text entered within this field is not utilized outside the data dictionary, but serves as documentation regarding that field. This text is also visible within the design center when a field is placed on a layout. It can be viewed within the Cell Attributes section of the screen.<\/p>\n Note that if you want to view where a field is used within the overall system, you can use the Where Used<\/strong> tab within the data dictionary.<\/p>\n","protected":false},"excerpt":{"rendered":" The Data Dictionary is the central place where all field definitions are stored and maintained. The data dictionary is found within the System Configuration administrative menu. Data Dictionary screen tabs Fields These are the fields within ExtraView that are used within all processes. There are two types of fields, built-in fields and users defined fields…<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_lmt_disableupdate":"","_lmt_disable":"","_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"class_list":["post-22164","page","type-page","status-publish","hentry"],"acf":[],"yoast_head":"\n\n\tFields<\/h3>\n
\n\tExpressions<\/h3>\n
\n\tLabels \/ Buttons<\/h3>\n
\n\tScreens<\/h3>\n
\n\tSession Variables<\/h3>\n
\n\tReserved Field Names<\/h3>\n
\n\tSpecial Variables<\/h3>\n
\n\tKey Uses of the Data Dictionary<\/h3>\n
\n
\n\tDocumenting the Purpose and Use of Fields<\/h3>\n