I am needing some clarification on how this actually works because I am seeing a behavior that, while I did not expect it, actually makes sense in a way.
Here is the scenario: We have a process that copies data from one cube to a blank copy of that cube, the copy having no rules. We only want non-rule driven, non-consolidation data, so we set:
Code: Select all
ViewExtractSkipCalcsSet(cubDLBRInputTBD, vwSource, 1);
ViewExtractSkipRuleValuesSet(cubDLBRInputTBD, vwSource, 1);
ViewExtractSkipZeroesSet(cubDLBRInputTBD, vwSource, 1);
Here is the problem. We saw some values show up in the target cube after the copy that had zeros same cells in the source cube. When we turned off the rule for the source cube, lo and behold, there were the values. Now, we know that if a value was written to a cell in a cube and a rule later comes into play for that cell, that the underlying value is retained. So here is the question: does ViewExtractSkipRuleValuesSet do nothing more than turn off the rules while the process is running? What I expected was a skipping of any rule-derived cell, not just a turning off of the rules.
If it is doing nothing more than turning off the rules, then I should expect any underlying value to copy. Seems to be that is what we are seeing.