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

Microsoft Dynamics 365 for Sales lookups in mappings

You can create lookups for objects in a Microsoft Dynamics 365 for Sales connection. You can retrieve data from a Microsoft Dynamics 365 for Sales lookup object based on the specified lookup condition.
When you configure a lookup in Microsoft Dynamics 365 for Sales, you select the lookup connection and lookup object. You also define the behavior when a lookup condition returns more than one match.
The following table describes the Microsoft Dynamics 365 for Sales lookup object properties that you can configure in a Lookup transformation:
Property
Description
Connection
Name of the lookup connection.
Source Type
Type of the source object. Select Single Object.
Lookup Object
Name of the lookup object for the mapping.
Multiple Matches
Behavior when the lookup condition returns multiple matches. Select Return any row, Return all rows, or Report error.
Filter
Not applicable.
Sort
Not applicable.
The following table describes the Microsoft Dynamics 365 for Sales lookup object advanced properties that you can configure in a Lookup transformation in mappings:
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.
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.
Record Name Aliases
Not applicable.
The following table describes the advanced properties for Lookup transformations in mappings:
Property
Description
Tracing Level
Determines the detail level of error and status messages written to the Activity Log. You can choose terse, normal, verbose initialization, or verbose data.
Default is normal.
Lookup Caching Enabled
Determines whether to cache lookup data during the runtime session. When you enable caching, the Data Integration Server queries the lookup source once and caches the values for use during the session. Caching the lookup values can improve session performance. When you disable caching, each time a row passes into the transformation.
Default is enabled.
Lookup cache directory name
Specifies the directory to store cached lookup data when you select Lookup Caching Enabled. The directory name can be an environment variable.
Lookup Data Cache Size
Sets the maximum size that the Secure Agent allocates to the data cache in memory. Select Auto to determine the cache size at runtime. Select Value to specify a maximum amount of memory to allocate to the cache. If the server cannot allocate the specified maximum amount when the session is initialized, the session fails. When the cached data is more than the available memory, it is paged to disk.
Default is Auto.
Lookup Index Cache Size
Sets the maximum size the agent allocates to the index cache in memory. Select Auto to determine the cache size at runtime. Select Value to specify a maximum amount of memory to allocate to the cache. If the server cannot allocate the specified maximum amount when the session is initialized, the session fails. When the cached data is more than the available memory, it is paged to disk. Default is Auto.
Default is Auto.
Null ordering
Determines how the null values are ordered. You can choose to sort null values high or low. By default, null values are sorted high. This overrides configuration to treat nulls in comparison operators as high, low, or null.
Sorted Input
Indicates whether or not the lookup file data is in sorted order. This increases lookup performance for file lookups. If you enable sorted input and the condition columns are not grouped, the session fails. If the condition columns are grouped but not sorted, the lookup is processed as if you did not configure sorted input.
Pre-build Lookup Cache
Specifies to build the lookup cache before the Lookup transformation receives data. Multiple lookup cache files can be built at the same time to improve performance.
Optional
Determines whether the transformation is optional. If a transformation is optional and there are no incoming fields, the task can run and the data can go through another branch in the data flow. If a transformation is required and there are no incoming fields, the task fails.
For example, you might configure a parameter for the source connection. In one branch of the data flow, you add a Lookup transformation with a field rule so that only Date/Time data enters the transformation. You specify that the Lookup transformation is optional. When you configure the mapping task, you select a source that does not have Date/Time data. The mapping task ignores the branch with the Lookup transformation, and the data flow continues through another branch of the mapping.