TIBCO Scribe® Online Connector for Microsoft Dynamics 365 for Finance and Operations/AX

The TIBCO Scribe® Online Connector For Microsoft Dynamics 365 for Finance and Operations/AX supports a variety of operations to multiple organizations/tenants using the OData Web Service including, query, create, update, insert, update/insert, and delete. The connector also supports authentication using Azure Active Directory and advanced functionality for configured customized HTTP requests.

Note:TIBCO Scribe® Online can only access Dynamics 365 for Finance and Operations/AX entities and fields that are exposed to OData web services in Dynamics 365 for Finance and Operations/AX by marking them as IsPublic in the Dynamics 365 for Finance and Operations/AX Application Object Tree (AOT). Contact your Microsoft Dynamics 365 for Finance and Operations/AX Administrator for assistance.

Connector Specifications

This Connector supports Microsoft Dynamics 365 for Finance and Operations/AX Online and is compliant with OData version 4.

Note: On-Premise versions of Microsoft Dynamics 365 for Finance and Operations/AX are not supported.

  Supported

Agent Types

On Premise X
Cloud X

Replication Services

Source  
Target  

Integration Services

Source X
Target X

Migration Services

Source X
Target X

Maps

Integration X
Request-Reply X
Message  

Note: This Connector is available from the TIBCO Scribe® Online Marketplace. See Marketplace TIBCO Scribe® Certified Connectors for more information.

Setup Considerations

Azure AD Best Practices

If you authenticate using Azure AD, there are some timing issues to consider to prevent errors.

Client Secret Authentication Requirements

To use Client Secret Authentication, a Connected app in the Azure portal is required. You can use the TIBCO Connected app or you can create an App Registration in the Azure portal. To create an App Registration, be sure to configure the following:

Once the App is created, you can find Tenant Id and Client Id on the User Interface.

Note: To create a Client secret click Certificates &secrets > New Client Secret. Add the client secret description and select the expiration period. Save the generated client secret value. Selecting An Agent Type For Dynamics 365 for Finance and Operations/AX

Legacy OAuth Authentication Requirements

Azure Active Directory (Azure AD), a Microsoft multi-tenant, cloud-based directory and identity management service, provides single sign-on (SSO) access to cloud SaaS Applications, such as Office365, Salesforce.com, and DropBox. To begin, set the Client Id in the Azure AD account where the Dynamics 365 for Finance and Operations/AX application is deployed.

Note: Because Dynamics 365 for Finance and Operations/AX is an enterprise resource planning (ERP) system, TIBCO recommends working with a Dynamics 365 for Finance and Operations/AX consultant or Microsoft partner to set the client ID in the Azure AD account where the Dynamics 365 for Finance and Operations/AX application is deployed.

To set the client ID in the Azure AD account, you must:

Selecting an Agent Type for Dynamics 365 for Finance and Operations/AX

Refer to TIBCO Scribe® Online Agents for information on available Agent types and how to select the best Agent for your Solution.

Connecting to Dynamics 365 for Finance and Operations/AX

Note: Best practice is to create Connections with credentials that limit permissions in the target system, following the principle of least privilege. Using Administrator level credentials in a Connection provides Administrator level access to the target system for TIBCO Scribe® Online users. Depending on the entities supported, a TIBCO Scribe® Online user could alter user accounts in the target system.

Deployment Types

There are two deployment types for the Microsoft Dynamics 365 for Finance and Operations/AX Connector that provide different authentication methods. Follow the link for the deployment type you plan to use for step-by-step configuration instructions: 

Client Secret Authentication

  1. Select More > Connections from the menu.
  2. From the Connections page, select Add to open the Add a New Connection dialog.
  3. Select the Connector from the drop-down list in the Connection Type field, and then enter the following information for this Connection:
    • Name — This can be any meaningful name, up to 25 characters.
    • Alias — An alias for this Connection name. The alias is generated from the Connection name, and can be up to 25 characters. The Connection alias can include letters, numbers, and underscores. Spaces and special characters are not accepted. You can change the alias. For more information, see Connection Alias.
    • Deployment - Select Client Secret
    • OData Service URL - The address of any acceptable URL where the OData service is located. This URL must end in /data.
    • Tenant - Enter the Tenant Id, also known as the Directory ID, generated when you registered the Azure Active Directory (AAD) application. Required.
    • Client ID - GUID that identifies the client in the Dynamics 365 for Finance and Operations/AX system. This is the Application ID generated when registering the application in Azure Active Directory. Required.
    • Client Secret - Enter the Client Secret generated when you registered the Azure Active Directory (AAD) application.
    • Company Name - The company specified in Dynamics 365 for Finance and Operations/AX for this integration. Required.
  4. Select Test to ensure that the Agent can connect to your database. Be sure to test the Connection against all Agents that use this Connection. See Testing Connections.
  5. Select OK/Save to save the Connection.

