This week's Tech Tuesday is from our Senior Technical Consultant, Chris Hanson, who will walk us through a scenario many come across when using SmartConnect.
When you use SmartConnect to import data into CRM, you will run into the scenario of needing to populate a field with a GUID. Any time you have a lookup field within CRM it is storing a GUID for its value which then links to another entity record.
There are a couple ways to work with and import them. The first is using the Additional Column called an Entity Look-up. For an entity look-up you need to provide what entity you are looking up the ID for, and then provide one or more fields to compare on. The screenshot below shows what it might look like if you are importing to the currency field on the account entity in CRM:
The Currency entity is selected in the lookup, and then the field from my source data is used to compare against the currency code field in CRM. The comparison that you set up must match exactly otherwise no records will be returned by the lookup. So you need to have at least one field in both the source and CRM that will have matching values. If there isn’t one, you will need to manipulate your source data in a calculated field or the data source itself so the data does match up.
The other way to work with GUIDs is by using an Additional Column called an Entity Reference. This is only used if you already have the GUID in your source data. To set it up, all you need to do is select the entity that the GUID is for, and then pick the source field that contains the GUID. By using the entity reference, SmartConnect makes sure it's handled as an identifier rather than a string value.
If you have any questions feel free to leave a comment or email us at email@example.com!