This section lists possible reasons for XML import failure related to security settings.
Importing an XML file with missing security properties
If an XML import does not have security elements, the import succeeds. Default security values are applied to the object. For example:
If the <SecurityList> element is missing, the Everyone group and View actions are set to Allow.
If the <Publisher name /> and <Published></Published> elements are missing, the Publisher name is defined as "Administrator" and Published is set to TRUE.
If an import contains a security element without any attributes, the import fails. For example:
If a security attribute is missing in an XML import file, the import fails. An error message displays the name of the object that causes the import to fail.
If the publisher name is not defined, the import fails. Metrics Management does not create an object that does not include a publisher name.
Importing system object security settings in an XML file
The security properties of system objects are defined in the import XML file as Read-Only. System objects include index mappings, period ranges, relative periods, special periods, translators, and unit types.
XML imports function in the same way as Metrics Management. A user cannot edit his own security settings.
If the <SecurityList> element is missing, the Everyone group and View actions are set to Allow.