Is it possible to lock a slice of a few cubes of data within Contributor using Macros?
I am working a monthly forecast process with a version for each month (1+11, 2+10, 3+9 etc.) and want to make sure that the prior forecast cannot be changed, either through data entry or d-links. The data entry part can be covered through access tables, but not the d-links.
Since this is undoubtedly a common situation, I figured someone out there has already mastered this challenge!
Briana Connell
No way to stop dlinks in Contributor.
Insert Allocation cubes in links and change them, so that your previous forecast becomes unmatched (if this a time-based rule, use @Time to automate it)