Buildings
Duplicates
If your import file contributes a new address for an existing Building, this will create a duplicate. Check that the address matches the existing address exactly. If you catch a mistake after the import, you can always re-import an edited file through the same CSV Import connector.
⚠️ Automatic address validation may edit the building address from what you have entered it in the CSV. ⚠️
Merged
If Buildings share the same address, they will be merged into the same Building. If the address provided is not standardized or incomplete, Mapped automatically normalizes the address. In order to avoid changing the building's address from what is entered in your file, disable address validation in the Advanced Config tab by setting Disable Address Validation to true and saving.
Read more: When should I disable address validation?
Floors
When importing Floors, be consistent in the floor-level indexing to ensure Floors merge correctly without duplicates. A Floor named "Level 01" can have floor.Level 1 or floor.Level 0, but if it has both this will result in duplicate Floors of the same name.
If a Floor is named "Level 01" with floor.Level 1 in one connector but the Floor is named "Level 02" with floor.Level 1 in a second connector, this results in merged Floors.
Spaces
When importing Spaces, be mindful of the Space Code and related Floor. Spaces that share the same Space Code, and that are mapped to the same Floor Level in the same Building, will be merged into one Space.
Things or Zones
When importing Things or Zones, the RefId value is especially important for merging or keeping separate entities. To enable a Thing or Zone to be merged with other Things or Zones contributed from other connectors, in Advanced Config set Add Org Scoped Identities - Thing to true. The RefId you use will be added to the Thing as an org-scoped ExternalIdentity value, and it will merge with any Things sharing the same identity.
To prevent a Thing from being merged with any other Things that share the same external RefId in other connectors, leave that setting disabled (the default).
RefIds
Understanding Scope and Identities
The RefId field adds an ExternalIdentity with the RefId as the value. By default, all RefIds in the CSV connector are connector-scoped. This means the value you enter in the RefId column acts as a unique identifier for that entity within the single CSV connector you're working on.
The Mapped Graph merges entities on shared identities in the same scope. The CSV connector's validation will not let you re-use the same RefId on multiple entities within a single import and it will flag it as an error. If you import multiple files that re-use the same RefId across different entities, those entities will merge.
If using org-scoped identities in the Advanced Config, this entity will merge with any other entity sharing that same org-scoped identity. If there is no other entity that shares that org-scoped identity, it won't merge.
Mapped Ids
Sometimes a user expects using the existing Mapped ID (eg THGA1B2C3D4F5G6H7J8K9) as the RefId will merge this record with the existing entity that has that Mapped ID.
Actually, External Identities do not match up with entity Ids in the Mapped Graph, they only match up with other ExternalIdentity values of the same scope. In order to target an existing entity for merging, you would need to add one of its org-scoped ExternalIdentity values to the RefId column.