[ABUSE] By: Parthpanchal / Board: ASForums (104)

jamietgwang

irrelevant link - looks like advertisement

Link to post:
(pointers and hints for reducing hardcoding?)

by Parthpanchal

https://community.anaplan.com/t5/Administration-and-Security/pointers-and-hints-for-reducing-hardcoding/m-p/37252#M104

<p>I got here throughout a large model lately in which Time (years), version, and list individuals are hardcoded in lots of locations (formulas, filters, mappings, ...). every year quit, the admin has to move on a look for those hardcoded years and replace the model. versions of forecasts / budgets are a bit much less complicated when you consider that one version may be tagged as energetic, but exchange from prior forecast may additionally nonetheless be calculated with hardcoding. Hardcoding of listing gadgets seems to depend on how dynamically rapid-converting that list is probably and the way close the member is to the "trunk of the tree" - leaf individuals are more likely to exchange whilst such things as division or Product institution are much less susceptible to trade.</p><p>A "Variables" module with modern yr, earlier year, subsequent year, earlier Forecast, and so on. might centralize quite a few that. but is that practical in general?</p><p>What are your mind? Do you obviously include a "Variables" module on your fashions? should that be promoted as a exceptional practice?</p>

This message has 0 replies