Adapter Limitations
Known limitations of the Adapter for Dynamics 365 and CRM include:
- Connection String — If you plan to use the Connection String deployment type, you must remove unnecessary values from fields in the Connection Settings. If you leave values in those fields, they are included in the connection string built by the adapter and could cause your connection to fail.
- Application Publisher — Dynamics 365 On-Premise deployments are not supported for the Application Publisher.
- Pre- and post-SQL scripts — Pre- and post-SQL scripts cannot be used against this adapter.
- SQLQUERY functions — SQLQUERY functions are not supported. Use DBLOOKUP functions instead.
- Fields on invoice and quote
objects do not update — Some fields on the invoice and quote
objects do not update, even when running a DTS file as integration user. The DTS shows as successful,
but no updates occur. Otherwise, the following message occurs:
The entity cannot be updated because it is read-only
The affected fields on these objects are:
- baseamount
- totalamountlessfreight
- extendedamount
- totallineitemdiscountamount
- ispricelocked
- totaldiscountamount
- totalamount
- totaltax
- totallineitemamount
- volumediscountamount
- Company match component — The Company match component is supported only for 3.0.
If you are using the company match component and you upgrade your Dynamics CRM 3.0 server, you must change the lookup links on any DTS files that use the custom attribute that is part of company match. Commit levels are not supported.
- Using Dynamics 365 in a Connection String deployment with IFD authentication — You must create a Dynamics 365 user as the integration user. This must be a different user than the default INTEGRATION user. For Connection String deployments with IFD authentication, Dynamics 365 does not have access to the Active Directory information required to use the default INTEGRATION User.
- DateOnly Format In DateTime Fields — A date and time value can be written to a DateTime field, even if that field is configured with a DateOnly format. When you perform a lookup on this field, the time value used on the lookup is midnight, 00:00. If the DateTime field contains a time value other than midnight, the lookup fails.
For example, if your DTS updates a DateOnly DateTime field with a Dynamics 365 source value that includes a time value, such as 10/6/2015 10:00, both the date and time values are written to the field, although only the date, 10/6/2015, displays. If you perform a lookup on that field, 10/6/2015, because the field is a DateOnly format, the lookup reads 10/6/2015 00:00, which does not match the actual value in the field, and the lookup fails.
To perform a successful lookup on a DateOnly DateTime field, the time in that field must be midnight, 00:00.
- Cancelled Dynamics 365 sales orders — If a Dynamics 365 sales order is in a canceled state, it is considered read-only and can only be updated by an integration user. For more information, see Using Integration Mode.
-
Adapter for Dynamics CRM 4.x with Microsoft Dynamics 365 —
If you use the Adapter for Dynamics CRM 4.x to point to an instance of Dynamics CRM or
Microsoft Dynamics 365, the following fields are not available:
- owningteam — Entities missing this field include, but may not be
limited to:
- account
- contact
- invoice
- salesorder
- owninguser — Entities missing this field include, but may not be
limited to:
- account
- invoicedetail
- contact
- salesorder
- customeraddress
- salesorderdetail
- invoice
- owningteam — Entities missing this field include, but may not be
limited to:
See also