-
1.05-11 Do not embed Numeric values or Dates within the Code of a list
Dates and values are "data" and should not be part of a code. Adding these elements to the code will in most cases, vastly increase the size of the list and consequently increase the mode size and reduce performance Best Practices article: Data Hubs Purpose and Peak Performance Questions on this topic? See 1.05-11 Do not…
-
1.05-12 Use formulas to derive properties of the list
Based off the code of the list it should be possible to derive the attributes; Calculating the values is more efficient than storing text fields Best Practices article: Data Hubs Purpose and Peak Performance Questions on this topic? See 1.05-12 Use formulas to derive properties of the list in our Planual forum.
-
1.05-13 Use Flat lists to store Metadata (in a system module)
Avoid having hierarchies in Data Hub; these should only be applicable to the main planning models Related Rule: 5.07-01 No Hierarchies Questions on this topic? See 1.05-13 Use Flat lists to store Metadata (in a system module) in our Planual forum.