The order of importing class information only applies if you are mapping Relationships. You cannot import classes with a relationship, if that relationships data is not already imported or created. When a class has the same relationship, the order is not important. The relationship for Users are not shown below since it only depends on having the User (Domain and Username) information. The 1-to-Many relationships have also been left out of this document. |
| If you have multiple .csv files that have relationship mapped to each other, just import all your data without mapping any relationships. Then map all the relationships in you import connectors and resync them. This way the import of the class properties can be done in any order, and then the updating of the relationships can be done in any order. |
|
|
|
| Follow the import order below if you want to import the properties and relationships at the same time: |
| | | |
| | Class | Relationship(s) |
| 1. | Vendor | -None- |
| | Subnet | -None- |
| | Standard | -None- |
| Location | Location (Parent) |
| | | |
| 2. | Catalog Item | Vendor |
| Consumable | Vendor, Location |
| | | |
| 3. | Cost Center | Organization |
| | Organization | Cost Center, Location (Primary), Organization (Parent) |
| | | |
| 4. | Purchase Order | Vendor, Cost Center |
| | Invoice | Vendor, Cost Center |
| | License | Vendor, Cost Center |
| | | |
| 5. | Contract | Vendor, Purchase Order, Cost Center, Invoice |
| | Lease | Vendor, Purchase Order, Cost Center, Invoice |
| | Warranty | Vendor, Purchase Order, Cost Center, Invoice |
| | | |
| 6. | Purchase | Vendor, Purchase Order, Cost Center, Invoice, Support Contract |
| | Software | Vendor, Purchase Order, Cost Center, Invoice, Location, Organization, Support Contract |
| | Hardware | Vendor, Purchase Order, Cost Center, Invoice, Location, Organization, Support Contract, Warranty, Lease, Catalog Item |
