Glossary
Alternate key
By Emil Björk · Microsoft business apps consultant, Gothenburg
A Dataverse uniqueness constraint on business-meaningful columns — enables external systems to identify records by natural keys rather than GUIDs.
An alternate key in Dataverse is a defined uniqueness constraint on one or more columns of a table, enabling records to be identified by business-meaningful values (Tax ID, Email, Product Number, External System ID) instead of GUIDs. Once configured, inserts violating the uniqueness fail, and the Web API supports retrieval by the alternate key value rather than by GUID. Critical for integration scenarios — external systems can Upsert records by natural key without first looking up the Dataverse GUID. Common examples: Account by Tax ID, Contact by Email, Product by Product Number, Lead by external system ID. Activation requires existing data to be free of duplicates on the key columns.
Related terms
Mentioned in these guides
- Dataverse alternate keys
- Dataverse data import templates
- Dataverse Web API errors explained
- Dual-write sync errors
- Student information system integration for Dynamics 365
- Idempotency in Dynamics 365 integrations
- Integrating Dynamics 365 with HubSpot
- Power Apps canvas app errors explained
- Power Automate flow failures explained