Concept of Alternate Keys has been introduced with Microsoft Dynamics CRM Version 2016.
All Microsoft Dynamics CRM records have unique identifiers defined as GUIDs. These are the primary key for each entity. However if you have alot integrated systems in your organization – it would be very difficult for other systems to retrieve or update records using the guids as they wont necessarily store CRM’s internal GUIDs. Hence you can create an alternate key which is actually a data in other systems – they can easily update or retrieve data from CRM using this.
Only below field types can be added as an alternate key :
- Decimal Number
- Whole Number
- Single Line of Text
- Date Time [ Only with Dynamics 365 v9 or above]
- Lookup [ Only with Dynamics 365 v9 or above]
- Picklist [ Only with Dynamics 365 v9 or above]
Point to note is that for a single entity, only 5 alternate keys are allowed in CRM.
Apart from Above , Alternate keys will stop creating duplicate records in the system, be it normal creation , excel import , or from external service.Wow how cool is that!
To Create an alternate key , go to customization > Entity> Expand the entity and look for “Alternate Keys” option > click on New and give display name and schema name > select the field for which you want to enable it > click on the right arrow > click on Save.
when you save an alternate key it, you are actually creating an async job which goes through following status :
- Pending
- In Progress
- Active
- Failed
Once status shows “Active” it means its ready to be used:
you can very well use alternate keys with WebApi , take reference from the below :
Write to me if you have any questions on this topic.
I hope this helps!
Cheers!
