Microsoft Dynamics 365 for Sales Connector > Introduction to Microsoft Dynamics 365 for Sales Connector > Rules and guidelines for Microsoft Dynamics 365 for Sales
  

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:

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:
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 image shows the lookup fields- name, websiteurl, and emailaddress1.
The following FetchXML query shows the condition values #INFA_name#, #INFA_websiteurl#, and #INFA_emailaddress1# for the lookup fields name, websiteurl, and emailaddress1:
<fetch mapping="logical" #INFA_PAGING#>
<entity name="account">
<attribute name="name"></attribute><attribute name="websiteurl"></attribute><attribute name="emailaddress1"></attribute>
<filter type="and">
<condition attribute="websiteurl" entityname="account" operator="eq" value="#INFA_websiteurl#"></condition>
<condition attribute="name" entityname="account" operator="eq" value="#INFA_name#"></condition>
<filter type="or">
<condition attribute="emailaddress1" entityname="account" operator="eq" value="#INFA_emailaddress1#">
</condition><condition attribute="name" entityname="account" operator="eq" value="#INFA_name#"></condition>
</filter>
</filter>
</entity>
</fetch>

Rules and guidelines for 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 use Write to Collection Values to write to Microsoft Dynamics 365 for Sales targets: