Entity Build Field Attributes

All entity build related field attributes are grouped under the Entity Build field category. These include field attributes defined as Entity Build and Advanced with a process of Entity build Position Table Columns.

Field Attributes Defined as Character Numeric

For any field attribute that is defined as character numeric, the OLAP engine converts the numeric value to a string, which retains the decimal precision before matching the value to the code value. The OLAP engine applies the field attribute’s precision, which is typically 0 for character numeric defined field attributes. Typically, you see this in ratings field attributes when adding a reference code to the Numerical Rating field.

On this page

Published Field Attributes

Published field attributes are available to additional report types. You can edit a published custom field attribute and select additional Report types from Make available to other Report types. These changes are saved in the database. You can also make published custom field attributes available to additional report types.

Field Attribute Mapping

Field attributes are mapped to report types. Field attributes with RPT_SUB_TYPE_INST values of zero in the REPORT_TYPE_FIELDS table of the Rules database are available for all subtypes of the corresponding report type value. The existence of these zero records has no impact on how reports run.

You can restrict certain field attribute types from certain report type and report component types. For example, you can make trades fields unavailable to Position reports, either by using the report rule or field rule maintenance window, or from the profile level filtering setting. This change prevents reporting scenarios that are known to cause either report failures or inconsistent report results.

Map Field Types

You can use the Map Field Types feature to make specific field attribute types available for various components of each report type. The scenarios and combinations which work correctly are scripted. You can apply tighter restrictions with this feature, disallowing specific scenarios that are mapped by default. You can allow additional combinations by mapping field type and report type combinations that are not mapped by default.

To open Map Field Types, right-click on the contents of the Fields folder on the Component tab and select Map Field Types.

This window has four main folders:

Fields. Used to select a specific custom field type, and specify which underlying field attribute types are included in it. For example, expand the Fields folder to display the list of custom field attributes. Select the Rollup Field type, and explode that folder to display the report types that can include rollup fields. Select the report type, such as positions single period, and use the Field Types check boxes in the right pane to select the field types that can be included in a rollup field created in a single period position report.
Others. Used to map field types for report types that do not fit into the typical structure of other report types. This folder contains the query tool.
Profiles. Maps field types to report types where the fields can be used in the profile-level filter feature. Because this filter feature, available in the Select Criteria tab in report profiles, is designed to be executed directly against the PACE report result set and is not as dynamic as the guideline filter feature, it is listed separately in the Map Field Types dialog box. The selections made to map field types to a report rule are not the same selections made to map field types to a report profile of the same report type.
Rules. Used to map field types to field rules, filter rules, range rules, and report rules. Expand the folder to display the rule types, and expand the Rule Type folder to display the report types that use the selected rule type. Select the check boxes to modify the map field types by selecting a report type. To restrict a field type from the selected rule and report type, deselect the check box next to that field type. Click OK to save any changes.

Field Type Limitations

The Cash Adjustment and Trade Adjustment custom field types have limited field types available to them by default in the Map Field Types feature. Cash Adjustment fields have only cash and security fields available in the formula editor of that field type. Trade Adjustment fields have only trade and security fields. You can override these default mappings.

Map Field Types Workflow

When you change Map Field Types settings, the change applies to all users.

If a specific field attribute was previously mapped to a report type, and that combination is later restricted by using the Map Field Types function, that field no longer appears as eligible. For example, a trades field is made available to multi period positions reports and you then use the map field types function to restrict trades fields from multi period positions report field rules. When you create a multi period positions report field rule, the Trades folder in the field attribute selector no longer appears. Those field types are no longer eligible for that component type.

If you add a trades field to a multi period positions field rule, and the map field types function is used later to restrict that combination, the trades field remains as part of the field rule created previously. Changes to the map field types settings do not impact components created and saved previously.

If a specific combination was restricted via the map field types function and you make a field attribute available to a report type that is restricted, you get a warning that you are about to map a restricted condition. You can choose to not publish the field to the restricted report type, or ignore the warning and proceed with the selected mapping. If you make the field available to more than one report type, only the restricted report types are listed in the warning message.

