-
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 items to be used as sums and lookup are the better option Exception: 1.01-01a Generic Time periods: It is OK to use SELECT with Generic Time periods such as Actual…
-
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.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.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.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.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.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.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.01-02 Use the Model Calendar by default
As the Model Calendar is dynamic, there are a lot of advantages in using it for the majority of modules. Choose suitable time settings (past and future years) that cover most of the requirements and use the model calendar to set these in the most part. For the exceptions outside of the “norm” use time ranges for efficiency…
-
1.02-02 Do not use formulas in the version settings
Whilst this is a simple construct and it might be OK for simple models; it effectively adds size to models every time versions are used in a module even if you don't want the variance. Also, in modules with 3 or more dimensions if you have calculation line items and aggregations the results may not always be give the…
