When should I enable org-scoped identities?

Use org-scoped External Identities if you anticipate that the same entity will be added from multiple connectors within the same organization, or if more than one connector needs to read the External Identity to sync (often for CMMS ticket syncing). In particular, enabling org-scoped identities for Things/Zones in the CSV connector enables the same entity contributed by multiple connectors to merge into one entity. 

The value you include in the RefId column is added as the ExternalIdentity value.

For example, if a Thing has already been contributed by one connector with org-scoped External Identity VAV01, and you want to contribute additional data to it through the CSV connector, enable org-scoped identities for Things in the Advanced Config and use the value VAV01 in the thingRefId column.

You can also use org-scoped External Identities for Buildings, Floors, and Spaces, but these entities will also merge based on other identities.

  • Buildings merge based on the PostalAddressIdentity value -- when they have matching addresses.
  • Floors merge based on the FloorLevelIdentity value -- when they have the same floorLevel value in the same Building.
  • Spaces merge based on the Space Code value -- when scoped to the same Floor or Building.

Read more: Why have these entities been merged or duplicated?

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request