1.05-11 Do not embed Numeric values or Dates within the Code of a list

rob_marshall

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

Misbah

Rule 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

Here is how it was done in Pre Planual Era.

What is wrong with this method? Dates and Values are data points and should never go to the list as part of the code. If you do imagine the number of keys that get inserted within the list and also you will have to add two more line item to store these two data points and then aggregate it based on these two items which is cumbersome, performance degrading and ineffective.

Here is how it should be done in Planual Way: Make the key without Dates and Values.

Once the key is created within Anaplan, load the values directly into the module on Time dimension