Microsoft Dynamics 365 Connection Details¶
Introduction¶
Connector Version
This documentation is based on version 23.0.8803 of the connector.
Get Started¶
Microsoft Dynamics 365 Version Support
The connector supports read/write access to Microsoft Dynamics 365 through OData Web services.
Establish a Connection¶
Connect to Microsoft Dynamics 365¶
Edition
and OrganizationUrl
are required connection properties for connection. The Microsoft Dynamics 365 driver supports connecting to the following Microsoft Dynamics 365 editions:
- CustomerService
- FieldService
- FinOpsOnline
- FinOpsOnPremise
- HumanResources
- Marketing
- ProjectOperations
- Sales
Note that "Supply Chain Management" is the same as "Finance and Operations." You can connect to it by setting the Edition
to either "FinOpsOnline" or "FinOpsOnPremise."
OrganizationUrl is the URL to your Microsoft Dynamics 365 organization. For instance, https://orgcb42e1d0.crm.dynamics.com
Authenticate to Microsoft Dynamics 365¶
OAuth¶
If required by your organization, Admin Consent is needed when authorizing a new OAuth application for your Azure Tenant. In all OAuth flows, the first time someone in your organization installs and uses an OAuth application, an administrator for the organization must approve the application for their Azure Tenant.
Your organization can choose, however, to disable this requirement.
Desktop Applications¶
An embedded OAuth application is provided that simplifies OAuth desktop Authentication. Alternatively, you can create a custom OAuth application. See Creating a Custom OAuth Application for information about creating custom applications and reasons for doing so.
For authentication, the only difference between the two methods is that you must set two additional connection properties when using custom OAuth applications. After setting the following connection properties, you are ready to connect:
AuthScheme
: TheAzureAD
in your application settings.InitiateOAuth
: Set this toGETANDREFRESH
. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting theOAuthAccessToken
.OAuthClientId
: (custom applications only) The client ID in your application settings.OAuthClientSecret
: (custom applications only) The client secret in your application settings.CallbackURL
: The Redirect URL in your application settings.
When you connect the connector opens the OAuth endpoint in your default browser. Log in and grant permissions to the application. The connector then completes the OAuth process:
- Extracts the access token from the callback URL and authenticates requests.
- Obtains a new access token when the old one expires.
- Saves OAuth values in
OAuthSettingsLocation
to be persisted across connections.
Web Applications¶
When connecting via a Web application, you need to create and register a custom OAuth application with Microsoft Dynamics 365. See Creating a Custom OAuth Application for more information about custom applications. You can then use the connector to get and manage the OAuth token values.
Get an OAuth Access Token
Set the following connection properties to obtain the OAuthAccessToken
:
AuthScheme
:AzureAD
.OAuthClientId
: The client ID in your application settings.OAuthClientSecret
: The client secret in your application settings
Then call stored procedures to complete the OAuth exchange:
- Call the GetOAuthAuthorizationUrl stored procedure. Set the CallbackURL input to the callback URL you specified in your application settings. If necessary, set the Scope parameter to request custom permissions. The stored procedure returns the URL to the OAuth endpoint.
- Open the URL, log in, and authorize the application. You are redirected back to the callback URL.
- Call the GetOAuthAccessToken stored procedure. Set the AuthMode input to
WEB
. Set the Verifier input to the "code" parameter in the query string of the callback URL. If necessary, set the Scope parameter to request custom permissions.
Once you have obtained the access and refresh tokens, you can connect to data and refresh the OAuth access token either automatically or manually.
Automatic Refresh of the OAuth Access Token
To have the driver automatically refresh the OAuth access token, set the following on the first data connection:
InitiateOAuth
:REFRESH
.OAuthClientId
: The client ID in your application settings.OAuthClientSecret
: The client secret in your application settings.OAuthAccessToken
: The access token returned by GetOAuthAccessToken.OAuthRefreshToken
: The refresh token returned by GetOAuthAccessToken.OAuthSettingsLocation
: The location where the connector saves the OAuth token values, which persist across connections.
On subsequent data connections, the values for OAuthAccessToken and OAuthRefreshToken are taken from OAuthSettingsLocation
.
Manual Refresh of the OAuth Access Token
The only value needed to manually refresh the OAuth access token when connecting to data is the OAuth refresh token.
Use the RefreshOAuthAccessToken stored procedure to manually refresh the OAuthAccessToken
after the ExpiresIn parameter value returned by GetOAuthAccessToken has elapsed, then set the following connection properties:
OAuthClientId
: The client ID in your application settings.OAuthClientSecret
: The client secret in your application settings.
Then call RefreshOAuthAccessToken with OAuthRefreshToken
set to the OAuth refresh token returned by GetOAuthAccessToken. After the new tokens have been retrieved, open a new connection by setting the OAuthAccessToken property to the value returned by RefreshOAuthAccessToken.
Finally, store the OAuth refresh token so that you can use it to manually refresh the OAuth access token after it has expired.
Headless Machines¶
To configure the driver to use OAuth with a user account on a headless machine, you need to authenticate on another device that has an internet browser.
- Choose one of these two options:
- Option 1: Obtain the
OAuthVerifier
value as described in "Obtain and Exchange a Verifier Code" below. - Option 2: Install the connector on another machine and transfer the OAuth authentication values after you authenticate through the usual browser-based flow, as described in "Transfer OAuth Settings" below.
- Option 1: Obtain the
- Then configure the connector to automatically refresh the access token from the headless machine.
You can follow the headless OAuth authentication flow using the OAuth credentials for your custom OAuth app. To create a custom OAuth application, see Creating a Custom OAuth Application. This section describes the procedure to authenticate and connect to data.
Option 1: Obtain and Exchange a Verifier Code
First, set the following properties on the headless machine:
InitiateOAuth
: Set toOFF
.OAuthClientId
: Set to the Client ID in your OAuth Integration settings.OAuthClientSecret
: Set to the Client Secret in your OAuth Integration settings.
Next, authenticate from another machine and obtain the OAuthVerifier
connection property:
- Call the GetOAuthAuthorizationUrl stored procedure. Set the CallbackURL input to the Redirect URI you specified in your application settings. The stored procedure returns the URL to the OAuth endpoint.
- Open the returned URL in a browser. Log in and grant permissions to the connector. You are then redirected to the callback URL, which contains the verifier code.
- Save the value of the Verifier. You must set the value of the Verifier in the
OAuthVerifier
connection property.
Finally, on the headless machine, set the following connection properties to obtain the OAuth authentication values:
OAuthClientId
: Set to the Client ID in your OAuth Integration settings.OAuthClientSecret
: Set to the Client Secret in your OAuth Integration settings.OAuthVerifier
: Set to the verifier code.OAuthSettingsLocation
: Set to persist the encrypted OAuth authentication values to the specified location.InitiateOAuth
: Set toREFRESH
.
Connect to Data
After the OAuth settings file is generated, set the following properties to connect to data:
OAuthSettingsLocation
: Set to the location containing the encrypted OAuth authentication values. Make sure this location gives read and write permissions to the provider to enable the automatic refreshing of the access token.InitiateOAuth
: Set toREFRESH
.
Option 2: Transfer OAuth Settings
To install the connector on another machine, authenticate, and then transfer the resulting OAuth values:
- On a second machine, install the connector and connect with the following properties set:
OAuthSettingsLocation
: Set to a writable location.InitiateOAuth
: Set toGETANDREFRESH
.OAuthClientId
: Set to the client ID in your application settings.OAuthClientSecret
: Set to the client secret in your application settings.CallbackURL
: Set to the callback URL in your application settings.
- Test the connection to authenticate. The resulting authentication values are written and encrypted to the path specified by
OAuthSettingsLocation
. After you have successfully tested the connection, copy the OAuth settings file to your headless machine. On the headless machine, set the following connection properties to connect to data:InitiateOAuth
: Set toREFRESH
.OAuthSettingsLocation
: Set to the location of your OAuth settings file. Make sure this location gives read and write permissions to the connector to enable the automatic refreshing of the access token.
Admin Consent¶
Admin consent refers to when the Admin for an Azure Active Directory tenant grants permissions to an application which requires an admin to consent to the use case.
The embedded application within the Microsoft Dynamics 365 connector, contains no permissions that require admin consent. Therefore, this information applies only to custom applications.
Admin Consent Permissions
When creating a new OAuth application in the Azure Portal, you must specify which permissions the application requires. Some permissions may be marked stating "Admin Consent Required". For example, all Groups permissions require Admin Consent. If your application requires admin consent, there are a couple of ways this can be done.
The easiest way to grant admin consent is to just have an admin log into portal.azure.com and navigate to the application you have created in App Registrations
. Under API Permissions, click Grant Consent
, which grants your application the necessary permissions on the tenant on which it was created.
If your organization has multiple tenants or the application needs to be granted permissions for other tenants outside your organization, you can use the GetAdminConsentURL to generate the Admin Authorization URL. Unlike the GetOAuthAuthorizationUrl, there is no important information returned from this endpoint. If the grants access, it returns a boolean indicating that permissions were granted.
After an admin grants consent, authentication may be performed as normal.
Client Credentials¶
Client credentials refers to a flow in OAuth where there is no direct user authentication taking place. Instead, credentials are created for just the application itself. All tasks taken by the application are done without a default user context. This makes the authentication flow a bit different from standard.
Client OAuth Flow
All permissions related to the client oauth flow require admin consent. This means the application embedded with the Microsoft Dynamics 365 connector cannot be used in the client oauth flow. You must create your own OAuth application to use client credentials. See Creating a Custom OAuth Application for more details.
In "App Registration" in portal.azure.com, navigate to API Permissions and select the Microsoft Graph permissions. There are two distinct sets of permissions - Delegated and Application permissions. The permissions used during client credential authentication are under Application Permissions. Select the applicable permissions you require for your integration.
You are ready to connect after setting one of the below connection properties groups depending on the authentication type.
Client Secret
InitiateOAuth
:GETANDREFRESH
. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting theOAuthAccessToken
.AzureTenant
: The tenant you wish to connect to.OAuthGrantType
:CLIENT
.OAuthClientId
: The client ID in your app settings.OAuthClientSecret
: The client secret in your app settings.
Certificate
InitiateOAuth
:GETANDREFRESH
. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting theOAuthAccessToken
.AzureTenant
: The tenant you wish to connect to.OAuthGrantType
:CLIENT
.OAuthClientId
: The client ID in your app settings.OAuthJWTCert
: The JWT Certificate store.OAuthJWTCertType
: The type of the certificate store specified byOAuthJWTCert
.
Azure AD¶
Azure AD is a connection type that leverages OAuth to authenticate. Set your AuthScheme
to AzureAD
.
Follow the steps below to authenticate with the credentials for a custom AzureAD app. See Creating a Custom OAuth Application.
There are two types of app authentication available: using a client secret and using a certificate. You can use any of them depending on the configured app authentication.
Get an AzureAD Access Token
You are ready to connect after setting one of the below connection properties groups depending on the authentication type.
Client Secret
AuthScheme
:AzureServicePrincipal
in your app settings.InitiateOAuth
:GETANDREFRESH
. You can use InitiateOAuth to avoid repeating the AzureAD exchange and manually setting theOAuthAccessToken
.AzureTenant
: The tenant you wish to connect to.OAuthClientId
: The Client ID in your app settings.OAuthClientSecret
: The client secret in your app settings.
Certificate
AuthScheme
: TheAzureServicePrincipal
in your app settings.InitiateOAuth
:GETANDREFRESH
. You can use InitiateAzureAD to avoid repeating the AzureAD exchange and manually setting theOAuthAccessToken
.AzureTenant
: The tenant you wish to connect to.OAuthClientId
: The client ID in your app settings.OAuthJWTCert
: The JWT Certificate store.OAuthJWTCertType
: The type of the certificate store specified byOAuthJWTCert
.
Azure Service Principal¶
The authentication as an Azure Service Principal is handled via the OAuth Client Credentials flow. It does not involve direct user authentication. Instead, credentials are created for just the application itself. All tasks taken by the app are done without a default user context, but based on the assigned roles. The application access to the resources is controlled through the assigned roles' permissions. Create an AzureAD App and an Azure Service Principal
When authenticating using an Azure Service Principal, you must register an application with an Azure AD tenant. See Creating a Custom AzureAD Service Principal App for more information.
Assign a role to the application
To access resources in your subscription, you must assign a role to the application.
- Open the
Subscriptions
page by searching and selecting the Subscriptions service from the search bar. - Select the subscription to assign the application to.
- Open the
Access control (IAM)
and selectAdd > Add role assignment
to open theAdd role assignment
page. - Select
Owner
as the role to assign to your created Azure AD app.
Complete the Authentication
To connect follow these steps:
- Set the
AuthScheme
toAzureServicePrincipal
for using a client secret orAzureServicePrincipalCert
for using a certificate in your application setting. - Set the connection properties that apply to both schemes.
- Set the connection properties specific to the authentication scheme you selected.
For Both Client Secret and Certificate
Set these connection properties and then continue to the relevant section below:
InitiateOAuth
:GETANDREFRESH
. You can useInitiateOAuth
to avoid repeating the OAuth exchange and manually setting theOAuthAccessToken
.AzureTenant
: The tenant you want to connect to.
Client Secret
Continue with the following:
OAuthClientId
: The client ID in your application settings.OAuthClientSecret
: The client secret in your application settings.
Certificate
Continue with the following:
OAuthJWTCert
: The JWT Certificate store.OAuthJWTCertType
: The type of the certificate store specified byOAuthJWTCert
.
Create a Custom OAuth Application¶
Create a Custom OAuth Application¶
Microsoft Dynamics 365 supports authentication using Azure AD and Azure Service Principal, both of which are OAuth-based.
This topic describes how to:
- create and register custom OAuth application for Azure AD or Azure Service Principal
- provide Admin Consent to a custom OAuth application
- create a custom OAuth application for use with client credentials
Azure AD¶
In portal.azure.com
:
- Log in to
https://portal.azure.com
. - In the left-hand navigation pane, select
Azure Active Directory
, thenapplicationRegistrations
. - Click
New registration
. - Enter a name for the application.
- Select the desired tenant setup: single- or multi-tenant, and public or private use.
- If you select the default option, "Accounts in this organizational directory only", you must set the
AzureTenant
connection property to the ID of the Azure AD Tenant when establishing a connection with the Microsoft Dynamics 365 connector. Otherwise, the authentication attempt fails with an error. - If your application is for private use only, specify
Accounts in this organization directory only
. - If you want to distribute your application, choose one of the multi-tenant options.
- If you select the default option, "Accounts in this organizational directory only", you must set the
- Set the redirect URL to
http://localhost:33333
(the connector's default) OR specify a different port and setCallbackURL
to the exact reply URL you defined. - Click
Register
to register the new application. An application management screen displays.
Note the value inApplication (client) ID
as theOAuthClientId
and theDirectory (tenant) ID
as theAzureTenant
. - Navigate to
Certificates & Secrets
and define the application authentication type. There are two types of authentication available: certificate (recommended) or client secret.- For certificate authentication: In
Certificates & Secrets
, selectUpload certificate
, then upload the certificate from your local machine. - For creating a new client secret: In
Certificates & Secrets
, selectNew Client Secret
for the application and specify its duration. After the client secret is saved, Microsoft Dynamics 365 displays the key value. Copy this value, as it is displayed only once. This value becomes theOAuthClientSecret
.
- For certificate authentication: In
- Select
API Permissions > Add > Delegated permissions
. Select Required Permissions > Add
. UnderSelect an API
, selectDynamics ERP > Delegated Permissions for _OAuthGrantType_ = CODE
(default).- Save your changes.
- If you have specified the use of permissions that require admin consent (such as the Application Permissions), you can grant them from the current tenant on the API Permissions page.
Azure Service Principal¶
To use Azure Service Principal authentication, you must set up the ability to assign a role to the authentication application, then register an application with the Azure AD tenant to create a new Service Principal. That new Service Principal can then leverage the assigned role-based access
control to access resources in your subscription.
In portal.azure.com
:
- Create a custom OAuth AD application, as described above.
- Use the search bar to search for the Subscriptions service.
- Open the
Subscriptions
page. - Select the subscription to which to assign the application.
- Open the
Access control (IAM)
. - Select
Add > Add role assignment
. Microsoft Dynamics 365 opens theAdd role assignment
page. - Assign your custom Azure AD application the role of
Owner
.
Admin Consent¶
Some custom applications require administrative permissions to operate within an Azure Active Directory tenant. Admin consent can be granted when creating a new custom OAuth application, by adding relevant permissions that are already marked with "Admin Consent Required". Admin consent is also required to use Client Credentials in the OAuth flow.
To grant admin consent:
- Have an admin log in to
portal.azure.com
. - Navigate to
App Registrations
and find the custom OAuth application you created. - Under
API Permissions
, clickGrant Consent
.
This gives your application permissions on the tenant under which it was created.
Consent for Client Credentials¶
OAuth supports the use of client credentials to authenticate. In a client credentials OAuth flow, credentials are created for the authenticating application itself. The auth flow acts just like the usual auth flow except that there is no prompt for an associated user to provide credentials.
All tasks accepted by the application are executed outside of the context of a default user.
Note
Since the embedded OAuth credentials authenticate on a per-user basis, you cannot
use them in a client OAuth flow. You must always create a custom OAuth application to use client credentials.
In portal.azure.com
:
- Create a custom OAuth application, as described above.
- Navigate to
App Registrations
. - Find the application you just created, and open
API Permissions
. - Select the Microsoft Graph permissions. There are two distinct sets of permissions: Delegated and Application.
- Under
Application Permissions
, select the permissions you require for your integration.
Create a Custom AzureAD Service Principal App¶
Creating a custom AzureAD application and a service principal that can access the necessary resources is required when authenticating using an Azure Service Principal.
Steps to Create an AzureAD SP App¶
Follow the steps below to create a custom AzureAD application and obtain the connection properties for the Azure Service Principal authentication.
-
Log in to
https://portal.azure.com
. -
In the left-hand navigation pane, select
Azure Active Directory > App Registrations
and clickNew registration
. -
Enter an application name and select
Any Azure AD Directory - Multi Tenant
. Then set the redirect URL tohttp://localhost:33333
, the connector's default, or a URL of your choosing. -
After creating the app, copy the Application (client) ID value displayed in the "Overview" section, since this value is used as the
OAuthClientId
-
Define the application authentication type by navigating to the "Certificates & Secrets" section. There are two types of authentication available: client secret and certificate.
The recommended authentication method is via a certificate.
Option 1 - Upload a certificate
: In "Certificates & Secrets", selectUpload certificate
and the certificate to upload from your local machine.Option 2 - Create a new application secret
: In "Certificates & Secrets", selectNew Client Secret
for the application and specify its duration. After saving the client secret, the key value is displayed. Copy this value since it is displayed only once. You will use it as theOAuthClientSecret
.
-
On the
Authentication
tab, make sure to select the optionAccess tokens
(used for implicit flows).
Important Notes¶
Configuration Files and Their Paths¶
- All references to adding configuration files and their paths refer to files and locations on the Jitterbit agent where the connector is installed. These paths are to be adjusted as appropriate depending on the agent and the operating system. If multiple agents are used in an agent group, identical files will be required on each agent.
Advanced Features¶
This section details a selection of advanced features of the Microsoft Dynamics 365 connector.
User Defined Views
The connector allows you to define virtual tables, called user defined views, whose contents are decided by a pre-configured query. These views are useful when you cannot directly control queries being issued to the drivers. See User Defined Views for an overview of creating and configuring custom views.
SSL Configuration
Use SSL Configuration to adjust how connector handles TLS/SSL certificate negotiations. You can choose from various certificate formats; see the SSLServerCert
property under "Connection String Options" for more information.
Proxy
To configure the connector using private agent proxy settings, select the Use Proxy Settings
checkbox on the connection configuration screen.
Query Processing
The connector offloads as much of the SELECT statement processing as possible to Microsoft Dynamics 365 and then processes the rest of the query in memory (client-side).
User Defined Views¶
The Microsoft Dynamics 365 connector allows you to define a virtual table whose contents are decided by a pre-configured query. These are called User Defined Views, which are useful in situations where you cannot directly control the query being issued to the driver, e.g. when using the driver from Jitterbit. The User Defined Views can be used to define predicates that are always applied. If you specify additional predicates in the query to the view, they are combined with the query already defined as part of the view.
There are two ways to create user defined views:
- Create a JSON-formatted configuration file defining the views you want.
- DDL statements.
Define Views Using a Configuration File¶
User Defined Views are defined in a JSON-formatted configuration file called UserDefinedViews.json
. The connector automatically detects the views specified in this file.
You can also have multiple view definitions and control them using the UserDefinedViews
connection property. When you use this property, only the specified views are seen by the connector.
This User Defined View configuration file is formatted as follows:
- Each root element defines the name of a view.
- Each root element contains a child element, called
query
, which contains the custom SQL query for the view.
For example:
{
"MyView": {
"query": "SELECT * FROM GoalHeadings WHERE MyColumn = 'value'"
},
"MyView2": {
"query": "SELECT * FROM MyTable WHERE Id IN (1,2,3)"
}
}
Use the UserDefinedViews
connection property to specify the location of your JSON configuration file. For example:
"UserDefinedViews", "C:\Users\yourusername\Desktop\tmp\UserDefinedViews.json"
Define Views Using DDL Statements¶
The connector is also capable of creating and altering the schema via DDL Statements such as CREATE LOCAL VIEW, ALTER LOCAL VIEW, and DROP LOCAL VIEW.
Create a View¶
To create a new view using DDL statements, provide the view name and query as follows:
CREATE LOCAL VIEW [MyViewName] AS SELECT * FROM Customers LIMIT 20;
If no JSON file exists, the above code creates one. The view is then created in the JSON configuration file and is now discoverable. The JSON file location is specified by the UserDefinedViews
connection property.
Alter a View¶
To alter an existing view, provide the name of an existing view alongside the new query you would like to use instead:
ALTER LOCAL VIEW [MyViewName] AS SELECT * FROM Customers WHERE TimeModified > '3/1/2020';
The view is then updated in the JSON configuration file.
Drop a View¶
To drop an existing view, provide the name of an existing schema alongside the new query you would like to use instead.
DROP LOCAL VIEW [MyViewName]
This removes the view from the JSON configuration file. It can no longer be queried.
Schema for User Defined Views¶
User Defined Views are exposed in the UserViews
schema by default. This is done to avoid the view's name clashing with an actual entity in the data model. You can change the name of the schema used for UserViews by setting the UserViewsSchemaName
property.
Work with User Defined Views¶
For example, a SQL statement with a User Defined View called UserViews.RCustomers
only lists customers in Raleigh:
SELECT * FROM Customers WHERE City = 'Raleigh';
An example of a query to the driver:
SELECT * FROM UserViews.RCustomers WHERE Status = 'Active';
Resulting in the effective query to the source:
SELECT * FROM Customers WHERE City = 'Raleigh' AND Status = 'Active';
That is a very simple example of a query to a User Defined View that is effectively a combination of the view query and the view definition. It is possible to compose these queries in much more complex patterns. All SQL operations are allowed in both queries and are combined when appropriate.
SSL Configuration¶
Customize the SSL Configuration¶
By default, the connector attempts to negotiate SSL/TLS by checking the server's certificate against the system's trusted certificate store.
To specify another certificate, see the SSLServerCert
property for the available formats to do so.
Data Model¶
The Microsoft Dynamics 365 connector models Microsoft Dynamics 365 entities in relational Tables, Views, and Stored Procedures. The table definitions are dynamically obtained from the OData service you connect to. Any changes in the metadata, such as added or removed columns or changes in data type, can be loaded by reconnecting.
Views
Views describes the available views. Views are statically defined to model PicklistAttributeMetadata, MultiPicklistAttributeMetadata and more.
Stored Procedures
Stored Procedures are function-like interfaces to the data source. They can be used to perform additional operations that fall outside of the
standard CRUD model such as retrieving an OAuth access token.
Tables¶
The connector uses the OData services of Microsoft Dynamics 365 to dynamically obtain a list of tables. All of your Microsoft Dynamics 365 tables will display as available once you connect.
Views¶
Views are similar to tables in the way that data is represented; however, views are read-only.
Queries can be executed against a view as if it were a normal table.
Microsoft Dynamics 365 Connector Views¶
Name | Description |
---|---|
MultiSelectPickListAttributeMetaData | Contains the Picklist metadata for an attribute type MultiSelect OptionSet. Note: This view is only available when Edition is set to either CustomerService, FieldService, Marketing, ProjectOperations or Sales. |
MultiSelectPickListOptions | Contains the Options Value of MultiSelect PicklistMetadata. Note: This view is only available when Edition is set to either CustomerService, FieldService, Marketing, ProjectOperations or Sales. |
PickListAttributeMetaData | Contains the metadata for an attribute type Picklist. Note: This view is only available when Edition is set to either CustomerService, FieldService, Marketing, ProjectOperations or Sales. |
PickListOptions | Contains the Options value of PickListMetaData. Note: This view is only available when Edition is set to either CustomerService, FieldService, Marketing, ProjectOperations or Sales. |
MultiSelectPickListAttributeMetaData¶
Contains the Picklist metadata for an attribute type MultiSelect OptionSet. Note: This view is only available when Edition
is set to either CustomerService, FieldService, Marketing, ProjectOperations or Sales.
Select¶
The connector will use the Microsoft Dynamics 365 API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the connector.
TableName
supports '=','IN' operators.
For example, the following queries are processed server side:
SELECT * FROM MultiSelectPickListAttributeMetaData WHERE TableName = 'teams'
SELECT * FROM MultiSelectPickListAttributeMetaData WHERE TableName IN ('accounts', 'teams')
Columns¶
Name | Type | Description |
---|---|---|
ColumnName [KEY] | String | |
MetadataId | String | |
OptionSet_Description_LocalizedLabels | String | |
OptionSet_Description_UserLocalizedLabel_HasChanged | String | |
OptionSet_Description_UserLocalizedLabel_IsManaged | Boolean | |
OptionSet_Description_UserLocalizedLabel_Label | String | |
OptionSet_Description_UserLocalizedLabel_LanguageCode | Integer | |
OptionSet_Description_UserLocalizedLabel_MetadataId | String | |
OptionSet_DisplayName_LocalizedLabels | String | |
OptionSet_DisplayName_UserLocalizedLabel_HasChanged | String | |
OptionSet_DisplayName_UserLocalizedLabel_IsManaged | Boolean | |
OptionSet_DisplayName_UserLocalizedLabel_Label | String | |
OptionSet_DisplayName_UserLocalizedLabel_LanguageCode | Integer | |
OptionSet_DisplayName_UserLocalizedLabel_MetadataId | String | |
OptionSet_ExternalTypeName | String | |
OptionSet_HasChanged | String | |
OptionSet_IntroducedVersion | String | |
OptionSet_IsCustomizable_CanBeChanged | Boolean | |
OptionSet_IsCustomizable_ManagedPropertyLogicalName | String | |
OptionSet_IsCustomizable_Value | Boolean | |
OptionSet_IsCustomOptionSet | Boolean | |
OptionSet_IsGlobal | Boolean | |
OptionSet_IsManaged | Boolean | |
OptionSet_MetadataId | String | |
OptionSet_Name | String | |
OptionSet_OptionSetType | String | |
OptionSet_ParentOptionSetName | String | |
TableName | String |
MultiSelectPickListOptions¶
Contains the Options Value of MultiSelect PicklistMetadata. Note: This view is only available when Edition
is set to either CustomerService, FieldService, Marketing, ProjectOperations or Sales.
Select¶
The connector will use the Microsoft Dynamics 365 API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the connector.
TableName
supports '=','IN' operators.
For example, the following queries are processed server side:
SELECT * FROM MultiSelectPickListOptions WHERE TableName = 'teams'
SELECT * FROM MultiSelectPickListOptions WHERE TableName IN ('accounts', 'teams')
Columns¶
Name | Type | Description |
---|---|---|
ColumnName | String | |
Color | String | |
ExternalValue | String | |
HasChanged | String | |
IsManaged | Boolean | |
Label_LocalizedLabels | String | |
Label_UserLocalizedLabel_HasChanged | String | |
Label_UserLocalizedLabel_IsManaged | Boolean | |
Label_UserLocalizedLabel_Label | String | |
Label_UserLocalizedLabel_LanguageCode | Integer | |
Label_UserLocalizedLabel_MetadataId | String | |
Description_LocalizedLabels | String | |
Description_UserLocalizedLabel_HasChanged | String | |
Description_UserLocalizedLabel_IsManaged | Boolean | |
Description_UserLocalizedLabel_Label | String | |
Description_UserLocalizedLabel_LanguageCode | Integer | |
Description_UserLocalizedLabel_MetadataId | String | |
MetadataId | String | |
ParentValues | String | |
Value | Integer | |
TableName | String |
PickListAttributeMetaData¶
Contains the metadata for an attribute type Picklist. Note: This view is only available when Edition
is set to either CustomerService, FieldService, Marketing, ProjectOperations or Sales.
Select¶
The connector will use the Microsoft Dynamics 365 API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the connector.
TableName
supports '=','IN' operators.
For example, the following queries are processed server side:
SELECT * FROM PickListAttributeMetaData WHERE TableName = 'teams'
SELECT * FROM PickListAttributeMetaData WHERE TableName IN ('accounts', 'teams')
Columns¶
Name | Type | Description |
---|---|---|
ColumnName [KEY] | String | |
MetadataId | String | |
OptionSet_Description_LocalizedLabels | String | |
OptionSet_Description_UserLocalizedLabel_HasChanged | String | |
OptionSet_Description_UserLocalizedLabel_IsManaged | Boolean | |
OptionSet_Description_UserLocalizedLabel_Label | String | |
OptionSet_Description_UserLocalizedLabel_LanguageCode | Integer | |
OptionSet_Description_UserLocalizedLabel_MetadataId | String | |
OptionSet_DisplayName_LocalizedLabels | String | |
OptionSet_DisplayName_UserLocalizedLabel_HasChanged | String | |
OptionSet_DisplayName_UserLocalizedLabel_IsManaged | Boolean | |
OptionSet_DisplayName_UserLocalizedLabel_Label | String | |
OptionSet_DisplayName_UserLocalizedLabel_LanguageCode | Integer | |
OptionSet_DisplayName_UserLocalizedLabel_MetadataId | String | |
OptionSet_ExternalTypeName | String | |
OptionSet_HasChanged | String | |
OptionSet_IntroducedVersion | String | |
OptionSet_IsCustomizable_CanBeChanged | Boolean | |
OptionSet_IsCustomizable_ManagedPropertyLogicalName | String | |
OptionSet_IsCustomizable_Value | Boolean | |
OptionSet_IsCustomOptionSet | Boolean | |
OptionSet_IsGlobal | Boolean | |
OptionSet_IsManaged | Boolean | |
OptionSet_MetadataId | String | |
OptionSet_Name | String | |
OptionSet_OptionSetType | String | |
OptionSet_ParentOptionSetName | String | |
TableName | String |
PickListOptions¶
Contains the Options value of PickListMetaData. Note: This view is only available when Edition
is set to either CustomerService, FieldService, Marketing, ProjectOperations or Sales.
Select¶
The connector will use the Microsoft Dynamics 365 API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the connector.
TableName
supports '=','IN' operators.
For example, the following queries are processed server side:
SELECT * FROM PickListOptions WHERE TableName = 'teams'
SELECT * FROM PickListOptions WHERE TableName IN ('accounts', 'teams')
Columns¶
Name | Type | Description |
---|---|---|
ColumnName | String | |
Color | String | |
ExternalValue | String | |
HasChanged | String | |
IsManaged | Boolean | |
Label_LocalizedLabels | String | |
Label_UserLocalizedLabel_HasChanged | String | |
Label_UserLocalizedLabel_IsManaged | Boolean | |
Label_UserLocalizedLabel_Label | String | |
Label_UserLocalizedLabel_LanguageCode | Integer | |
Label_UserLocalizedLabel_MetadataId | String | |
Description_LocalizedLabels | String | |
Description_UserLocalizedLabel | String | |
MetadataId | String | |
ParentValues | String | |
Value | Integer | |
TableName | String |
Stored Procedures¶
Stored procedures are function-like interfaces that extend the functionality of the connector beyond simple SELECT/INSERT/UPDATE/DELETE operations with Microsoft Dynamics 365.
Stored procedures accept a list of parameters, perform their intended function, and then return any relevant response data from Microsoft Dynamics 365, along with an indication of whether the procedure succeeded or failed.
Microsoft Dynamics 365 Connector Stored Procedures¶
Name | Description |
---|---|
CreateAssociation | Creates an association between two entities based on a navigation property. Set the IncludeNavigationProperties connection property to true in order to use this stored procedure. |
CreateSchema | Creates a schema file for the specified table or view. Note: This stored procedure only applies when Edition is set to either FinOpsOnline, FinOpsOnPremise or HumanResources. |
GetAdminConsentURL | Gets the admin consent URL that must be opened separately by an admin of a given domain to grant access to your application. Only needed when using custom OAuth credentials. |
GetOAuthAccessToken | Gets the auth token used to authenticate to the service. |
GetOAuthAuthorizationUrl | Gets an authorization URL from the data source. The authorization URL can be used to generate a verifier required to obtain the OAuth token. |
ListAssociations | Lists associations for a given table and navigation property. Set the IncludeNavigationProperties connection property to true in order to use this stored procedure. |
ListNavigationProperties | Lists navigation properties for a given table and the tables they are associated with. Navigation properties are used by the Association stored procedures. Set the IncludeNavigationProperties connection property to true in order to use this stored procedure. |
RefreshOAuthAccessToken | Obtains an updated OAuthAccessToken if passed a token to refresh. |
RemoveAssociation | Removes an association between two entities based on a navigation property. Set the IncludeNavigationProperties connection property to true in order to use this stored procedure. |
CreateAssociation¶
Creates an association between two entities based on a navigation property. Set the IncludeNavigationProperties connection property to true in order to use this stored procedure.
Input¶
Name | Type | Required | Description |
---|---|---|---|
FromId | String | False | The ID of the entity you are creating an associations for. |
UrlId | String | False | An alternative to specifying the FromId. This is the complete URL to the resource for which the association is being created. It is required to be specified in the case that the navigation property is an abstract, or to specify more specific child types where the navigation property entity type is used as a basetype. |
FromTable | String | True | The table where the entity comes from that you are creating an association for. For example, if the FromId was from a table called Customers, set this parameter to: Customers. |
ToNavigationProperty | String | True | The navigation property you are creating an association on. It can be obtained from ListNavigationProperties. |
ToId | String | False | The ID of the navigation entity. This will come from the table associated with the navigation property. |
ToUrlId | String | False | An alternative to specifying the ToId. This is the complete URL to the resource to be associated. It is required to be specified in the case that the navigation property is an abstract, or to specify more specific child types where the navigation property entity type is used as a basetype. |
CreateSchema¶
Creates a schema file for the specified table or view.
CreateSchema¶
Creates a local schema file (.rsd) from an existing table or view in the data model.
The schema file is created in the directory set in the Location
connection property when this procedure is executed. You can edit the file to include or exclude columns, rename columns, or adjust column datatypes.
The connector checks the Location
to determine if the names of any .rsd files match a table or view in the data model. If there is a duplicate, the schema file will take precedence over the default instance of this table in the data model. If a schema file is present in Location
that does not match an existing table or view, a new table or view entry is added to the data model of the connector.
Input¶
Name | Type | Required | Accepts Output Streams | Description |
---|---|---|---|---|
TableName | String | True | False | The name of the table or view. |
FileName | String | False | False | The full file path and name of the schema to generate. Ex : 'C:\Users\User\Desktop\D365\Contents.rsd' |
FileStream | String | False | True | An instance of an output stream where file data is written to. Only used if FileName is not set. |
Result Set Columns¶
Name | Type | Description |
---|---|---|
FileData | String | File data that will be outputted encoded in Base64 if the FileName and FileStream inputs are not set. |
Result | String | Whether or not the schema was successfully downloaded. |
GetAdminConsentURL¶
Gets the admin consent URL that must be opened separately by an admin of a given domain to grant access to your application. Only needed when using custom OAuth credentials.
Input¶
Name | Type | Required | Description |
---|---|---|---|
CallbackUrl | String | False | The URL the user will be redirected to after authorizing your application. This value must match the Reply URL in the Azure AD app settings. |
State | String | False | The same value for state that you sent when you requested the authorization code. |
Result Set Columns¶
Name | Type | Description |
---|---|---|
URL | String | The authorization URL, entered into a Web browser to obtain the verifier token and authorize your app. |
GetOAuthAccessToken¶
Gets the auth token used to authenticate to the service.
Input¶
Name | Type | Required | Description |
---|---|---|---|
AuthMode | String | False | The type of authentication you are attempting. Use App for a Windows application, or Web for Web-based applications. The default value is APP. |
Verifier | String | False | A verifier returned by the service that must be input to return the access token. Needed only when using the Web auth mode. Obtained by navigating to the URL returned in GetOAuthAuthorizationUrl. |
CallbackUrl | String | False | The URL the user will be redirected to after authorizing your application. |
State | String | False | This field indicates any state that may be useful to your application upon receipt of the response. Your application receives the same value it sent, as this parameter makes a round-trip to Dynamics authorization server and back. Uses include redirecting the user to the correct resource in your site, using nonces, and mitigating cross-site request forgery. |
Prompt | String | False | Defaults to 'select_account' which prompts the user to select account while authenticating. Set to 'None', for no prompt, 'login' to force user to enter their credentials or 'consent' to trigger the OAuth consent dialog after the user signs in, asking the user to grant permissions to the app. |
Result Set Columns¶
Name | Type | Description |
---|---|---|
OAuthAccessToken | String | The OAuth access token. |
OAuthRefreshToken | String | A token that may be used to obtain a new access token. |
ExpiresIn | String | The remaining lifetime on the access token. |
\* | String | Other outputs that may be returned by the data source. |
GetOAuthAuthorizationUrl¶
Gets an authorization URL from the data source. The authorization URL can be used to generate a verifier required to obtain the OAuth token.
Input¶
Name | Type | Required | Description |
---|---|---|---|
CallbackURL | String | False | The URL the user will be redirected to after authorizing your application. |
State | String | False | This field indicates any state that may be useful to your application upon receipt of the response. Your application receives the same value it sent, as this parameter makes a round-trip to Dynamics authorization server and back. Uses include redirecting the user to the correct resource in your site, using nonces, and mitigating cross-site request forgery. |
Prompt | String | False | Defaults to 'select_account' which prompts the user to select account while authenticating. Set to 'None', for no prompt, 'login' to force user to enter their credentials or 'consent' to trigger the OAuth consent dialog after the user signs in, asking the user to grant permissions to the app. |
Result Set Columns¶
Name | Type | Description |
---|---|---|
Url | String | The authorization URL that will need to be opened for the user to authorize your app. |
ListAssociations¶
Lists associations for a given table and navigation property. Set the IncludeNavigationProperties connection property to true in order to use this stored procedure.
Input¶
Name | Type | Required | Description |
---|---|---|---|
FromId | String | False | The ID of the entity you are listing associations for. |
UrlId | String | False | An alternative to specifying the FromId. This is the complete URL to the resource you are listing the associations for. It is required to be specified in the case that the navigation property is an abstract, or to specify more specific child types where the navigation property entity type is used as a basetype. |
FromTable | String | True | The table where the entity comes from that you are listing entities for. For example, if the FromId was from a table called Customers, set this parameter to: Customers. |
NavigationProperty | String | True | The navigation property you are listing assications for. It can be obtained from ListNavigationProperties. |
Result Set Columns¶
Name | Type | Description |
---|---|---|
Uri | String | The linked URL. |
ListNavigationProperties¶
Lists navigation properties for a given table and the tables they are associated with. Navigation properties are used by the Association stored procedures. Set the IncludeNavigationProperties connection property to true in order to use this stored procedure.
Input¶
Name | Type | Required | Description |
---|---|---|---|
TableName | String | True | The name of the table to list navigation properties for. |
Result Set Columns¶
Name | Type | Description |
---|---|---|
Name | String | The name of the navigation property. |
AssociatedTable | String | The table the navigation property is associated with. |
RefreshOAuthAccessToken¶
Obtains an updated OAuthAccessToken if passed a token to refresh.
Input¶
Name | Type | Required | Description |
---|---|---|---|
OAuthRefreshToken | String | True | The refresh token returned from the original authorization code exchange. |
Result Set Columns¶
Name | Type | Description |
---|---|---|
OAuthAccessToken | String | The new OAuthAccessToken returned from the service. |
OAuthRefreshToken | String | A token that may be used to obtain a new access token. |
ExpiresIn | String | The remaining lifetime on the access token. |
RemoveAssociation¶
Removes an association between two entities based on a navigation property. Set the IncludeNavigationProperties connection property to true in order to use this stored procedure.
Input¶
Name | Type | Required | Description |
---|---|---|---|
FromId | String | False | The ID of the entity you are removing an associations for. |
UrlId | String | False | An alternative to specifying the FromId. This is the complete URL to the resource you are removing an association for. It is required to be specified in the case that the navigation property is an abstract, or to specify more specific child types where the navigation property entity type is used as a basetype. |
FromTable | String | True | The table where the entity comes from that you are removing an association for. For example, if the FromId was from a table called Customers, set this parameter to: Customers. |
ToNavigationProperty | String | True | The navigation property you are removing an association on. It can be obtained from ListNavigationProperties. |
ToId | String | False | The ID of the navigation entity. This will come from the table associated with the navigation property. |
ToUrlId | String | False | An alternative to specifying the ToId. This is the complete URL to the resource to be associated. It is required to be specified in the case that the navigation property is an abstract, or to specify more specific child types where the navigation property entity type is used as a basetype. |
System Tables¶
You can query the system tables described in this section to access schema information, information on data source functionality, and batch operation statistics.
Schema Tables¶
The following tables return database metadata for Microsoft Dynamics 365:
- sys_catalogs: Lists the available databases.
- sys_schemas: Lists the available schemas.
- sys_tables: Lists the available tables and views.
- sys_tablecolumns: Describes the columns of the available tables and views.
- sys_procedures: Describes the available stored procedures.
- sys_procedureparameters: Describes stored procedure parameters.
- sys_keycolumns: Describes the primary and foreign keys.
- sys_indexes: Describes the available indexes.
Data Source Tables¶
The following tables return information about how to connect to and query the data source:
- sys_connection_props: Returns information on the available connection properties.
- sys_sqlinfo: Describes the SELECT queries that the connector can offload to the data source.
Query Information Tables¶
The following table returns query statistics for data modification queries, including batch operations:
- sys_identity: Returns information about batch operations or single updates.
sys_catalogs¶
Lists the available databases.
The following query retrieves all databases determined by the connection string:
SELECT * FROM sys_catalogs
Columns¶
Name | Type | Description |
---|---|---|
CatalogName | String | The database name. |
sys_schemas¶
Lists the available schemas.
The following query retrieves all available schemas:
SELECT * FROM sys_schemas
Columns¶
Name | Type | Description |
---|---|---|
CatalogName | String | The database name. |
SchemaName | String | The schema name. |
sys_tables¶
Lists the available tables.
The following query retrieves the available tables and views:
SELECT * FROM sys_tables
Columns¶
Name | Type | Description |
---|---|---|
CatalogName | String | The database containing the table or view. |
SchemaName | String | The schema containing the table or view. |
TableName | String | The name of the table or view. |
TableType | String | The table type (table or view). |
Description | String | A description of the table or view. |
IsUpdateable | Boolean | Whether the table can be updated. |
sys_tablecolumns¶
Describes the columns of the available tables and views.
The following query returns the columns and data types for the GoalHeadings table:
SELECT ColumnName, DataTypeName FROM sys_tablecolumns WHERE TableName='GoalHeadings'
Columns¶
Name | Type | Description |
---|---|---|
CatalogName | String | The name of the database containing the table or view. |
SchemaName | String | The schema containing the table or view. |
TableName | String | The name of the table or view containing the column. |
ColumnName | String | The column name. |
DataTypeName | String | The data type name. |
DataType | Int32 | An integer indicating the data type. This value is determined at run time based on the environment. |
Length | Int32 | The storage size of the column. |
DisplaySize | Int32 | The designated column's normal maximum width in characters. |
NumericPrecision | Int32 | The maximum number of digits in numeric data. The column length in characters for character and date-time data. |
NumericScale | Int32 | The column scale or number of digits to the right of the decimal point. |
IsNullable | Boolean | Whether the column can contain null. |
Description | String | A brief description of the column. |
Ordinal | Int32 | The sequence number of the column. |
IsAutoIncrement | String | Whether the column value is assigned in fixed increments. |
IsGeneratedColumn | String | Whether the column is generated. |
IsHidden | Boolean | Whether the column is hidden. |
IsArray | Boolean | Whether the column is an array. |
IsReadOnly | Boolean | Whether the column is read-only. |
IsKey | Boolean | Indicates whether a field returned from sys_tablecolumns is the primary key of the table. |
sys_procedures¶
Lists the available stored procedures.
The following query retrieves the available stored procedures:
SELECT * FROM sys_procedures
Columns¶
Name | Type | Description |
---|---|---|
CatalogName | String | The database containing the stored procedure. |
SchemaName | String | The schema containing the stored procedure. |
ProcedureName | String | The name of the stored procedure. |
Description | String | A description of the stored procedure. |
ProcedureType | String | The type of the procedure, such as PROCEDURE or FUNCTION. |
sys_procedureparameters¶
Describes stored procedure parameters.
The following query returns information about all of the input parameters for the GetOAuthAccessToken stored procedure:
SELECT * FROM sys_procedureparameters WHERE ProcedureName='GetOAuthAccessToken' AND Direction=1 OR Direction=2
Columns¶
Name | Type | Description |
---|---|---|
CatalogName | String | The name of the database containing the stored procedure. |
SchemaName | String | The name of the schema containing the stored procedure. |
ProcedureName | String | The name of the stored procedure containing the parameter. |
ColumnName | String | The name of the stored procedure parameter. |
Direction | Int32 | An integer corresponding to the type of the parameter: input (1), input/output (2), or output(4). input/output type parameters can be both input and output parameters. |
DataTypeName | String | The name of the data type. |
DataType | Int32 | An integer indicating the data type. This value is determined at run time based on the environment. |
Length | Int32 | The number of characters allowed for character data. The number of digits allowed for numeric data. |
NumericPrecision | Int32 | The maximum precision for numeric data. The column length in characters for character and date-time data. |
NumericScale | Int32 | The number of digits to the right of the decimal point in numeric data. |
IsNullable | Boolean | Whether the parameter can contain null. |
IsRequired | Boolean | Whether the parameter is required for execution of the procedure. |
IsArray | Boolean | Whether the parameter is an array. |
Description | String | The description of the parameter. |
Ordinal | Int32 | The index of the parameter. |
sys_keycolumns¶
Describes the primary and foreign keys.
The following query retrieves the primary key for the GoalHeadings table:
SELECT * FROM sys_keycolumns WHERE IsKey='True' AND TableName='GoalHeadings'
Columns¶
Name | Type | Description |
---|---|---|
CatalogName | String | The name of the database containing the key. |
SchemaName | String | The name of the schema containing the key. |
TableName | String | The name of the table containing the key. |
ColumnName | String | The name of the key column. |
IsKey | Boolean | Whether the column is a primary key in the table referenced in the TableName field. |
IsForeignKey | Boolean | Whether the column is a foreign key referenced in the TableName field. |
PrimaryKeyName | String | The name of the primary key. |
ForeignKeyName | String | The name of the foreign key. |
ReferencedCatalogName | String | The database containing the primary key. |
ReferencedSchemaName | String | The schema containing the primary key. |
ReferencedTableName | String | The table containing the primary key. |
ReferencedColumnName | String | The column name of the primary key. |
sys_foreignkeys¶
Describes the foreign keys.
The following query retrieves all foreign keys which refer to other tables:
SELECT * FROM sys_foreignkeys WHERE ForeignKeyType = 'FOREIGNKEY_TYPE_IMPORT'
Columns¶
Name | Type | Description |
---|---|---|
CatalogName | String | The name of the database containing the key. |
SchemaName | String | The name of the schema containing the key. |
TableName | String | The name of the table containing the key. |
ColumnName | String | The name of the key column. |
PrimaryKeyName | String | The name of the primary key. |
ForeignKeyName | String | The name of the foreign key. |
ReferencedCatalogName | String | The database containing the primary key. |
ReferencedSchemaName | String | The schema containing the primary key. |
ReferencedTableName | String | The table containing the primary key. |
ReferencedColumnName | String | The column name of the primary key. |
ForeignKeyType | String | Designates whether the foreign key is an import (points to other tables) or export (referenced from other tables) key. |
sys_primarykeys¶
Describes the primary keys.
The following query retrieves the primary keys from all tables and views:
SELECT * FROM sys_primarykeys
Columns¶
Name | Type | Description |
---|---|---|
CatalogName | String | The name of the database containing the key. |
SchemaName | String | The name of the schema containing the key. |
TableName | String | The name of the table containing the key. |
ColumnName | String | The name of the key column. |
KeySeq | String | The sequence number of the primary key. |
KeyName | String | The name of the primary key. |
sys_indexes¶
Describes the available indexes. By filtering on indexes, you can write more selective queries with faster query response times.
The following query retrieves all indexes that are not primary keys:
SELECT * FROM sys_indexes WHERE IsPrimary='false'
Columns¶
Name | Type | Description |
---|---|---|
CatalogName | String | The name of the database containing the index. |
SchemaName | String | The name of the schema containing the index. |
TableName | String | The name of the table containing the index. |
IndexName | String | The index name. |
ColumnName | String | The name of the column associated with the index. |
IsUnique | Boolean | True if the index is unique. False otherwise. |
IsPrimary | Boolean | True if the index is a primary key. False otherwise. |
Type | Int16 | An integer value corresponding to the index type: statistic (0), clustered (1), hashed (2), or other (3). |
SortOrder | String | The sort order: A for ascending or D for descending. |
OrdinalPosition | Int16 | The sequence number of the column in the index. |
sys_connection_props¶
Returns information on the available connection properties and those set in the connection string.
When querying this table, the config connection string should be used:
jdbc:cdata:dynamics365:config:
This connection string enables you to query this table without a valid connection.
The following query retrieves all connection properties that have been set in the connection string or set through a default value:
SELECT * FROM sys_connection_props WHERE Value <> ''
Columns¶
Name | Type | Description |
---|---|---|
Name | String | The name of the connection property. |
ShortDescription | String | A brief description. |
Type | String | The data type of the connection property. |
Default | String | The default value if one is not explicitly set. |
Values | String | A comma-separated list of possible values. A validation error is thrown if another value is specified. |
Value | String | The value you set or a preconfigured default. |
Required | Boolean | Whether the property is required to connect. |
Category | String | The category of the connection property. |
IsSessionProperty | String | Whether the property is a session property, used to save information about the current connection. |
Sensitivity | String | The sensitivity level of the property. This informs whether the property is obfuscated in logging and authentication forms. |
PropertyName | String | A camel-cased truncated form of the connection property name. |
Ordinal | Int32 | The index of the parameter. |
CatOrdinal | Int32 | The index of the parameter category. |
Hierarchy | String | Shows dependent properties associated that need to be set alongside this one. |
Visible | Boolean | Informs whether the property is visible in the connection UI. |
ETC | String | Various miscellaneous information about the property. |
sys_sqlinfo¶
Describes the SELECT query processing that the connector can offload to the data source.
Discovering the Data Source's SELECT Capabilities¶
Below is an example data set of SQL capabilities. Some aspects of SELECT functionality are returned in a comma-separated list if supported; otherwise, the column contains NO.
Name | Description | Possible Values |
---|---|---|
AGGREGATE_FUNCTIONS | Supported aggregation functions. | AVG , COUNT , MAX , MIN , SUM , DISTINCT |
COUNT | Whether COUNT function is supported. | YES , NO |
IDENTIFIER_QUOTE_OPEN_CHAR | The opening character used to escape an identifier. | [ |
IDENTIFIER_QUOTE_CLOSE_CHAR | The closing character used to escape an identifier. | ] |
SUPPORTED_OPERATORS | A list of supported SQL operators. | = , > , < , >= , <= , <> , != , LIKE , NOT LIKE , IN , NOT IN , IS NULL , IS NOT NULL , AND , OR |
GROUP_BY | Whether GROUP BY is supported, and, if so, the degree of support. | NO , NO_RELATION , EQUALS_SELECT , SQL_GB_COLLATE |
STRING_FUNCTIONS | Supported string functions. | LENGTH , CHAR , LOCATE , REPLACE , SUBSTRING , RTRIM , LTRIM , RIGHT , LEFT , UCASE , SPACE , SOUNDEX , LCASE , CONCAT , ASCII , REPEAT , OCTET , BIT , POSITION , INSERT , TRIM , UPPER , REGEXP , LOWER , DIFFERENCE , CHARACTER , SUBSTR , STR , REVERSE , PLAN , UUIDTOSTR , TRANSLATE , TRAILING , TO , STUFF , STRTOUUID , STRING , SPLIT , SORTKEY , SIMILAR , REPLICATE , PATINDEX , LPAD , LEN , LEADING , KEY , INSTR , INSERTSTR , HTML , GRAPHICAL , CONVERT , COLLATION , CHARINDEX , BYTE |
NUMERIC_FUNCTIONS | Supported numeric functions. | ABS , ACOS , ASIN , ATAN , ATAN2 , CEILING , COS , COT , EXP , FLOOR , LOG , MOD , SIGN , SIN , SQRT , TAN , PI , RAND , DEGREES , LOG10 , POWER , RADIANS , ROUND , TRUNCATE |
TIMEDATE_FUNCTIONS | Supported date/time functions. | NOW , CURDATE , DAYOFMONTH , DAYOFWEEK , DAYOFYEAR , MONTH , QUARTER , WEEK , YEAR , CURTIME , HOUR , MINUTE , SECOND , TIMESTAMPADD , TIMESTAMPDIFF , DAYNAME , MONTHNAME , CURRENT_DATE , CURRENT_TIME , CURRENT_TIMESTAMP , EXTRACT |
REPLICATION_SKIP_TABLES | Indicates tables skipped during replication. | |
REPLICATION_TIMECHECK_COLUMNS | A string array containing a list of columns which will be used to check for (in the given order) to use as a modified column during replication. | |
IDENTIFIER_PATTERN | String value indicating what string is valid for an identifier. | |
SUPPORT_TRANSACTION | Indicates if the provider supports transactions such as commit and rollback. | YES , NO |
DIALECT | Indicates the SQL dialect to use. | |
KEY_PROPERTIES | Indicates the properties which identify the uniform database. | |
SUPPORTS_MULTIPLE_SCHEMAS | Indicates if multiple schemas may exist for the provider. | YES , NO |
SUPPORTS_MULTIPLE_CATALOGS | Indicates if multiple catalogs may exist for the provider. | YES , NO |
DATASYNCVERSION | The Data Sync version needed to access this driver. | Standard , Starter , Professional , Enterprise |
DATASYNCCATEGORY | The Data Sync category of this driver. | Source , Destination , Cloud Destination |
SUPPORTSENHANCEDSQL | Whether enhanced SQL functionality beyond what is offered by the API is supported. | TRUE , FALSE |
SUPPORTS_BATCH_OPERATIONS | Whether batch operations are supported. | YES , NO |
SQL_CAP | All supported SQL capabilities for this driver. | SELECT , INSERT , DELETE , UPDATE , TRANSACTIONS , ORDERBY , OAUTH , ASSIGNEDID , LIMIT , LIKE , BULKINSERT , COUNT , BULKDELETE , BULKUPDATE , GROUPBY , HAVING , AGGS , OFFSET , REPLICATE , COUNTDISTINCT , JOINS , DROP , CREATE , DISTINCT , INNERJOINS , SUBQUERIES , ALTER , MULTIPLESCHEMAS , GROUPBYNORELATION , OUTERJOINS , UNIONALL , UNION , UPSERT , GETDELETED , CROSSJOINS , GROUPBYCOLLATE , MULTIPLECATS , FULLOUTERJOIN , MERGE , JSONEXTRACT , BULKUPSERT , SUM , SUBQUERIESFULL , MIN , MAX , JOINSFULL , XMLEXTRACT , AVG , MULTISTATEMENTS , FOREIGNKEYS , CASE , LEFTJOINS , COMMAJOINS , WITH , LITERALS , RENAME , NESTEDTABLES , EXECUTE , BATCH , BASIC , INDEX |
PREFERRED_CACHE_OPTIONS | A string value specifies the preferred cacheOptions. | |
ENABLE_EF_ADVANCED_QUERY | Indicates if the driver directly supports advanced queries coming from Entity Framework. If not, queries will be handled client side. | YES , NO |
PSEUDO_COLUMNS | A string array indicating the available pseudo columns. | |
MERGE_ALWAYS | If the value is true, The Merge Mode is forcibly executed in Data Sync. | TRUE , FALSE |
REPLICATION_MIN_DATE_QUERY | A select query to return the replicate start datetime. | |
REPLICATION_MIN_FUNCTION | Allows a provider to specify the formula name to use for executing a server side min. | |
REPLICATION_START_DATE | Allows a provider to specify a replicate startdate. | |
REPLICATION_MAX_DATE_QUERY | A select query to return the replicate end datetime. | |
REPLICATION_MAX_FUNCTION | Allows a provider to specify the formula name to use for executing a server side max. | |
IGNORE_INTERVALS_ON_INITIAL_REPLICATE | A list of tables which will skip dividing the replicate into chunks on the initial replicate. | |
CHECKCACHE_USE_PARENTID | Indicates whether the CheckCache statement should be done against the parent key column. | TRUE , FALSE |
CREATE_SCHEMA_PROCEDURES | Indicates stored procedures that can be used for generating schema files. |
The following query retrieves the operators that can be used in the WHERE clause:
SELECT * FROM sys_sqlinfo WHERE Name = 'SUPPORTED_OPERATORS'
Note that individual tables may have different limitations or requirements on the WHERE clause; refer to the Data Model section for more information.
Columns¶
Name | Type | Description |
---|---|---|
NAME | String | A component of SQL syntax, or a capability that can be processed on the server. |
VALUE | String | Detail on the supported SQL or SQL syntax. |
sys_identity¶
Returns information about attempted modifications.
The following query retrieves the Ids of the modified rows in a batch operation:
SELECT * FROM sys_identity
Columns¶
Name | Type | Description |
---|---|---|
Id | String | The database-generated ID returned from a data modification operation. |
Batch | String | An identifier for the batch. 1 for a single operation. |
Operation | String | The result of the operation in the batch: INSERTED, UPDATED, or DELETED. |
Message | String | SUCCESS or an error message if the update in the batch failed. |
Data Type Mapping¶
Data Type Mappings¶
The connector maps types from the data source to the corresponding data type available in the schema. The table below documents these mappings.
Microsoft Dynamics 365 (OData V4) | Schema |
---|---|
Edm.Binary | binary |
Edm.Boolean | bool |
Edm.Date | datetime |
Edm.DateTimeOffset | datetime |
Edm.Decimal | decimal |
Edm.Double | double |
Edm.Guid | guid |
Edm.Int32 | int |
Edm.String | string |
Edm.TimeOfDay | time |
Advanced Configurations Properties¶
The advanced configurations properties are the various options that can be used to establish a connection. This section provides a complete list of the options you can configure. Click the links for further details.
Property | Description |
---|---|
AuthScheme | The type of authentication to use when connecting to Microsoft Dynamics 365. |
OrganizationURL | The URL to your Dynamics 365 organization. For instance, https://abc123.cloudax.dynamics.com/ . |
Edition | The edition of Microsoft Dynamics 365 being used. |
ADFSServer | The ADFS Server used for authentication. Only used with FinOpsOnPremise edition. |
ApiVersion | The API version being used. This can be specified to access a new version of the API once it is released. |
Property | Description |
---|---|
AzureTenant | The Microsoft Online tenant being used to access data. If not specified, your default tenant is used. |
AzureEnvironment | The Azure Environment to use when establishing a connection. |
Property | Description |
---|---|
InitiateOAuth | Set this property to initiate the process to obtain or refresh the OAuth access token when you connect. |
OAuthClientId | The client ID assigned when you register your application with an OAuth authorization server. |
OAuthClientSecret | The client secret assigned when you register your application with an OAuth authorization server. |
OAuthAccessToken | The access token for connecting using OAuth. |
OAuthSettingsLocation | The location of the settings file where OAuth values are saved when InitiateOAuth is set to GETANDREFRESH or REFRESH . Alternatively, you can hold this location in memory by specifying a value starting with 'memory://' . |
CallbackURL | The OAuth callback URL to return to when authenticating. This value must match the callback URL you specify in your app settings. |
OAuthGrantType | The grant type for the OAuth flow. |
OAuthVerifier | The verifier code returned from the OAuth authorization URL. |
OAuthRefreshToken | The OAuth refresh token for the corresponding OAuth access token. |
OAuthExpiresIn | The lifetime in seconds of the OAuth AccessToken. |
OAuthTokenTimestamp | The Unix epoch timestamp in milliseconds when the current Access Token was created. |
Property | Description |
---|---|
OAuthJWTCert | The JWT Certificate store. |
OAuthJWTCertType | The type of key store containing the JWT Certificate. |
OAuthJWTCertPassword | The password for the OAuth JWT certificate. |
OAuthJWTCertSubject | The subject of the OAuth JWT certificate. |
OAuthJWTIssuer | The issuer of the Java Web Token. |
OAuthJWTSubject | The user subject for which the application is requesting delegated access. |
Property | Description |
---|---|
SSLServerCert | The certificate to be accepted from the server when connecting using TLS/SSL. |
Property | Description |
---|---|
Location | A path to the directory that contains the schema files defining tables, views, and stored procedures. |
BrowsableSchemas | This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA, SchemaB, SchemaC. |
Tables | This property restricts the tables reported to a subset of the available tables. For example, Tables=TableA, TableB, TableC. |
Views | Restricts the views reported to a subset of the available tables. For example, Views=ViewA, ViewB, ViewC. |
Property | Description |
---|---|
AllowDuplicateRecords | Indicates if the driver should check the configured duplicate detection rules. |
CrossCompany | Whether to pull data for all companies or just the user's default company. |
CustomUrlParams | The custom query string to be included in the request. |
IncludeFormattedValues | Indicates if columns that hold formatted values should be exposed. |
IncludeLookUpLogicalName | Indicates if the referenced entity name for a LookUp field should be exposed. |
IncludeNavigationProperties | A boolean indicating if navigation properties should be included in the column listing. |
MaxRows | Limits the number of rows returned when no aggregation or GROUP BY is used in the query. This takes precedence over LIMIT clauses. |
Other | These hidden properties are used only in specific use cases. |
Pagesize | The maximum number of results to return per page from Microsoft Dynamics 365. |
PseudoColumns | This property indicates whether or not to include pseudo columns as columns to the table. |
Timeout | The value in seconds until the timeout error is thrown, canceling the operation. |
UseClientSidePaging | Whether or not the ADO.NET Provider for Microsoft Dynamics 365 should use multiple threads with client side paging. |
UseDynamicStoredProcedures | A boolean indicating if dynamic stored procedures should be exposed. |
UserDefinedViews | A filepath pointing to the JSON configuration file containing your custom views. |
Authentication¶
This section provides a complete list of authentication properties you can configure.
Property | Description |
---|---|
AuthScheme | The type of authentication to use when connecting to Microsoft Dynamics 365. |
OrganizationURL | The URL to your Dynamics 365 organization. For instance, https://abc123.cloudax.dynamics.com/ . |
Edition | The edition of Microsoft Dynamics 365 being used. |
ADFSServer | The ADFS Server used for authentication. Only used with FinOpsOnPremise edition. |
ApiVersion | The API version being used. This can be specified to access a new version of the API once it is released. |
AuthScheme¶
The type of authentication to use when connecting to Microsoft Dynamics 365.
Data Type¶
string
Default Value¶
AzureAD
Remarks¶
- AzureAD: Set this to perform Azure Active Directory OAuth authentication.
- AzureMSI: Set this to automatically obtain Managed Service Identity credentials when running on an Azure VM.
- AzureServicePrincipal: Set this to authenticate as an Azure Service Principal using a Client Secret.
- AzureServicePrincipalCert: Set this to authenticate as an Azure Service Principal using a Certificate.
OrganizationURL¶
The URL to your Dynamics 365 organization. For instance, https://abc123.cloudax.dynamics.com/
.
Data Type¶
string
Default Value¶
""
Remarks¶
This may also be known as the resource.
For Edition=HumanResources, the value should be like: https://{cluster}.hr.talent.dynamics.com/namespaces/{namespace_guid}/
Edition¶
The edition of Microsoft Dynamics 365 being used.
Data Type¶
string
Default Value¶
FinOpsOnline
Remarks¶
Currently for Microsoft Dynamics 365 Finance and Operations, further FinOpsOnline and FinOpsOnPremise are available. If specifying FinOpsOnPremise, then the ADFSServer must also be specified.
ADFSServer¶
The ADFS Server used for authentication. Only used with FinOpsOnPremise edition.
Data Type¶
string
Default Value¶
""
Remarks¶
Should only be specified when Edition is set to FinOpsOnPremise. Otherwise this property is ignored.
ApiVersion¶
The API version being used. This can be specified to access a new version of the API once it is released.
Data Type¶
string
Default Value¶
9.0
Remarks¶
The API version being used. This can be specified to access a new version of the API once it is released. Otherwise, you can use the default.
Note: This property only applies when Edition is set to either CustomerService, FieldService, Marketing, ProjectOperations or Sales.
Azure Authentication¶
This section provides a complete list of Azure authentication properties you can configure.
Property | Description |
---|---|
AzureTenant | The Microsoft Online tenant being used to access data. If not specified, your default tenant is used. |
AzureEnvironment | The Azure Environment to use when establishing a connection. |
AzureTenant¶
The Microsoft Online tenant being used to access data. If not specified, your default tenant is used.
Data Type¶
string
Default Value¶
""
Remarks¶
The Microsoft Online tenant being used to access data. For instance, contoso.onmicrosoft.com. Alternatively, specify the tenant Id. This value is the directory ID in the Azure Portal > Azure Active Directory > Properties.
Typically it is not necessary to specify the Tenant. This can be automatically determined by Microsoft when using the OAuthGrantType set to CODE (default). However, it may fail in the case that the user belongs to multiple tenants. For instance, if an Admin of domain A invites a user of domain B to be a guest user. The user will now belong to both tenants. It is a good practice to specify the Tenant, although in general things should normally work without having to specify it.
The AzureTenant
is required when setting OAuthGrantType to CLIENT. When using client credentials, there is no user context. The credentials are taken from the context of the app itself. While Microsoft still allows client credentials to be obtained without specifying which Tenant, it has a much lower probability of picking the specific tenant you want to work with. For this reason, we require AzureTenant
to be explicitly stated for all client credentials connections to ensure you get credentials that are applicable for the domain you intend to connect to.
AzureEnvironment¶
The Azure Environment to use when establishing a connection.
Possible Values¶
GLOBAL
, CHINA
, USGOVT
, USGOVTDOD
Data Type¶
string
Default Value¶
GLOBAL
Remarks¶
In most cases, leaving the environment set to global will work. However, if your Azure Account has been added to a different environment, the AzureEnvironment
may be used to specify which environment. The available values are GLOBAL, CHINA, USGOVT, USGOVTDOD.
OAuth¶
This section provides a complete list of OAuth properties you can configure.
Property | Description |
---|---|
InitiateOAuth | Set this property to initiate the process to obtain or refresh the OAuth access token when you connect. |
OAuthClientId | The client ID assigned when you register your application with an OAuth authorization server. |
OAuthClientSecret | The client secret assigned when you register your application with an OAuth authorization server. |
OAuthAccessToken | The access token for connecting using OAuth. |
OAuthSettingsLocation | The location of the settings file where OAuth values are saved when InitiateOAuth is set to GETANDREFRESH or REFRESH . Alternatively, you can hold this location in memory by specifying a value starting with 'memory://' . |
CallbackURL | The OAuth callback URL to return to when authenticating. This value must match the callback URL you specify in your app settings. |
OAuthGrantType | The grant type for the OAuth flow. |
OAuthVerifier | The verifier code returned from the OAuth authorization URL. |
OAuthRefreshToken | The OAuth refresh token for the corresponding OAuth access token. |
OAuthExpiresIn | The lifetime in seconds of the OAuth AccessToken. |
OAuthTokenTimestamp | The Unix epoch timestamp in milliseconds when the current Access Token was created. |
InitiateOAuth¶
Set this property to initiate the process to obtain or refresh the OAuth access token when you connect.
Possible Values¶
OFF
, GETANDREFRESH
, REFRESH
Data Type¶
string
Default Value¶
OFF
Remarks¶
The following options are available:
OFF
: Indicates that the OAuth flow will be handled entirely by the user. An OAuthAccessToken will be required to authenticate.GETANDREFRESH
: Indicates that the entire OAuth Flow will be handled by the connector. If no token currently exists, it will be obtained by prompting the user via the browser. If a token exists, it will be refreshed when applicable.REFRESH
: Indicates that the connector will only handle refreshing the OAuthAccessToken. The user will never be prompted by the connector to authenticate via the browser. The user must handle obtaining the OAuthAccessToken and OAuthRefreshToken initially.
OAuthClientId¶
The client ID assigned when you register your application with an OAuth authorization server.
Data Type¶
string
Default Value¶
""
Remarks¶
As part of registering an OAuth application, you will receive the OAuthClientId
value, sometimes also called a consumer key, and a client secret, the OAuthClientSecret.
OAuthClientSecret¶
The client secret assigned when you register your application with an OAuth authorization server.
Data Type¶
string
Default Value¶
""
Remarks¶
As part of registering an OAuth application, you will receive the OAuthClientId, also called a consumer key. You will also receive a client secret, also called a consumer secret. Set the client secret in the OAuthClientSecret
property.
OAuthAccessToken¶
The access token for connecting using OAuth.
Data Type¶
string
Default Value¶
""
Remarks¶
The OAuthAccessToken
property is used to connect using OAuth. The OAuthAccessToken
is retrieved from the OAuth server as part of the authentication process. It has a server-dependent timeout and can be reused between requests.
The access token is used in place of your user name and password. The access token protects your credentials by keeping them on the server.
OAuthSettingsLocation¶
The location of the settings file where OAuth values are saved when InitiateOAuth is set to GETANDREFRESH or REFRESH . Alternatively, you can hold this location in memory by specifying a value starting with 'memory://'
.
Data Type¶
string
Default Value¶
%APPDATA%\Dynamics365 Data Provider\OAuthSettings.txt
Remarks¶
When InitiateOAuth is set to GETANDREFRESH
or REFRESH
, the connector saves OAuth values to avoid requiring the user to manually enter OAuth connection properties and to allow the credentials to be shared across connections or processes.
Instead of specifying a file path, you can use memory storage. Memory locations are specified by using a value starting with 'memory://'
followed by a unique identifier for that set of credentials (for example, memory://user1). The identifier can be anything you choose but should be unique to the user. Unlike file-based storage, where credentials persist across connections, memory storage loads the credentials into static memory, and the credentials are shared between connections using the same identifier for the life of the process. To persist credentials outside the current process, you must manually store the credentials prior to closing the connection. This enables you to set them in the connection when the process is started again. You can retrieve OAuth property values with a query to the sys_connection_props
system table. If there are multiple connections using the same credentials, the properties are read from the previously closed connection.
The default location is "%APPDATA%\Dynamics365 Data Provider\OAuthSettings.txt" with %APPDATA%
set to the user's configuration directory. The default values are
- Windows: "
register://%DSN
" - Unix: "%AppData%..."
- Mac: "%AppData%..."
where DSN is the name of the current DSN used in the open connection.
The following table lists the value of %APPDATA%
by OS:
Platform | %APPDATA% |
---|---|
Windows | The value of the APPDATA environment variable |
Mac | ~/Library/Application Support |
Linux | ~/.config |
CallbackURL¶
The OAuth callback URL to return to when authenticating. This value must match the callback URL you specify in your app settings.
Data Type¶
string
Default Value¶
""
Remarks¶
During the authentication process, the OAuth authorization server redirects the user to this URL. This value must match the callback URL you specify in your app settings.
OAuthGrantType¶
The grant type for the OAuth flow.
Possible Values¶
CODE
, CLIENT
, PASSWORD
Data Type¶
string
Default Value¶
CLIENT
Remarks¶
The following options are available: CODE,CLIENT,PASSWORD
OAuthVerifier¶
The verifier code returned from the OAuth authorization URL.
Data Type¶
string
Default Value¶
""
Remarks¶
The verifier code returned from the OAuth authorization URL. This can be used on systems where a browser cannot be launched such as headless systems.
Authentication on Headless Machines¶
See to obtain the OAuthVerifier
value.
Set OAuthSettingsLocation along with OAuthVerifier
. When you connect, the connector exchanges the OAuthVerifier
for the OAuth authentication tokens and saves them, encrypted, to the specified location. Set InitiateOAuth to GETANDREFRESH to automate the exchange.
Once the OAuth settings file has been generated, you can remove OAuthVerifier
from the connection properties and connect with OAuthSettingsLocation set.
To automatically refresh the OAuth token values, set OAuthSettingsLocation and additionally set InitiateOAuth to REFRESH.
OAuthRefreshToken¶
The OAuth refresh token for the corresponding OAuth access token.
Data Type¶
string
Default Value¶
""
Remarks¶
The OAuthRefreshToken
property is used to refresh the OAuthAccessToken when using OAuth authentication.
OAuthExpiresIn¶
The lifetime in seconds of the OAuth AccessToken.
Data Type¶
string
Default Value¶
""
Remarks¶
Pair with OAuthTokenTimestamp to determine when the AccessToken will expire.
OAuthTokenTimestamp¶
The Unix epoch timestamp in milliseconds when the current Access Token was created.
Data Type¶
string
Default Value¶
""
Remarks¶
Pair with OAuthExpiresIn to determine when the AccessToken will expire.
JWT OAuth¶
This section provides a complete list of JWT OAuth properties you can configure.
Property | Description |
---|---|
OAuthJWTCert | The JWT Certificate store. |
OAuthJWTCertType | The type of key store containing the JWT Certificate. |
OAuthJWTCertPassword | The password for the OAuth JWT certificate. |
OAuthJWTCertSubject | The subject of the OAuth JWT certificate. |
OAuthJWTIssuer | The issuer of the Java Web Token. |
OAuthJWTSubject | The user subject for which the application is requesting delegated access. |
OAuthJWTCert¶
The JWT Certificate store.
Data Type¶
string
Default Value¶
""
Remarks¶
The name of the certificate store for the client certificate.
The OAuthJWTCertType field specifies the type of the certificate store specified by OAuthJWTCert
. If the store is password protected, specify the password in OAuthJWTCertPassword.
OAuthJWTCert
is used in conjunction with the OAuthJWTCertSubject
field in order to specify client certificates. If OAuthJWTCert
has a value, and OAuthJWTCertSubject is set, a search for a certificate is initiated. Please refer to the OAuthJWTCertSubject field for details.
Designations of certificate stores are platform-dependent.
The following are designations of the most common User and Machine certificate stores in Windows:
Property | Description |
---|---|
MY | A certificate store holding personal certificates with their associated private keys. |
CA | Certifying authority certificates. |
ROOT | Root certificates. |
SPC | Software publisher certificates. |
In Java, the certificate store normally is a file containing certificates and optional private keys.
When the certificate store type is PFXFile, this property must be set to the name of the file. When the type is PFXBlob, the property must be set to the binary contents of a PFX file (i.e. PKCS12 certificate store).
OAuthJWTCertType¶
The type of key store containing the JWT Certificate.
Data Type¶
string
Default Value¶
USER
Remarks¶
This property can take one of the following values:
Property | Description |
---|---|
USER | For Windows, this specifies that the certificate store is a certificate store owned by the current user. Note: This store type is not available in Java. |
MACHINE | For Windows, this specifies that the certificate store is a machine store. Note: this store type is not available in Java. |
PFXFILE | The certificate store is the name of a PFX (PKCS12) file containing certificates. |
PFXBLOB | The certificate store is a string (base-64-encoded) representing a certificate store in PFX (PKCS12) format. |
JKSFILE | The certificate store is the name of a Java key store (JKS) file containing certificates. Note: this store type is only available in Java. |
JKSBLOB | The certificate store is a string (base-64-encoded) representing a certificate store in Java key store (JKS) format. Note: this store type is only available in Java. |
PEMKEY_FILE | The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate. |
PEMKEY_BLOB | The certificate store is a string (base64-encoded) that contains a private key and an optional certificate. |
PUBLIC_KEY_FILE | The certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate. |
PUBLIC_KEY_BLOB | The certificate store is a string (base-64-encoded) that contains a PEM- or DER-encoded public key certificate. |
SSHPUBLIC_KEY_FILE | The certificate store is the name of a file that contains an SSH-style public key. |
SSHPUBLIC_KEY_BLOB | The certificate store is a string (base-64-encoded) that contains an SSH-style public key. |
P7BFILE | The certificate store is the name of a PKCS7 file containing certificates. |
PPKFILE | The certificate store is the name of a file that contains a PPK (PuTTY Private Key). |
XMLFILE | The certificate store is the name of a file that contains a certificate in XML format. |
XMLBLOB | The certificate store is a string that contains a certificate in XML format. |
OAuthJWTCertPassword¶
The password for the OAuth JWT certificate.
Data Type¶
string
Default Value¶
""
Remarks¶
If the certificate store is of a type that requires a password, this property is used to specify that password in order to open the certificate store.
OAuthJWTCertSubject¶
The subject of the OAuth JWT certificate.
Data Type¶
string
Default Value¶
*
Remarks¶
When loading a certificate the subject is used to locate the certificate in the store.
If an exact match is not found, the store is searched for subjects containing the value of the property.
If a match is still not found, the property is set to an empty string, and no certificate is selected.
The special value "*" picks the first certificate in the certificate store.
The certificate subject is a comma separated list of distinguished name fields and values. For instance "CN=www.server.com, OU=test, C=US, E=example@jbexample.com". Common fields and their meanings are displayed below.
Field | Meaning |
---|---|
CN | Common Name. This is commonly a host name like www.server.com. |
O | Organization |
OU | Organizational Unit |
L | Locality |
S | State |
C | Country |
E | Email Address |
If a field value contains a comma it must be quoted.
OAuthJWTIssuer¶
The issuer of the Java Web Token.
Data Type¶
string
Default Value¶
""
Remarks¶
The issuer of the Java Web Token. This is typically either the Client ID or Email Address of the OAuth Application.
OAuthJWTSubject¶
The user subject for which the application is requesting delegated access.
Data Type¶
string
Default Value¶
""
Remarks¶
The user subject for which the application is requesting delegated access. Typically, the user account name or email address.
SSL¶
This section provides a complete list of SSL properties you can configure.
Property | Description |
---|---|
SSLServerCert | The certificate to be accepted from the server when connecting using TLS/SSL. |
SSLServerCert¶
The certificate to be accepted from the server when connecting using TLS/SSL.
Data Type¶
string
Default Value¶
""
Remarks¶
If using a TLS/SSL connection, this property can be used to specify the TLS/SSL certificate to be accepted from the server. Any other certificate that is not trusted by the machine is rejected.
This property can take the following forms:
Description | Example |
---|---|
A full PEM Certificate (example shortened for brevity) | -----BEGIN CERTIFICATE----- MIIChTCCAe4CAQAwDQYJKoZIhv......Qw== -----END CERTIFICATE----- |
A path to a local file containing the certificate | C:\\cert.cer |
The public key (example shortened for brevity) | -----BEGIN RSA PUBLIC KEY----- MIGfMA0GCSq......AQAB -----END RSA PUBLIC KEY----- |
The MD5 Thumbprint (hex values can also be either space or colon separated) | ecadbdda5a1529c58a1e9e09828d70e4 |
The SHA1 Thumbprint (hex values can also be either space or colon separated) | 34a929226ae0819f2ec14b4a3d904f801cbb150d |
If not specified, any certificate trusted by the machine is accepted.
Certificates are validated as trusted by the machine based on the System's trust store. The trust store used is the 'javax.net.ssl.trustStore' value specified for the system. If no value is specified for this property, Java's default trust store is used (for example, JAVA_HOME\lib\security\cacerts).
Use '*' to signify to accept all certificates. Note that this is not recommended due to security concerns.
Schema¶
This section provides a complete list of schema properties you can configure.
Property | Description |
---|---|
Location | A path to the directory that contains the schema files defining tables, views, and stored procedures. |
BrowsableSchemas | This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA, SchemaB, SchemaC. |
Tables | This property restricts the tables reported to a subset of the available tables. For example, Tables=TableA, TableB, TableC. |
Views | Restricts the views reported to a subset of the available tables. For example, Views=ViewA, ViewB, ViewC. |
Location¶
A path to the directory that contains the schema files defining tables, views, and stored procedures.
Data Type¶
string
Default Value¶
%APPDATA%\Dynamics365 Data Provider\Schema
Remarks¶
The path to a directory which contains the schema files for the connector (.rsd files for tables and views, .rsb files for stored procedures). The folder location can be a relative path from the location of the executable. The Location
property is only needed if you want to customize definitions (for example, change a column name, ignore a column, and so on) or extend the data model with new tables, views, or stored procedures.
If left unspecified, the default location is "%APPDATA%\Dynamics365 Data Provider\Schema" with %APPDATA%
being set to the user's configuration directory:
Platform | %APPDATA% |
---|---|
Windows | The value of the APPDATA environment variable |
Mac | ~/Library/Application Support |
Linux | ~/.config |
BrowsableSchemas¶
This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC.
Data Type¶
string
Default Value¶
""
Remarks¶
Listing the schemas from databases can be expensive. Providing a list of schemas in the connection string improves the performance.
Tables¶
This property restricts the tables reported to a subset of the available tables. For example, Tables=TableA,TableB,TableC.
Data Type¶
string
Default Value¶
""
Remarks¶
Listing the tables from some databases can be expensive. Providing a list of tables in the connection string improves the performance of the connector.
This property can also be used as an alternative to automatically listing views if you already know which ones you want to work with and there would otherwise be too many to work with.
Specify the tables you want in a comma-separated list. Each table should be a valid SQL identifier with any special characters escaped using square brackets, double-quotes or backticks. For example, Tables=TableA,[TableB/WithSlash],WithCatalog.WithSchema.`TableC With Space`.
Note that when connecting to a data source with multiple schemas or catalogs, you will need to provide the fully qualified name of the table in this property, as in the last example here, to avoid ambiguity between tables that exist in multiple catalogs or schemas.
Views¶
Restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC.
Data Type¶
string
Default Value¶
""
Remarks¶
Listing the views from some databases can be expensive. Providing a list of views in the connection string improves the performance of the connector.
This property can also be used as an alternative to automatically listing views if you already know which ones you want to work with and there would otherwise be too many to work with.
Specify the views you want in a comma-separated list. Each view should be a valid SQL identifier with any special characters escaped using square brackets, double-quotes or backticks. For example, Views=ViewA,[ViewB/WithSlash],WithCatalog.WithSchema.`ViewC With Space`.
Note that when connecting to a data source with multiple schemas or catalogs, you will need to provide the fully qualified name of the table in this property, as in the last example here, to avoid ambiguity between tables that exist in multiple catalogs or schemas.
Miscellaneous¶
This section provides a complete list of miscellaneous properties you can configure.
Property | Description |
---|---|
AllowDuplicateRecords | Indicates if the driver should check the configured duplicate detection rules. |
CrossCompany | Whether to pull data for all companies or just the user's default company. |
CustomUrlParams | The custom query string to be included in the request. |
IncludeFormattedValues | Indicates if columns that hold formatted values should be exposed. |
IncludeLookUpLogicalName | Indicates if the referenced entity name for a LookUp field should be exposed. |
IncludeNavigationProperties | A boolean indicating if navigation properties should be included in the column listing. |
MaxRows | Limits the number of rows returned when no aggregation or GROUP BY is used in the query. This takes precedence over LIMIT clauses. |
Other | These hidden properties are used only in specific use cases. |
Pagesize | The maximum number of results to return per page from Microsoft Dynamics 365. |
PseudoColumns | This property indicates whether or not to include pseudo columns as columns to the table. |
Timeout | The value in seconds until the timeout error is thrown, canceling the operation. |
UseClientSidePaging | Whether or not the ADO.NET Provider for Microsoft Dynamics 365 should use multiple threads with client side paging. |
UseDynamicStoredProcedures | A boolean indicating if dynamic stored procedures should be exposed. |
UserDefinedViews | A filepath pointing to the JSON configuration file containing your custom views. |
AllowDuplicateRecords¶
Indicates if the driver should check the configured duplicate detection rules.
Data Type¶
bool
Default Value¶
true
Remarks¶
Set this value to false to avoid adding duplicate records while performing INSERT operations.
Note: This property only applies when Edition is set to either CustomerService, FieldService, Marketing, ProjectOperations or Sales.
CrossCompany¶
Whether to pull data for all companies or just the user's default company.
Data Type¶
bool
Default Value¶
false
Remarks¶
This property only applies when Edition is set to either FinOpsOnline, FinOpsOnPremise or HumanResources.
CustomUrlParams¶
The custom query string to be included in the request.
Data Type¶
string
Default Value¶
""
Remarks¶
The CustomUrlParams
allow you to specify custom query string parameters that are included with the HTTP request. The parameters must be encoded as a query string in the form field1=value1&field2=value2&field3=value3. The values in the query string must be URL encoded.
IncludeFormattedValues¶
Indicates if columns that hold formatted values should be exposed.
Data Type¶
bool
Default Value¶
false
Remarks¶
For each column, an extra one is added to expose the formatted value. New columns will have "_display" postfix.
Note: This property only applies when Edition is set to either CustomerService, FieldService, Marketing, ProjectOperations or Sales.
IncludeLookUpLogicalName¶
Indicates if the referenced entity name for a LookUp field should be exposed.
Data Type¶
bool
Default Value¶
false
Remarks¶
For each key column, an extra one is added to expose the LookUp logical name value. New columns will have "_lookuplogicalname" postfix.
Note: This property only applies when Edition is set to either CustomerService, FieldService, Marketing, ProjectOperations or Sales.
IncludeNavigationProperties¶
A boolean indicating if navigation properties should be included in the column listing.
Data Type¶
bool
Default Value¶
false
Remarks¶
Navigation properties will not populate with information when retrieving data. Instead, navigation properties may be used to bind to an existing resource during inserts or updates. For example:
INSERT INTO accounts (_primarycontactid_value) VALUES ('123456')
To specify multiple values, use a comma-separated list. For instance:
INSERT INTO accounts (lead_customer_accounts) VALUES ('123,456')
MaxRows¶
Limits the number of rows returned when no aggregation or GROUP BY is used in the query. This takes precedence over LIMIT clauses.
Data Type¶
int
Default Value¶
-1
Remarks¶
Limits the number of rows returned when no aggregation or GROUP BY is used in the query. This takes precedence over LIMIT clauses.
Other¶
These hidden properties are used only in specific use cases.
Data Type¶
string
Default Value¶
""
Remarks¶
The properties listed below are available for specific use cases. Normal driver use cases and functionality should not require these properties.
Specify multiple properties in a semicolon-separated list.
Integration and Formatting¶
Property | Description |
---|---|
DefaultColumnSize | Sets the default length of string fields when the data source does not provide column length in the metadata. The default value is 2000. |
ConvertDateTimeToGMT | Determines whether to convert date-time values to GMT, instead of the local time of the machine. |
RecordToFile=filename | Records the underlying socket data transfer to the specified file. |
Pagesize¶
The maximum number of results to return per page from Microsoft Dynamics 365.
Data Type¶
int
Default Value¶
5000
Remarks¶
The Pagesize
property affects the maximum number of results to return per page from Microsoft Dynamics 365. Setting a higher value may result in better performance at the cost of additional memory allocated per page consumed.
PseudoColumns¶
This property indicates whether or not to include pseudo columns as columns to the table.
Data Type¶
string
Default Value¶
""
Remarks¶
This setting is particularly helpful in Entity Framework, which does not allow you to set a value for a pseudo column unless it is a table column. The value of this connection setting is of the format "Table1=Column1, Table1=Column2, Table2=Column3". You can use the "*" character to include all tables and all columns; for example, "*=*".
Timeout¶
The value in seconds until the timeout error is thrown, canceling the operation.
Data Type¶
int
Default Value¶
60
Remarks¶
If Timeout
= 0, operations do not time out. The operations run until they complete successfully or until they encounter an error condition.
If Timeout
expires and the operation is not yet complete, the connector throws an exception.
UseClientSidePaging¶
Whether or not the ADO.NET Provider for Microsoft Dynamics 365 should use multiple threads with client side paging.
Data Type¶
bool
Default Value¶
false
Remarks¶
Regardless of this value, the Microsoft Dynamics 365 connector will always use client side paging to retrieve data. However, setting this value to false will cause only a single thread to be used to execute this operation instead of attempting to use multiple threads to improve performance.
Note: This property only applies when Edition is set to either FinOpsOnline, FinOpsOnPremise or HumanResources.
UseDynamicStoredProcedures¶
A boolean indicating if dynamic stored procedures should be exposed.
Data Type¶
bool
Default Value¶
false
Remarks¶
A boolean indicating if dynamic stored procedures should be exposed.
Note: This property only applies when Edition is set to either FinOpsOnline, FinOpsOnPremise or HumanResources.
UserDefinedViews¶
A filepath pointing to the JSON configuration file containing your custom views.
Data Type¶
string
Default Value¶
""
Remarks¶
User Defined Views are defined in a JSON-formatted configuration file called UserDefinedViews.json
. The connector automatically detects the views specified in this file.
You can also have multiple view definitions and control them using the UserDefinedViews
connection property. When you use this property, only the specified views are seen by the connector.
This User Defined View configuration file is formatted as follows:
- Each root element defines the name of a view.
- Each root element contains a child element, called
query
, which contains the custom SQL query for the view.
For example:
{
"MyView": {
"query": "SELECT * FROM GoalHeadings WHERE MyColumn = 'value'"
},
"MyView2": {
"query": "SELECT * FROM MyTable WHERE Id IN (1,2,3)"
}
}
Use the UserDefinedViews
connection property to specify the location of your JSON configuration file. For example:
"UserDefinedViews", C:\Users\yourusername\Desktop\tmp\UserDefinedViews.json
Note that the specified path is not embedded in quotation marks.