Legacy OAuth Authentication

  1. Select More > Connections from the menu.
  2. From the Connections page select Add to open the Add a New Connection dialog.
  3. Select the Connector from the drop-down list in the Connection Type field, and then enter the following information for this Connection:
    • Name — This can be any meaningful name, up to 25 characters.
    • Alias — An alias for this Connection name. The alias is generated from the Connection name, and can be up to 25 characters. The Connection alias can include letters, numbers, and underscores. Spaces and special characters are not accepted. You can change the alias. For more information, see Connection Alias.
    • Deployment - Select Legacy OAuth
    • OData Service URL - The address of any acceptable URL where the OData service is located. This URL must end in /data.
    • User - The name of the user who has rights to access OData, if your OData service requires authentication. Required.
    • Password - The password for User, if your OData service requires authentication. For more information on OData, see your endpoint provider. Required.
    • Client ID - GUID that identifies the client in the Dynamics 365 for Finance and Operations/AX system. This is the Application ID generated when registering the application in Azure Active Directory. Required.
    • Authentication URL - The URL where the Client Id is verified in following the format. Required.

      http://login.microsoftonline.com/[domain_name]

    • Company Name - The company specified in Dynamics 365 for Finance and Operations/AX for this integration. Required.
  4. Select Test to ensure that the Agent can connect to your database. Be sure to test the Connection against all Agents that use this Connection. See Testing Connections.
  5. Select OK/Save to save the Connection.

Metadata Notes

Consider the following for Dynamics 365 for Finance and Operations/AX data fields and entity types.

Naming

Connection metadata must have unique entity, relationship, and field names. If your Connection metadata has duplicate names, review the source system to determine if the duplicates can be renamed.

Related Entities

Note: For this Connector, only one level of relationship, Parent/Child, is supported for the entity selected in the Query or Fetch Block. For records with multiple levels of relationships, such as Parent, Child, Grandchild, only the selected Parent entity and related Child entities can be retrieved. Additional levels beneath Child entities, such as Grandchildren, cannot be accessed for this Connector using the Include tab. See Block Properties Include Tab — Relational Data.

Query Timeouts

Retry Logic

When a timeout occurs, theMicrosoft Dynamics 365 for Finance and Operations/AX Connector retries three times with the following delays in between:

When a throttle limit or request limit exceeded error is received, the Microsoft Dynamics 365 for Finance and Operations/AX Connector retries once using the delay returned by Microsoft Dynamics 365 for Finance and Operations/AX. This delay throttles or slows down the entire Map.

Filters

The "is like" and "is not like" operators are not supported. For the "is like"operator, use the "equals" operator and use an "*" as a wild card character. The "is not like" operator does not have a similar alternative.

Dynamics 365 for Finance and Operations/AX Connector As IS/MS Source

Consider the following when using the Dynamics 365 for Finance and Operations/AX Connector as an IS/MS source.

Custom Fields

Filtering On Multiple Companies

Dynamics 365 for Finance and Operations/AX Connector As IS/MS Target

Consider the following when using the Dynamics 365 for Finance and Operations/AX Connector as an IS/MS target.

Batch Processing

Mapping Unrequired Fields

Update And Upsert Operations

Send Operation

Optimistic Concurrency

TIBCO Scribe® Online API Considerations

You must define a Connection Name and Connection Alias for each OData endpoint. For more information, see TIBCO Scribe® Online Connector For OData.

To create Connections with the TIBCO Scribe® Online API, the Dynamics 365 for Finance and Operations/AX Connector requires the following information:

Connector Name

Microsoft Dynamics 365 for Operations/AX7

Connector ID

A48234C1-BDE7-4AF0-B88E-64478168EF30

TIBCO Scribe® Online Connection Properties

In addition, this Connector uses the Connection properties shown in the following table.

Note: Connection property names are case-sensitive.

Client Secret OAuth Properties

Name Data Type Required Secured Usage

DynamicsAuthenticationType

string

Yes

No

 

CompanyId

string

Yes

No

 

ClientId

string

Yes

Yes

 

ServiceUrl

string

Yes

No

 

ClientCredsTenant

string

Yes

No

 

ClientSecret

string

Yes

Yes

 

Legacy OAuth Connection Properties

Name Data Type Required Secured Usage

AuthenticationUrl

string

Yes

No

 

CompanyId

string

Yes

No

 

ClientId

string

Yes

Yes

 

ServiceUrl

string

Yes

No

 

User

string

Yes

No

 

Password

string

Yes

Yes

 

AuthenticationType

string

Yes

No

None, Basic

License Agreement

The TIBCO Scribe® Online End User License Agreement for the Dynamics 365 for Finance and Operations/AX Connector describes your and TIBCO's legal obligations and requirements. TIBCO suggests that you read the End User License Agreement.

More Information

For additional information on this Connector, refer to the Knowledge Base and Discussions in the TIBCO Community.