Dynamics CRM 365

Audience: Low-code Engineers

Skill Prerequisites: Actions, Tokens, Connectors

The Dynamics CRM 365 add-on works with records (entities) in Microsoft Dynamics 365 / Dynamics CRM. Its actions create, read, search, update and delete records such as contacts, accounts, leads and cases, so your application can keep its data in step with Dynamics.

note

The add-on is installed separately as the DnnSharp.DynamicsCrm package, and needs the DYNCRM feature in your license. If it isn't licensed, the actions fail with a "not licensed" error. If you don't see the Dynamics actions or the Dynamics Service Connector type, the add-on isn't installed.

Choosing an action

Action	What it does	Use it to
Create Entity	Creates a record from a list of attribute values, and can save its GUID in a token.	Create a lead or contact when someone submits a form.
Read Entity	Reads the attributes you choose from one record, by its GUID, into tokens.	Prefill an edit form, or read a record you just created.
Find Entity	Searches an entity with conditions and loads the first match into tokens, including its GUID.	Find a contact by email, or get an account's GUID from its account number.
Read Multiple Entities	Searches an entity with conditions and loads all matches into a list, with optional paging.	Email every contact of an account, export records, or count matches.
Update Entity	Changes the attributes you list on a record, by its GUID.	Update a contact's details, or change a case's status.
Delete Entity	Deletes a record by its GUID.	Remove a contact when the user closes their account.

Connecting to Dynamics

All the actions use a connector of type Dynamics Service Connector. Create it on the Connectors page or with Add Connector, and check it with Test Connector. See Connecting to Dynamics for its fields.

• Sign-in. The connector signs in with a username and password, using Active Directory (on-premises) or an online or federated sign-in. There's no option for OAuth, app registrations or client secrets.
• Permissions. The actions run as the Dynamics user in the connector, so that user must be allowed to read, create, change or delete the entities you use.
• Caching. The sign-in is reused until its security token is about to expire.

Finding the GUID

Read Entity, Update Entity and Delete Entity need the record's GUID and its entity's logical name. Get the GUID from:

• Create Entity, in its Created EntityId Token. Save it with your own record.
• Find Entity or Read Multiple Entities, in the token or list property you set in Id Mapping.

Find Entity fails when nothing matches and Id Mapping is set, and Read Entity fails when the GUID isn't found. To check whether a record exists, see When nothing matches. In 1.28, Order Type isn't applied, so Find Entity and Read Multiple Entities always sort in ascending order.

Names and values

• Use logical names. Entity and attribute names are the lowercase logical names, such as emailaddress1, not display names such as Email. An unknown attribute name fails the action.
• Writing values. Create Entity and Update Entity convert each value to the attribute's type. Option sets take the option's number, and lookups take the related record's GUID. An empty or invalid number becomes 0 and an empty Yes/No value becomes false, without an error. See Attribute values.
• Reading values. The read actions return Dynamics' formatted value when there is one, so an option set gives its label, not its number. For lookups, use the extra :Id token or property to get the GUID.
• Errors. None of the actions have an On Error list. Connection and Dynamics errors fail the action. To handle them, put the action inside Execute Actions and use its On Error actions.

To create and manage connectors, see Connectors. To work with the list from Read Multiple Entities, see Lists Objects. For Salesforce, see Salesforce. For all add-ons, see Add-ons.

Revised 10/02/2026