Line Item Subsets

Planual Rules regarding Line Item Subsets in the Polaris engine

Note: Rule numbers on this page may not be sequential. Our Planual uses a common index across Classic Hyperblock and Polaris Engines, which means some rules only appear on one page or may have been removed.

Prefix with LIS then a description or the module used in the Line Item Subset. For Line item subsets using multiple modules, use a generic name that best describes its purpose

Good Practice Naming Conventions

Use Line Item subsets to create different numeric formulae for each version to avoid multiple IF statements.

Line Item Subsets Demystified
Decreasing the Length of your Formulas
Variance Analysis with Native Versions made easy

By default, you should keep summaries turned off on line items using the Collect() function. By having summaries turned on, the system is aggregating data that isn't usually needed.

Line item subsets work well in Polaris when kept lean and purposeful. Model performance degrades progressively as a line item subset grows, so keep them as small as required. Use iterative development to test your subsets often with real data, not just sample data. This will help you spot problems before they happen in production. Also note that simply creating a line item subset consumes workspace allowance, even if no module uses it. Only create and retain the subsets your model strictly needs.

_{Engine Applicability: Polaris only}