-
5.07-01 No Hierarchies
There should be no need for composite list hierarchies in the Hub. They can be built to "test" the actions, but after testing they should be deleted Exceptions: 5.07-01a Validation purposes: If data is needed to be consolidated to check against source systems, although the flat modules with attributes can be used to sum…
-
5.02-01 Naming Convention
Use "friendly" names for user facing processes. For data hubs or administrative processes use numeric prefixes to signify the order of the processes Related to Rule: 5.01-01 Naming Convention Best Practice article: Naming Convention Questions on this topic? See 5.02-01 Naming Convention in our Planual forum.
-
5.06-01 Naming Convention
Rename the import sources as soon as possible. For a saved view include the module name (e.g. module.saved view). For model imports, include a shorted version of the model name (e.g. model_module.saved view) Best Practice article: Naming Convention Questions on this topic? See 5.06-01 Naming Convention in our Planual forum.
-
5.03-01 Remove unwanted sources
For one off imports, or when source models are no longer required, delete the source model to keep the list tidy Questions on this topic? See 5.03-01 Remove unwanted sources in our Planual forum.
-
5.04-01 From source system, create a code defining all attributes
Ideally, this would be a separate file that is unique vs. using the same file for the transactional load Exception: 5.04-01a Code is >60 characters: If the code is >60 characters, you will have to use combination of properties Related to Rule: 5.04-02 Create separate files for attributes and data Best Practice article:…
-
5.05-01 Naming Convention
Keep it simple. Export, Build etc. There is no need to include the module name in the view name Best Practice article: Naming Convention Questions on this topic? See 5.05-01 Naming Convention in our Planual forum.
-
5.01-01 Naming Convention
New! The Planual can now be found on the Anaplan Support site. We will be transitioning it off Community in the coming months. 5.01-01 Naming Convention Use numeric prefixes to signify the order within the process (e.g. 1.1 Import Products, 1.2 Import Product details). There is no need to include the technical module name…
-
5.01-02 User Facing Actions in a process
Import and Export actions need to be republished if modified or replaced, whereas Process Actions are always consistent with whatever is held within the Process, making management easier Exception: 5.01-02a Numbered list actions: Actions involving numbered lists (Create, Assign, Copy Branch and Delete Branch) cannot be…
-
5.07-02 No Analytical modules
Try and keep Analytical modules out of the Hub Questions on this topic? See 5.07-02 No Analytical modules in our Planual forum.
-
5.06-02 Delete unwanted sources
For one off imports, or when import sources are no longer required, delete the sources to keep the source list tidy Questions on this topic? See 5.06-02 Delete unwanted sources in our Planual forum.