Loading the XML File

When importing an extracted xml file, it processes in the following order:

  1. New or changed Members

  2. Deleted Members

  3. New Relationships

  4. Deleted Relationships

NOTE: The processing order is important because if any errors occur during the xml file load, OneStream applies as many modifications as it can up to the point of the error.  For example, an xml file contains ten Member changes, three deleted Members and one new relationship.  If an error occurs when trying to delete the first Member, the ten Member changes will still take place because they are processed first during the xml load.  Any modifications in the xml prior to the error will occur and any after the error will not.

If a user receives an error during the load process, the error must be resolved in order to complete the metadata migration.

Common Load Errors and Resolutions

  1. Deleting a Member with data
    If a Member without data is deleted from the source application, but that same Member contains data in the destination application, an error occurs and the Member will not be deleted.  To resolve the error, do one of the following:

    1. Clear the Member’s data in the destination application and reload the xml file.

    2. Create a new xml extract excluding that Member from the file.

    3. Edit the xml file to exclude the Member and the action.

  1. Deleting a Member without Data

    Care should be taken when deleting Entity members.  Even though the member may not have data, it may be in use as an Intercompany Partner.  Ensure the member is not in use on any data records, or on records as an Intercompany Partner.

  2. Undefined Security Group
    If a security group is assigned to a Dimension Member in the source application, but does not exist in the destination application, an error will occur.  To resolve the error, do one of the following:

    1. Create the security group in the destination application and reload the xml file.

    2. Create a new xml extract excluding this Member and its changes from the file.

    3. Edit the xml file to exclude the Member and the action.

  1. Undefined FX Rate Type
    If a FX Rate Type is assigned to a Scenario Member in the source application, but does not exist in the destination application, an error will occur.  To resolve the error, do one of the following:

    1. Create the FX Rate Type in the destination application and reload the file.

    2. Create a new xml extract excluding this Member and its changes from the file.

    3. Edit the xml file to exclude the Member and the action.

  2. Invalid Characters in the XML File
    If the xml file was edited and invalid characters were entered for a Member name, an error will occur.  To resolve the error, do one of the following:

    1. Make the Member modifications in the source application and extract an xml file without invalid characters.

    2. Edit the xml file and remove the invalid characters.