All Collections
CRM integrations
Microsoft Dynamics 365
Dynamics 365 and Field-Level Security
Dynamics 365 and Field-Level Security

How to set up your Dynamics 365 integration in Dealfront if you use field-level security

Tamar Keenan avatar
Written by Tamar Keenan
Updated over a week ago

If your organisation uses field-level security in Dynamics 365 you need to remember that when setting up your Dynamics 365 integration in Dealfront.

While integrating with Dealfront, you can choose which entities in Dynamics 365 you want to sync your Dealfront account with. The accounts in Dynamics 365 are always synced to make the integration work, all the other Dynamics 365 entities are optional.

The Dynamics 365 accounts sync includes the following fields that we will always need to have the read and write permission to:

accountid 
name
description
createdon
modifiedon
ownerid
numberofemployees
websiteurl
createdby
modifiedby
lfapp_latestwebsitevisit
lfapp_leadfeederlink
statecode
address1_country
address1_stateorprovince
address1_city sic

If you choose to sync other Dynamics 365 entities as well, you need to remember that similar rules will also apply to them. However, each Dynamics 365 entity requires read and write permissions to different fields. Please contact us for a list of those fields if necessary.

As long as the person who sets up the Dynamics 365 integration or who will be the account owner has all the necessary read and write permissions to the above-mentioned fields in Dynamics 365, field-level security should not be an issue.

--

Questions, comments, feedback? Please let us know by contacting our support team via the chat or by sending us an email at support@dealfront.com.

RELATED:

Did this answer your question?