- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 65 Insurance
- 536.7K On-Premises Infrastructure
- 138.4K Analytics Software
- 38.6K Application Development Software
- 5.8K Cloud Platform
- 109.5K Database Software
- 17.6K Enterprise Manager
- 8.8K Hardware
- 71.2K Infrastructure Software
- 105.3K Integration
- 41.6K Security Software
Advice on smart use of DATACOPY
(Note: This same post can be found here: Advice on smart use of DATACOPY . Reposting in OTN for wider cast)
I'm looking for advice on how to improve my code regarding the use of DATACOPY.
I have a sparse dimension that looks similar to this:
I'm not getting into details, but at some point I need the parent value of Parent_X to be copied to Legacy_X
I first solved this using the following:
And that works perfectly, but now I've realized blocks are not being created for Legacy* members, and using block member calculations cannot be done this time (for reasons I'm not detailing now).
So, I consider using DATACOPY to force the creation of blocks, but something like
is giving the fllowing error:
Error: 1012001 Invalid Calc Script syntax [
I get the same if I use @PARENT instead, so it looks like my only option would be something like this:
DATACOPY Parent_1 TO Legacy_1;
DATACOPY Parent_2 TO Legacy_2;
but I'd hate having to do that. It looks terribly awful.
Notice that in this example I made the Parent_X and the Legacy_X match their sufixes (X) for better understanding, but this does not always happen. Nonetheless, the first child under a parent will always start by "Legacy*"
I also tried using @CREATEBLOCK, but it didn't seem to work.
Version is on-premise 126.96.36.199, but I asume this should be the same for PBCS.