ODBC Driver for Microsoft Dynamics CRM

Build 25.0.9434

Miscellaneous

This section provides a complete list of the Miscellaneous properties you can configure in the connection settings for this provider.


PropertyDescription
BatchSizeSpecifies the maximum number of rows included in each batch submitted during batch operations. To submit the entire batch as a single request, set BatchSize to 0 .
CallerIdThe Id of a user to impersonate when inserting or updating new records.
ConnectOnOpenSpecifies whether the provider establishes a connection to Microsoft Dynamics CRM immediately upon opening the connection. Set ConnectOnOpen to True if immediate connectivity verification is necessary.
DefaultDomainThis property is used for the Oracle Database Gateway for ODBC.
DefaultPrecisionThe currency precision that is used for pricing throughout the system. Valid values are 0-4 and Auto. If the value is Auto, the default value will be retrieved from the Microsoft Dynamics CRM server.
EnableForeignKeyDetectionWhether to detect the foreign keys in ODBC.
ExposeVirtualSubColumnBoolean that exposes a virtual subcolumn to return data in a different format.
IncludeCalculatedColumnsThis option controls whether the driver returns the Calculated Columns defined on a table. Only applicable for CRM 2015+.
IncludeDualTableSet this property to mock the Oracle DUAL table for better compatibility with Oracle database.
LanguageCodeThe code indicating the language.
LimitKeySizeThe maximum length of a primary key column.
MapBigintToVarcharThis property controls whether or not the bigint type maps to SQL_VARCHAR instead of SQL_BIGINT. This property is false by default.
MapToIntThis property controls whether or not the long type maps to SQL_INTEGER instead of SQL_BIGINT. This property is false by default.
MapToLongVarcharThis property controls whether or not a column is returned as SQL_LONGVARCHAR.
MapToWVarcharThis property controls whether or not string types map to SQL_WVARCHAR instead of SQL_VARCHAR. This property is set by default.
MaximumColumnSizeThe maximum column size.
MaxRowsSpecifies the maximum number of rows returned for queries that do not include either aggregation or GROUP BY.
OtherSpecifies additional hidden properties for specific use cases., to be used only when our Support team advises it, to address specific issues. See Remarks for details.
PagesizeSpecifies the maximum number of records per page the provider returns when requesting data from Microsoft Dynamics CRM.
PseudoColumnsSpecifies the pseudocolumns to expose as table columns, expressed as a string in the format 'TableName=ColumnName;TableName=ColumnName'.
QueryMethodThe method to use when querying data from Dynamics CRM. In most cases FetchXML will work with all tables.
QueryPassthroughThis option passes the query to the Microsoft Dynamics CRM server as is.
ReadonlyToggles read-only access to Microsoft Dynamics CRM from the provider.
RTKSpecifies the runtime key for licensing the provider. If unset or invalid, the provider defaults to the standard licensing method. This property is only required in environments where the standard licensing method is unsupported or requires a runtime key.
SavedQueryFilterA comma-separated list of filters to use for displaying Saved Queries as views (ex: Accounts%,Contacts%).
TimeoutSpecifies the maximum time, in seconds, that the provider waits for a server response before throwing a timeout error.
UpperCaseIdentifiersThis property reports all identifiers in uppercase. This is the default for Oracle databases and thus allows better integration with Oracle tools such as the Oracle Database Gateway.
UseDisplayNamesBoolean determining if the display names for the columns should be used instead of the API names. UseDisplayNames and UseSchemaNames are mutually exclusive.
UseDisplayTableNamesBoolean determining if the display names for the table should be used instead of the API names.
UseNameForPicklistValueBoolean determining if the string value should be used for picklist field values instead of integers.
UserDefinedViewsSpecifies a filepath to a JSON configuration file that defines custom views. The provider automatically detects and uses the views specified in this file.
UseSchemaNamesBoolean determining if the schema names for the table should be used instead of the API names. UseDisplayNames and UseSchemaNames are mutually exclusive.
UseSimpleNamesSpecifies whether or not simple names should be used for tables and columns.

Copyright (c) 2025 CData Software, Inc. - All rights reserved.
Build 25.0.9434