Guidelines

When doing ETL in the customer spaces, these rules are applicable for the components that you want to import through a package into the Consumer space:

Aggregates

Infor-provided aggregates are in a model space and brought into the consumer space with a package. Do not modify Infor-provided aggregates. With the appropriate Birst license, you can create aggregates in a customer created space. Import a package from a model space and create the aggregate. Create a package with your new aggregate and import that package into the consumer space.

The custom aggregate name should not start with LN.

Note: If Infor provides changes to the model spaces, the changes may break any customer created aggregates. Managing aggregates is an advanced task that requires considerable testing and ongoing monitoring to ensure that they are built properly.

Analyze By Date

Customers should restrict the use of Analyze By Date as it impacts report performance. Analyze By Date-enabled columns should not have a four-character long prefix such as abcd Date. Instead, use a prefix with a maximum of two or three characters or do not use a prefix at all

Custom Attributes

Customer-created custom attributes should be created only on new customer dimensions. The custom attributes are automatically added to the package when the new customer dimension is selected.

Custom Measures

Customer-created custom measures should be created only on new fact tables. The custom measures are automatically added to the package when the new customer fact table is selected.

Custom Subject Areas

Customers should not create custom subject areas in their customer-created spaces. Instead, create the custom subject area in the consumer space.

Hierarchies

Customer-created dimensions should be unique. For example, start your own hierarchy name with your company name or an abbreviation of your company name. This prevents naming conflicts when the dimension is imported into the Consumer space.

Measures

Customer-created measures should not have a four character long prefix such as column abcd Amount. Instead, use a prefix with a maximum of two or three characters or do not use a prefix at all.

Packages

Customer-created packages coming from an extension or customer managed space can be imported into the consumer space. These package names should not start with ‘LN’.

Customers can reuse dimensions and fact tables from the LN extraction and model spaces. From the extraction space, use the LN Tables – Extensibility package for handling table sharing. From the model spaces, use only the packages that end with ‘- Consumer’ as these packages remain stable over releases. To have access to the packages. you must be a member of the LNBIRST-Model-Administrator space group of the extraction and model spaces.

Scripts/Sources

Logical fact table names are based on the script names and should be unique. For example, start your own hierarchy name with your company name or an abbreviation of your company name.

Variables

Customer-created variable names should not start with ‘LN’.