-
1.08-01 Don't use Emojis
Don't use Emoji or symbols in any naming of lists, modules, line items, or actions. They can cause issues with integration and different browsers Exception: 1.08-01a Placeholders: It is OK to use Emojis or symbols for placeholders in General Lists, Module Names, Functional Areas etc. Questions on this topic? See 1.08-01…
-
1.07-01 Naming Convention
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 Related to Rule: 1.08-01 Don't use Emojis Best Practices article: Good Practice Naming Conventions Questions on this topic? See 1.07-01 Naming…
-
1.06-01 Naming convention
Prefix the subset with the name of the list (e.g. P3 Products: Active Products) Related to Rule: 1.08-01 Don't use Emojis Best Practices article: Good Practice Naming Conventions Questions on this topic? See 1.06-01 Naming convention in our Planual forum.
-
1.01-01 Never use SELECT with Time
New! The Planual can now be found on the Anaplan Support site. We will be transitioning it off Community in the coming months. 1.01-01 Never use SELECT with Time This goes against the Sustainable element of PLANS and the hard coding can cause issues when updating the timescales of the model. Modules with Time formatted…
-
1.05-01 Naming Convention
Hierarchies should be prefixed with a letter signifying the name of the hierarchy and a number indicating the level. e.g. P1 Product Category, P2 Product Family, P3 Products. The is no need to add "L" as a prefix to lists Related to Rule: 1.08-01 Don't use Emojis Best Practices article: Good Practice Naming Conventions…
-
1.02-01 Use "Current" in Version settings
Utilising the Current (and Actual) check box within the Version Settings allows the use of CURRENTVERSION() and ACTUALVERSION() in calculations, in SELECT statements and ISCURRENTVERSION and ISACTUALVERSION() for Boolean checks. Current version also acts like a top level for Versions; if you have a source module with…
-
1.04-01 Keep modules hidden for end users’ roles
Users should only be entering data through dashboards, so remove Modules from the contents panel Questions on this topic? See 1.04-01 Keep modules hidden for end users’ roles in our Planual forum.
-
1.03-01 Only give write access to lists when needed
Unless the end users need to edit the members of the list (e.g. add, delete), access does not need to be set. Adding roles to lists increases the memory usage, so only use when necessary. A user can edit data in a module without needing to have access to the list Best Practice article: Pre-Allocation in Lists (and Impacts…
-
1.05-02 Always use a code
Using codes is more efficient for loading and using lists so strive to always have a code for lists. This is especially important for numbered lists Exception: 1.05-02a Static non hierarchy lists: For simple static lists (such as Yes/No) it is OK not to have a code, but even then, Y and N can be used as codes Related to…
-
1.07-02 Line Item subsets for Version Formula
Use Line Item subsets to create different numeric formulae for each version to avoid multiple Ifs Best Practice article: Line Item Subsets Demystified Decreasing the Length of Your Formulas Variance Analysis With Native Versions Made Easy Questions on this topic? See 1.07-02 Line Item subsets for Version Formula in our…