IC Account copy
- 6 days ago
I routinely copy data with Calculate() and DM packages where IsIC=True that includes I#None. It would be a big problem if that were not permitted.
I cannot think of any reason why simply changing IsIC to False should "fix" the problem.
What I think is more likely the problem is that Constraints, InUse, dimensionality or Cell Security might have been updated AFTER the source data that you are attempting to copy was created in the cube. Put differently, tightening constraints, setting InUse=False, extending a dim, or tightening up cell security among other changes does NOT have any impact of pre-existing data in the cube that may now no longer comply with the new settings. However, if you try to copy that no longer complient data in any way, OS will apply current settings and silently drop any destination data on the floor that does not comply.
As I previously mentioned, it is often handy to create a Cube View that attempts to allow input to one of the destination cells you are trying to write to, so you can see if you can write, and if not, what clues Right Click/Cell Status offers. Based on the clues you have presented, I'm pretty sure the data is being dropped when written to the destination side, for which a Cube View should offer clues.
If doing the copy in a business rule, it is also often handy to read the right side of the Calculate() formula into a junker DataBuffer, which you can then dump out to the log to confirm if the source data you are interested in is included.