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:

Register your application with Azure AD — For instructions, see Register a native application with AAD in the Service Endpoints section of the Dynamics 365 For Operations / AX online documentation.
Obtain an authentication URL — You can either use a standard URL or specify an endpoint:
- Standard URL — Use the standard Microsoft URL: https://login.microsoftonline.com/common.
- Specify an endpoint — Use an endpoint specific to the user who has access to the Dynamics 365 For Operations / AX application. For example, if John Doe has access to the application, and his email address is john.doe@companyname.com, the Azure AD domain name would be companyname.com.
For more information on authentication with Azure AD, see Basics of Registering an Application in Azure AD.

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.

Select More > Connections from the menu.
From the Connections page select Add to open the Add a New Connection dialog.
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.
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.
Select OK to save the Connection.

Metadata Notes

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

Related Entities

Using relationships in the Include tab on the Query Block or Fetch Block may require you to expose related entities and fields to the OData web services in Dynamics 365 For Operations / AX. See the note at the beginning of this document for more information on exposing entities and fields.
Only one relationship is supported within a Map.
Hierarchical data is not supported.

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

Query operations run on an entire SQL table may cause a timeout. If a Query operation times out, reduce the number of fields selected for the Query.
Reducing the number of fields selected for the Query does not affect Preview, which selects all fields. You must run the Query operation to determine if the reduced number of fields selected resolved the timeout.

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

By default the creation date/time, last modified date/time, created by user and last modified by user fields are not exposed for any of the standard OData entities provided by Microsoft. If those fields are required for your integration, create similarly named fields and map the standard fields to the new fields. Different field names are required on the new fields because standard field names are reserved and cannot be exposed. See the note at the beginning of this document for more information on exposing entities and fields.

Filtering On Multiple Companies

To return results from more than one company, you can filter for multiple companies. For example, to return records associated with either the MyTicket company or the EventsManager company, define a filter that accepts those values for the dataAreaId field.

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

This Connector does not support Batch Processing.

Mapping Unrequired Fields

Some unrequired fields are marked as required. Mapping an unrequired field in Dynamics 365 For Operations / AX causes an error to occur.
The following fields are not required for the Create or Update operation, and generate an error if mapped:
- AmountChargedNotPosted
- DAXIntegrationId

Update And Upsert Operations

This Connector supports the Update Patch operation.
This Connector does not support the following operations:
- Update Replace
- Upsert Replace
- Upsert Patch
Using any of these unsupported functions may cause an error message.
dataAreaId — When performing a target operation, such as Update Patch, if the dataAreaId value for the record you are updating is not the same as the Company Name in your Dynamics 365 For Operations / AX Connection, the record is only found and updated if you include the dataAreaId of the record in the Match Criteria of your target operation Block.

Optimistic Concurrency

The OData Protocol uses Entity Tags (ETag) to determine how to update or delete data. Rules for updating or deleting data are based on the ETag value and the concurrency behavior. There are three options for concurrency behavior: always overwrite, overwrite if ETag has not changed, or overwrite if ETag has changed.
The Dynamics 365 For Operations / AX Connector exposes these ETags as fields:
- ETag — Available as a source and target field, contains the ETag value provided by the Dynamics 365 For Operations / AX OData service.
- ETagConcurrencyBehavior — Available as a target field, used to determine how data conflicts are handled. Possible values for this field are:
  - Always Overwrite
  - Overwrite If Match
  - Overwrite If Not Match
If these fields are left blank and the entity provides ETag information, the default is to always overwrite the record.
Delete operations always perform the default behavior. There is no way to map fields within a Delete Block. Therefore, if you attempt to use a Delete Block it always overwrites the existing data.
Optimistic Concurrency is an optional OData feature and is limited to specific entities. Contact your Dynamics 365 For Operations / AX OData service administrator for additional information.

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.