...
For example, you may use the /Type Multi-Column notation to create Locations for the Base Location “North Campus”, and the path for each new Location should include the following Location Types: “Building”, “Floor” and “Room”. For this Import, you would select the Base Location "North Campus", and the CSV file would be set up as follows:
| Action | /Building | /Floor | /Room |
|---|---|---|---|
| CREATE | A | 02 | 231 |
| CREATE | A | 02 | 240 |
| CREATE | A | 03 | 311 |
| CREATE | B | 01 | 119 |
The first entry in the above data file sample would be interpreted as the Location Type “Room”. It would have the name “231” under the Location Type “Floor” with name “02”, which would exist under the Location Type “Building” with the name “A”.
...
Using the Path and Name notation, your CSV file must include an Action column for the desired action “CREATE”. It must also include a column for the Location path associated with each new Location, with column header “Path”. For each new Location the “Path” field should include the entire Location path with each path segment separated by a backward slash (e.g., “Building A\Floor 02\Room 231”).
| Action | Path | Type | Name |
|---|---|---|---|
| CREATE | Building A\Floor 02 | Room | 231 |
| CREATE | Building A\Floor 02 | Room | 240 |
| CREATE | Building A\Floor 03 | Room | 311 |
| CREATE | Building B\Floor 01 | Room | 119 |
In the above data file sample, the first entry would be interpreted as the Location Type “Room”. It would have the name “231” under the Location Type “Floor” with name “02”, which would exist under the Location Type “Building” with the name “A”.
...
Using the UUID notation to update existing Locations, your CSV file must include an Action column header for the desired import action “UPDATE”. The file must include the UUID column header. The UUID uniquely identifies the existing Location. With the UUID identified, a Name column header will provide the data field for renaming each listed Location. A Path column header will provide the data fields necessary to change Location position.
Action | UUID | State | Zip Code | City | Description |
UPDATE | eebc7182-365d-475a-a328-195d3e4bc19b | VA | 22102 | Tysons | Change address via import UUID |
| UPDATE | c8ec6064-22ca-47b2-94ee-be000319fc5e | VA | 22102 | Tysons | Change address via import UUID |
UPDATE | 2fdcd1f6-3995-4ba8-8e70-ddb8e4ce1ce6 | VA | 22102 | Tysons | Change address via import UUID |
UPDATE | 3b5e3bfc-44d0-455d-80d1-6f53fd6fbbd0 | VA | 221025 | Tysons | Change address via import UUID |
In the above sample CSV file, the User is changing the City, State and Zip code associated with four uniquely identified Locations.
...
When updating Locations via bulk Import, the New Name column header can be used to rename existing Locations which are uniquely identified by UUID. The first column of the CSV file must include the Action column header for the desired action "UPDATE", and the UUID data field must be populated for each line of the data file.
Action | UUID | New Name |
UPDATE | fff6390b-a14b-4829-9381-591fb36ed82e | W231 |
| UPDATE | b6261822-2b3c-477f-9d77-722849448be0 | W240 |
UPDATE | f9e683f3-0d55-470b-8382-14bab86a2765 | W311 |
UPDATE | 7221f3cf-28f4-4066-8cf7-b1870e402444 | E119 |
Note: When using the New Name data column, do not include a Path column in the same Import data file, as values from the two data fields may conflict as imported line items are processed.
...