TIBCO Scribe® Connector For Microsoft Dynamics 365 For Operations / AX

Use the Connector for Dynamics 365 For Operations / AX in an Azure environment to access 365 For Operations / AX system functionality and customizations through OData web services. This Connector supports custom entities, as well as multiple Dynamics 365 For Operations / AX organizations and tenants.

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

Connector Specifications

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

Note: On-premise versions of Microsoft Dynamics 365 For 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.

Selecting An Agent Type For Dynamics 365 For Operations / AX

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

Azure Active Directory

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 Operations / AX Connector is deployed.

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

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

Connecting To Dynamics 365 For 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.

This section provides information on creating a TIBCO Scribe® Online Connection to Dynamics 365 For Operations / AX.

  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.
    • 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 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 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 to save the Connection.

Metadata Notes

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

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

Dynamics 365 For Operations / AX Connector As IS/MS Source

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

Custom Fields

Filtering On Multiple Companies

Dynamics 365 For Operations / AX Connector As IS/MS Target

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

Batch Processing

Mapping Unrequired Fields

Update And Upsert Operations

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 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.

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

More Information

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