Microsoft Dynamics 365 for Sales Connector > Mappings and mapping tasks with Microsoft Dynamics 365 for Sales Connector > Microsoft Dynamics 365 for Sales sources in mappings
  

Microsoft Dynamics 365 for Sales sources in mappings

In a mapping, you can configure a Source transformation to represent a Microsoft Dynamics 365 for Sales source.
The following table describes the Microsoft Dynamics 365 for Sales source properties that you can configure in a Source transformation:
Property
Description
Connection
Name of the source connection.
Source Type
Type of the source object. Select Single Object, Multiple Object or Parameter.
Object
Name of the source object for the mapping.
Filter
Filter value in a read operation. You can add conditions to filter records and reduce the number of rows that the Secure Agent reads from the source.
Sort
Sorts records based on the conditions you specify. Click Configure to add conditions to sort records and reduce the number of rows that the Secure Agent reads from the source.
The following table describes the Microsoft Dynamics 365 for Sales advanced properties that you can configure in a Source transformation:
Advanced Property
Description
Row Limit
The maximum number of rows that the Secure Agent processes. Specify a number to process a specific number of rows.
Page Size
Size of the page set to retrieve the maximum number of entries for each page. Default value is 100.
Tracing Level
Amount of detail that appears in the log for this transformation. You can choose terse, normal, verbose initialization, or verbose data. Default is normal.
FetchXML Query
The native Microsoft query format to read data from Microsoft Dynamics 365 for Sales. Enter the FetchXML query defined in Microsoft Dynamics 365 for Sales. You can use one or any combination of paging, filter, sort, and join operations in the FetchXML query.
If you do not add a FetchXML query for multiple sources, an implicit join will take place and the primary object and sibling object relationship will be used.
The implicit join is used, by default.
Record Name Aliases
The map that holds the alias names for each linked entity that is part of the FetchXML query. Enter the record name aliases as a name-value pair. Use the following format:
{"<EntityName1>" : "<EntityAlias1>","<EntityName2>" : "<EntityAlias2>"}
For example,
{"lead":"lead","contact":"con"}
Read Picklist Values
Reads string values for picklist fields.
By default, the check box is not selected.