Note:
If import fails for a selected metadata object, check whether the source object name contains restricted special characters. If it does, rename the object in the source/on-premise environment, recreate or refresh the archive, and retry the import.
Note:
Member IDs
-1 and
-2 are reserved system values in the SaaS environment:
-1 is created as a Leaf member and
-2 as a Node member, and system hierarchies use
-2 as the parent and
-1 as the child. In the on-premises environment, member
-1 may be created as a Node instead. During migration, the on-premises export process converts member
-1 to a Leaf to match SaaS behavior — but if member
-1 still has child members under it on-premises, it is exported as a parent, which is invalid for a Leaf member. This can trigger the following validation error during import:
Leaf member id found in parent member id column in the table STG_DIMENSIONS_HIER_INTF.PARENT_MEMBER_ID.