...

1. From the General Reporting module, select the report type you want to use in the Grouping Rules folder in tree view.

   Image RemovedImage Added

2. Right-click and select New.
   You see the New Range Grouping Rule dialog box.

3. In the Name field, enter a name for the rule.

4. In the Comments field, enter an optional comment about the rule.

5. Click to populate the field details with the Quartile Rank field.

6. Double-click the text box under Range Title, and enter Rank 1

7. Double-click the text box under Range, select the = operator and enter the value 1.

8. Repeat steps 6 and 7 for the remaining three ranks, Rank 2, Rank 3, and Rank 4.
   You see the Edit Range Grouping dialog box displaying the new range grouping rule.

   Image RemovedImage Added

The following example shows a sample report with range grouping in place.

...

...

1. To access the Time Series Field dialog box, open the Custom folder, located on the Field Selector window.

2. Open the Time Series folder on the Field Selector window.
   You see the Time Series field dialog box.

The Times Series Fields dialog box contains the following fields and options:

...

1. Image Added

2. Complete the following options on the Time Series Field dialog box and click OK.

...

Time Series

...

Click OK to save your changes.

...

Fields Restrictions Per-Share Data

Times Series

Note that some of your analytical data fields may not be appropriate candidates for Eagle's time series fields. These include the per-share fields for equities, such as price, earnings per share and dividend per share. This is because these fields are impacted by capital changes that companies experience, like splits and stock dividends that change the definition of a share. Eagle's prices are not adjusted for splits, and normally, security analytics are loaded as unadjusted. It is not meaningful to include both pre- and post-split data in a time series calculation. Fortunately, many important equity analytics such as beta, and financial ratios such as P/E do not have a share dimension and are unaffected by splits. The same is true of index levels, which are normally loaded as prices.

Data Mart

You may be able to obtain split-adjusted per-share data through a direct vendor load or exporter approach. If so, you can analyze that data using time series fields. However, if you want to build such fields in Data Mart, your data will reflect different share definitions every time a security has a capital change. To solve this issue, you must re-build all per-share fields, for all past dates, for every required date (perhaps only monthly depending upon reporting requirements) in order not to miss a split in any stock in the Mart. This may be facilitated by adding an extension to the Mart's Security Details table and dedicating it to your per-share fields, building only that extension since inception on a selective-fields basis.

...

Use the calculator when defining calculations for creating custom fields.

...

CalculatorUse the commands If, Then, Like, And, Or, and Null to compare two values. For example, an inference field could be: If Cost Basis is less than market value, then display Losing Money.

Supporting Nested IF Clauses

You can use ELSE and END IF statements to support nested IF clauses in Custom type fields. Using these statements in Custom fields allows you to create complex logic similar to that of standard programming practices. For example, you can create statements such as:

IF Investment Type =Fixed Income

THEN

IF Coupon <= 5

THEN Fixed Income Less Than 5

ELSE Fixed Income Over 5

END IF

ELSE

No Security

Data Mart

You may be able to obtain split-adjusted per-share data through a direct vendor load or exporter approach. If so, you can analyze that data using time series fields. However, if you want to build such fields in Data Mart, your data will reflect different share definitions every time a security has a capital change. To solve this issue, you must re-build all per-share fields, for all past dates, for every required date (perhaps only monthly depending upon reporting requirements) in order not to miss a split in any stock in the Mart. This may be facilitated by adding an extension to the Mart's Security Details table and dedicating it to your per-share fields, building only that extension since inception on a selective-fields basis.

...

Use the calculator when defining calculations for creating custom fields.

...

CalculatorUse the commands If, Then, Like, And, Or, and Null to compare two values. For example, an inference field could be: If Cost Basis is less than market value, then display Losing Money.

...

You can use ELSE and END IF statements to support nested IF clauses in Custom type fields. Using these statements in Custom fields allows you to create complex logic similar to that of standard programming practices. For example, you can create statements such as:

IF Investment Type =Fixed Income

THEN

IF Coupon <= 5

THEN Fixed Income Less Than 5

ELSE Fixed Income Over 5

END IF

ELSE

No Security

END IF

...

Date and Date Part Commands

You can perform math functions on dates in reports. For example, you can calculate the number of days between the trade date and settlement date on a trades report. The detail calculation and inference fields allows you to compare two date fields using the subtraction ( - ) operator. The concentration engine calculates the difference in days.

The Date Part option lets you add days to a field and extract a month value from a field. You can also use Date Parts to display portions of the full date. For example, if a report is grouped by the month portion of the trade date value, you can create a detail calculation field that retrieves the month portion of the trade date field. You can then use the detail calculation field in the grouping rule. When you select Date Part, a window appears that allows you to decide which part to use. Options include Date, Month, and Year.

...

...

String Command

You can limit a calculation to part of a string of characters by using the string function in the detail calculation or inference fields. Eagle supports the following string manipulations:

• Right Trim. Takes a parameter for how many characters to the right. For example, if (right trim,5(Entity Name)= “HEDGE”) then Account Type = “Hedge Fund” else “Private Account.”

• Left Trim. Takes a parameter for how many characters to the left. For example, if (left trim,11(Entity Name)= “Institution”) then Account Type = “Institutional Account” else “Private Account.”

• Upper. Evaluates a string of data in all upper case regardless of the actual case of the string. For example, if (upper(security description) = “Cisco”) then (Share Par Value * 2) else Share Par Value would return the result of (Share Par Value * 2) for the string "Cisco" or for "cisco".

• Lower. Evaluates a string of data in all lower case regardless of the actual case of the string. For example, if (lower(security description) = “motorola”) then (Share Par Value * 2) else Share Par Value would return the result of (Share Par Value * 2) for the string "Motorola" or for "MOTOROLA".

• Substring. Takes a parameter for start location and stop location. For example, if (substring(Security Name,1,3 = “ADR”) then Security Type = ‘ADR’ else Security Type.

1. Click String.
   You see

...

1. the String drop-down menu.

...

1. Image Added

2. Select the string type.
   To evaluate the last letters in a value, use the right string. For use with substrings, you have to populate a start position and the number of letters to extract for the word part. For example, if you are looking for the value “Consumer Cyclicals,” you may evaluate for the word part “Cyc” by entering 10 as the start position and 3 for the number of letters to extract.

...

Other Calculator Commands

...

Entity Build Field Attributes

...

1. In a report rule, add a field that is configured with a translation code.

   Image RemovedImage Added

2. Change the sort from default to custom.

...