DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Configuring a Shopify MuleSoft Connector
  • Handle HL7 MLLP Messages With Mule 4
  • SharePoint Integration With MuleSoft
  • Configuring Amazon S3 Using Mulesoft

Trending

  • 9 Practical Ways to Fix Laravel Performance Issues in Production
  • AI Agents Need an Identity Plane: Rethinking Enterprise Authorization for Autonomous Software
  • AI-Era Cybersecurity, Part 1: Mapping Glasswing, Daybreak, Lightwell and the Tools Racing to Find and Fix Bugs
  • Where Should a Transaction End? Designing Consistency Boundaries in Distributed Java Systems

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Software Design and Architecture
  3. Integration
  4. Mulesoft — Microsoft Dynamics 365 for Operations Connector

Mulesoft — Microsoft Dynamics 365 for Operations Connector

In this article, we will learn how to use MuleSoft’s Microsoft Dynamics 365 for Operations Connector to connect to Microsoft Dynamics 365 for Operations.

By 
Vishnu Ramakrishnan
·
Updated Jun. 11, 18 · Tutorial
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
10.8K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

This is the second article in 3 part series. You can read the first article here. In this article, we will learn how to use Mulesoft’s Microsoft Dynamics 365 for Operations Connector (3.6+, for v4 we have a different connector) to connect to Microsoft Dynamics 365 for Operations.

Prerequisite:

We need enterprise license to download Microsoft Dynamics 365 for Operations Connector ("Select" Connector) and here is Anypoint Exchange link to download it. We need to use 1.0.1 version.

Note: Though this version is not listed in Anypoint Exchange, with enterprise license, it works.

Maven dependency details:

<dependency>
<groupId>org.mule.modules</groupId>
<artifactId>microsoft-dynamics365-for-operations</artifactId>
<version>1.0.1</version>
</dependency>

Azure Active Directory (AAD) app Registration:

Follow the same steps from article 1, with a minor change in step 1. Here we select Web app / API for Application type instead of Native.

We have an additional step to set up key (client secret). Follow this link and topic “Register a native application with AAD” — step 10 for setting up the key. Please note, copy the key and store it safely because we cannot get it again.

Configurations in Dynamics 365

In the left-hand side menu, under the heading “Modules,” scroll down to “System Administration.”

Click “Azure Active Directory” applications link.

Image title

Click “New” and set up “Client ID” (From AAD App) and “User ID” (set it up in Active Directory and Dynamics 365 as a User)

Image title

Mulesoft's Microsoft Dynamics 365 for Operations Connector:

Image title

Connector Configuration

The following values are "required"/"mandatory" for Dynamics 365 for Operations Connector.

(1) Client Id (2) Client Secret (3) Username (4) Password (5) Resource (6) Token Request Endpoint.

Please work with your Platform/DevOps Engineer and Infra Team to get these values.

Client ID and Client Secret comes from AAD App. User Name and Password are to be set up in both Active Directory (AD) and as a valid user with required permissions in Dynamics 365. Resource is Dynamics env URL, like Dev, SIT, Prod. Token Request Endpoint is used to get the access token. It will look something like,

Token Request Endpoint — The token endpoint that is called to get the access token. Example: https://login.windows.net/TENANT_ID/oauth2/token where TENANT_ID (Check article 1) is the Azure Active Directory ID.

Follow this link in the Mulesoft documentation “To Configure for OAuth 2.0 Username-Password” to setup Connector Configurations.

Image title

Click “Test Connection” to test connectivity. Look for “Test Connection Successful.”

Follow this link in Mulesoft documentation “To Import Data Recurring Job” and set up “General” Connector settings.

URI Path — “api/connector/enqueue/” — This is standard for import recurring jobs.

Activity ID — is from Dynamics 365. Talk to Dynamics 365 team to get it. Each recurring job has a unique Activity ID.

Entity Name — is from Dynamics 365. Talk to Dynamics 365 team to get it.

File Input — Is the payload that contains the actual CSV/Txt file. #[payload]. Please note, the payload has to be a stream/ByteArray.

Hope you enjoyed this article. Looking forward to your feedback. Stay tuned for article 3.

Microsoft Dynamics 365 Connector (mathematics) MuleSoft

Opinions expressed by DZone contributors are their own.

Related

  • Configuring a Shopify MuleSoft Connector
  • Handle HL7 MLLP Messages With Mule 4
  • SharePoint Integration With MuleSoft
  • Configuring Amazon S3 Using Mulesoft

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook