Rules and guidelines for Microsoft Dynamics 365 for Sales
Consider the following rules and guidelines when you use Microsoft Dynamics 365 for Sales source and target operations:
•If you use the data driven operation on a Microsoft Dynamics 365 for Sales target, the DD_UPDATE or DD_DELETE constraints do not work.
•If you run a delete operation on a Microsoft Dynamics 365 for Sales entity and the simple navigation field is mapped to the target field, the task fails.
•You cannot write to accountlist_association, contactlist_association, or leadlist_association attributes of the list entity.
•Microsoft Dynamics 365 for Sales Connector supports only the following DateTime format: yyyy-mm-ddThh:mm:ssZ. For example, 2016-12-31T00:00:00Z, where Z represents the UTC timezone.
•When you fetch a large number of records from Microsoft Dynamics 365 for Sales, set the JVM options for type DTM to increase the -Xms and -Xmx values in the system configuration details of the Secure Agent, and then restart the Secure Agent.
•You can set the JVM property -DMSD_SALES_ADAPTER_LOG_LEVEL=ALL to configure unique request IDs for all the requests so that they can be uniquely identified at the Microsoft Dynamics 365 for Sales server. The request ID is sent as a header with the request when you configure the JVM property.
•When you use the upsert operation, you can enter either a valid, unique guid or a null guid for the record to be inserted. Microsoft Dynamics 365 for Sales Connector first tries to update the record with the guid present in the target object. If the update operation fails, Microsoft Dynamics 365 for Sales Connector inserts the value into the record.
- If you do not enter any value, Microsoft Dynamics 365 for Sales Connector does not update any value. Microsoft Dynamics 365 for Sales Connector creates an auto-generated guid and inserts this value into the record.
- If you enter a unique, valid guid, which is not present in the target object, Microsoft Dynamics 365 for Sales Connector does not update the record. Microsoft Dynamics 365 for Sales Connector inserts the guid that you provided into the record.
•The input for Customer, Owner, and Lookup data types should be in the following format:
/LogicalCollectionName(guid) or LogicalCollectionName(guid)
•You can use the $LastRunTime variable in a simple data filter for a source object.
•When you write data to Microsoft Dynamics 365 for Sales in batch mode, even if an error row does not contain a primary key or an alternate key, the Secure Agent writes the error row to the error file.
•When you use an in-out parameter of type datetime in the mapping to filter source data that contains date and time values, the mapping truncates the time part while writing the data to the target.
Rules and guidelines for FetchXML query and record name aliases
Consider the following rules and guidelines when you use FetchXML query and record name aliases in Microsoft Dynamics 365 for Sales sources and lookups:
•To configure a FetchXML query, you must select the source type as Multiple Objects. Then, select the Add Sibling option to add multiple objects. Depending upon the relationship name selected, the related object is shown up for the primary object in the Add Sibling Object window.
•The primary entity in the FetchXML query and the primary object in the source should be the same.
•Attributes should not have aliases in the FetchXML query.
•You must specify an alias map in the Record Name Aliases field. The map holds the alias names for each linked entity that is part of the FetchXML query. The map is required because the result dataset contains modified field names for the linked objects.
•If you use a single source object, the Record Name Aliases field is optional.
•The linked-entity name and alias specified in the Record Name Aliases field should be the same as in the FetchXML query.
•The mapped attributes in the field mapping must match the attributes mentioned in the FetchXML query. Otherwise, the non-matching attributes are ignored.
•There is a URL length limit on the FetchXML query. To fetch more elements, use <all-attributes /> in the FetchXML query.
•You can configure the $LastRuntime and $LastRunDate parameters as part of the FetchXML query. Do not use quotes when you configure the parameters in the query.
•You can fully parameterize a maximum of 600 characters in the FetchXML query.
• To fetch all the records from Microsoft Dynamics 365 for Sales, enter the term #INFA_PAGING# in the FetchXML query.
•You cannot configure key range partitioning with FetchXML queries.
When you use Microsoft Dynamics 365 for Sales sources and caching-disabled lookups, you can configure a condition in the FetchXML query. In the FetchXML query, set the condition attribute to the value of the lookup field that you used in the lookup condition.
For example, if the lookup fields are name, websiteurl, and emailaddress1, as shown in the following image, the condition values are #INFA_name#, #INFA_websiteurl#, and #INFA_emailaddress1#.
The following FetchXML query shows the condition values #INFA_name#, #INFA_websiteurl#, and #INFA_emailaddress1# for the lookup fields name, websiteurl, and emailaddress1:
Rules and guidelines when you write to collection values
Collection-valued properties represent a collection of entities. The collection could represent either a one-to-many or a many-to-many relationship between the entities. The many-to-many relationship is handled through an entity known as intersect entity.
Consider the following rules and guidelines when you write to collections values in a Microsoft Dynamics 365 for Sales target:
•To update an association of the existing entities, choose the insert operation and map the primary key or alternate key of the entity and the collection value fields. For example, to associate an account with a lead, map the fields accountid and accountleads_association.
•To create a new record and add an association to it, choose the insert operation and map the data field and collection valued fields along with a key.
For example, to insert an account and add an existing association to it, map the fields name, emailaddress1, accountid, and accountleads_association. You can insert null values to the accountid field because the value is retrieved from the Microsoft Dynamics CRM as a part of insert operation.
You cannot create a new record and add an association to it in batch mode.
•To delete an existing association, select the delete operation and map the primary key or alternate key of the entity and the collection value fields.
•You can use one of the following formats when you use the collection valued property:
