2.01-01 Naming Convention
As short as is practical. Use Alpha numeric to help identify modules from long names. There is no need to prefix modules in line with DISCO. It is better to align them with functional areas Exception: 2.01-01a Space saving for User Facing Modules: User facing modules can be renamed to a more descriptive name if required to…
2.02-01 Nested IFs
Avoid using multiple IFs. It is better to split the formula into more line items, use LOOKUPs or alternative constructs Best Practices article: Line Item Subsets Demystified Decreasing the Length of Your Formulas Questions on this topic? See 2.02-01 Nested IFs in our Planual forum.
2.03-01 Turn Summary options off by default
Most line items in the model will not need summary calculations, so it is good practice to turn summaries off initially and add then back when necessary. This is especially true for Calculation modules and conditional formatting line items Exception: 2.03-01a User facing modules on dashboards: For Input or Output modules,…
2.04-01 Naming convention
Give the view a meaningful name (e.g. Dashboard Grid, Filtered View, Export etc.) There is no need to add the module name within the name of the view Best Practice article: Naming Convention Questions on this topic? See 2.04-01 Naming convention in our Planual forum.
2.01-02 Functional Areas
Use functional areas to categorise modules Questions on this topic? See 2.01-02 Functional Areas in our Planual forum.
2.02-02 < 12 expressions in a formula
If it takes you longer than one simple sentence to describe what the formula is doing, it is probably too long. Try not to mix expressions Questions on this topic? See 2.02-02 < 12 expressions in a formula in our Planual forum.
2.03-02 Try not to use TEXT as a format, or limit it as much as possible
Anaplan (as with computers in general) is optimized for numbers and Booleans. Text formats use more memory than any other format due to the way computers need to store the data. Minimize the use of text if possible. Set to BLANK rather than leave empty or invalid text. Related to Rule: 2.02-04 Text Strings Questions on…
2.04-02 Filtering on views
Filter on a Boolean and only have one filter per dimensional tab Related to Rule: 4.03-01 Use efficient filters Best Practice article: Filter Best Practice Questions on this topic? See 2.04-02 Filtering on views in our Planual forum.
2.01-03 Add "Dummy" Modules as Separators
Use these to provide sections and ordering to the Modules list, but don't use Emojis Related to Rule: 1.08-01 Don't use Emojis Questions on this topic? See 2.01-03 Add "Dummy" Modules as Separators in our Planual forum.
2.02-03 No Repeated expressions
If the expression is repeated in the formula (or other modules), put it on a separate line item. “Calculate once, reference many times” Questions on this topic? See 2.02-03 No Repeated expressions in our Planual forum.