Map Field Types Database Information

The data that is maintained by the map field types feature is stored in primary tables:

Field Types. This table contains a record for each field attribute type in PACE, and drives the lists of field attribute types in the Map Field Types dialog box.
Context Types. This table contains information about each specific PACE reporting component type that is supported by the map field types feature.

The combinations that are mapped using the map field types feature are stored in two separate tables.

CONTEXT_REPORT_TYPES_FILTER. This table contains the relationships among report types and subtypes, and context types. This drives the folder structure that is displayed on the left side of the Map Field Types dialog box.
FIELD_TYPES_FILTER. This table contains the mappings among reports, contexts, and field types that are represented by the selected check boxes in the right half of the Map Field Types dialog box.

The full structure of these tables is shown in the tables that follow.

Field Attribute Type Table

Column	Description
INSTANCE	Unique record identifier.
FIELD_TYPE_SHORT	Short description of field attribute type.
FIELD_TYPE_LONG	Long description of field attribute type.
UPD_USER	The user who last updated the record.
UPD_DATETIME	Determines the last time the record was updated.

Component Type Table

Column	Description
INSTANCE	Unique record identifier.
CONTEXT_TYPE_SHORT	Short description of Reporting Context type.
CONTEXT_TYPE_LONG	Long description of Reporting Context type.
UPD_USER	The user who last updated the record.
UPD_DATETIME	Determines the last time the record was updated.

Field Types Filter Table in PACE Master Database

Column	Description
RPT_TYPE_INST	Unique record identifier.
RPT_SUB_TYPE_INST	Instance value from REPORT_SUB_TYPES table.
CONTEXT_INST	Instance value from CONTEXT_TYPES table.
FLD_TYPE_INST	Instance value from FIELD_TYPES table.
UPD_USER	The user who last updated the record.
UPD_DATETIME	Determines the last time the record was updated.
COLUMN_NAME	Not currently used.

Context Report Types Filter Table in PACE Master Database

Column	Description
INSTANCE	Unique record identifier.
CONTEXT_INST	Instance value from CONTEXT_TYPES table.
RPT_TYPE_INST	Instance value from REPORT_TYPES table.
RPT_SUB_TYPE_INST	Instance value from REPORT_SUB_TYPES table.
UPDATE_USER	The user who last updated the record.
UPDATE_DATE	Determines the last time the record was updated.

Custom Categories

You create custom categories for field attributes to determine how field attributes are displayed. You can organize the fields by indicator, database, table, or by category. You can also list the fields all in one folder in alphabetical order.

Complete the following procedure to create custom categories.

From any Eagle window, click the Eagle Navigator button to access the Eagle Navigator.
Enter Codes in the Start Search text box.
Click the Codes (System Management Center) link to access the Codes window.
You see the Codes window.
From the Codes module, select the Field Category Code and add new code values. The short description holds a number and the long description holds the actual description, as shown in the table that follows.
Short Description: 1 Long Description: Accounting Data
Short Description: 2 Long Description: Performance Measurement Data
Short Description: 3 Long Description: Holdings Data
Short Description: 4 Long Description: Security Master Data
Short Description: 5 Long Description: Shared Data
Open the Field Attributes module, under the Metadata category.
Assign a category to each field attribute. From the workspace, select just one grouping, or create a tree so that one grouping is designated as a main category and then one or more other categories are added as subgroups.
To customize the display, click Customize.
You see the Customize Field Grouping dialog box. Select as many groupings as you want to create the grouping tree. Click OK when done. The resulting view is displayed in all other field rules until it is changed. If a field attribute is not assigned to a category, it appears under the category Unknown.
The field rule view is saved in the registry in the section HKEY_CURRENT_USER > Software > EagleSystems > Clients > EaglePACE > Settings > FieldsCtrlGroups. Category=Setting of 1, Indicator=Setting of 3, Database=Setting of 2 and Table=Setting of 4. This registry setting applies to the user.