Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Using the Portfolio Data Center, you may want to create a field attribute for this characteristic. This can make it easier to add it to the required fund (entity) policy. The following figure shows example of a field that can be used for this purpose. Note that the Table is set to ENTITY_EXTENSION. You do not have to set this to ENTITY_EXTENSION_HIST in order to maintain entity history.
Image Removed
AnchorRTF350031003100320033003a00RTF350031003100320033003a00Figure : New Regular Field Screen
New Regular Field ScreenImage Added

After you build this field you may have to synchronize the metadata in the inventory of fields for the ENTITY_EXTENSION table. The necessary configuration is shown in the following figure. Image Removed
Anchor

RTF370037003300310032003a00RTF370037003300310032003a00Figure : Edit Pace Inventory Field ScreenEdit Pace Inventory Field ScreenImage Added

Once the field is created and the inventory of fields is set, you are able to easily add the field to the required fund policy.

Because performance reports default to using entity history, Eagle recommends setting the relationship as of the inception date of the "convert from" fund.

Open the fund details (in Portfolio Data Center) then set the date range to have a start date that coincides with the class's inception date (in order to display all history record since inception). If the Conversion parent is not set, create an override and set the value to the convertible parent entity id. Then set the start date to the inception date of the fund and the end date to current date. Click save (to save the override) then click submit to process the override request.

...


Info

Only convertible funds need this setting applied.

...