Is there a way to control member order when loading metadata through Data Integration?
in Planning
Summary:
Existing member order is being changed by the metadata load through Data Integration.
Content (please ensure you mask any confidential information):
We are using the EPM Integration Agent for metadata loads. Users have modified the order of existing members manually in the outline, but the members are being moved by the metadata load. This seem to be a change from the past metadata load methods where new members were added at the bottom and existing members stay where they are (except for parent changes.)
I can't find a description of this behavior in the documentation.
The old OLU documentation has flags to control this, is there way to control the behavior in the EPM Cloud?
Tagged:
0