08-31-2022 06:47 PM - last edited on 05-23-2023 11:10 AM by JackLacava
Happy Labor Day for USA. Happy gas shortages, high electric bills and soon coming freezing winters for many of us around the world.
I renamed my Cubeview from CV1 to CV2_deleteVersion08302022. Why did my workflows automatically change its configuration to use new name CV2_deleteVersion08302022? Should it not remain as CV1 ? I'll try to give a screen shot
Solved! Go to Solution.
09-01-2022 02:31 AM
Simply by design, so that you can rename things and not have to rework everything that utilises the renamed object. In reality nothing has changed in your workflow because it would be referring to the cubeview by ID behind the scenes rather than the name.
09-01-2022 07:38 PM
Funnily though I've actually wanted to be able to rename things and be able to switch something else in! It does come in useful sometimes. But you can work around it with export/import and some tweaks.
08-31-2022 06:48 PM - edited 08-31-2022 06:54 PM
why name of CV changed in workflow?
09-01-2022 02:31 AM
Simply by design, so that you can rename things and not have to rework everything that utilises the renamed object. In reality nothing has changed in your workflow because it would be referring to the cubeview by ID behind the scenes rather than the name.
09-01-2022 09:02 AM
I understand - it's referential integrity. Oracle Planning/ Essbase doesn't have that, so I was pleasantly surprised.
Thanks.
09-01-2022 07:38 PM
Funnily though I've actually wanted to be able to rename things and be able to switch something else in! It does come in useful sometimes. But you can work around it with export/import and some tweaks.
09-01-2022 09:40 PM
Same here - there should be an option to turn off referential integrity. Yes, that's what I did - workaround using Load/Extract. Thanks again buddy.
Happy Labor day weekend!!