How to rename a Dimension correctly in Planning Cloud without Data Management to stop working
Summary:
Looking for a best practice guide how to rename a dimension (top element, member name, not alias) in Planning Cloud (or FCCS)
Challenge: how do we adjust the Artifacts of Data Exchange correctly, so that Data Management/ Data Exchange Interface
- File Import Interfaces (from csv into the Planning Cloud) (EPM Local)
- EPM Transfer Interface (Data Pull from a remote Planning cloud into the own planning cloud) (EPM Cloud)
continue to work - the current conclusion is, that this is not supported and you must never rename a dimension, as it breaks everything you built - which is not acceptable from a customer perspective ( I work for 15 years with Oracle EPM - but keeping DataManagement/ DataExchange working longterm is still a challenge)
Tagged:
0