Updating Organizational Structures Using XML

An organizational structure can be updated to have additional nodes, delete nodes and move nodes from one parent to another by modifying and re-importing the organizational structure. The update is always done incrementally and cannot retroactively change an organizational structure. In the cases where the organizational structure is modified and needs to be taken back to a previous state at the previous time, it is recommended to delete a structure and re-import.

You can re-use a previously imported XML file to create an updated organizational structure. (Note that the isnew flag has been deprecated. The flag must be present in the XML file, but the value is not processed.)

Organizational structures can be updated to add a node that was previously deleted, as long as the start date for the node being re-added is not prior to the end-date for the same node. While updating the organizational structure, it is validated to ensure that no child node exists prior to its parent node. The best way to ensure the changes made to the structure are valid is to provide an appropriate start-date for a structure. The start-date for a structure can never be in the past.

Another key consideration with regard to updating an existing organizational structure is that the names of the existing nodes must remain the same. If a node is renamed, FlexNet Manager for Engineering Applications treats the two nodes as two different nodes belonging to different time periods.

Running Report Data Aggregation After XML Import

When updating an organizational structure using XML, you can delete any leaf node. However, the deleted nodes are not moved to the unassigned pool immediately after the update. After updating an organizational structure using XML, you must run the report data aggregation process. The aggregation process moves deleted leaf nodes that had usage data, to the unassigned pool.