Microsoft Dynamics 365 | Integration, Dataverse...

Writing a Dynamics AddOn, do we need to write to one API or three?

(0) Share

Report

Posted on by DavidThielen

Hi all;

We have a cloud product we want to tightly integrate into Dynamics as we do to Salesforce & HubSpot. I am having trouble figuring out where to get started.

First off, the Microsoft Dynamics cloud family now is:

Microsoft Dynamics 365 for Finance and Operations Enterprise Edition (formerly Microsoft Dynamics AX)
Microsoft Dynamics 365 Business Central (formerly Microsoft Dynamics NAV)
Microsoft Dynamics 365 Customer Service (formerly Microsoft CRM)

Is the above correct?

Second, we want to integrate our SAAS application into each of these products. Not just connect to the data, but to be part of the Dynamics SAAS product so we can add buttons to pages in the Dynamics products, get triggers when certain things change (like an Opportunity being marked closed-won in the CRM), and have web pages of ours in iFrames in Dynamics where appropriate (like a listing of templates of ours that can be run).

How do we integrate?
What is the API in Dynamics we can call for this?
And is it one API for all three? Or three distinct APIs?

Thanks – dave

All responses (5)

Answers (0)

Suggested answer

a33ik 84,325 Most Valuable Professional on at

Like (1)

Report

RE: Writing a Dynamics AddOn, do we need to write to one API or three?

In order to put buttons, weblets inside the system - there is no API. You will have to do that through manual customizing using "maker" - docs.microsoft.com/.../data-platform-create-entity and in order to customize buttons I would recommend using Ribbon Workbench - www.develop1.net/.../ribbonworkbench.aspx

Consider Dynamics (I believe you mean Dynamics for Sales/Service/Field Service) as an extended version of DataVerse and they have the same API. And this is the API I mentioned in my previous reply.
DavidThielen 10 on at

Like (0)

Report

RE: Writing a Dynamics AddOn, do we need to write to one API or three?

Hi Andrew;

Please correct me if I'm wrong. Accessing the DataVerse is accessing the data in the app. But it's not the API to put our buttons, weblets, etc. inside the Dynamics UI.

Also, Dynamics also has an OData API. Is there any downside to using that instead of direct DataVerse access? I ask because we have a wizard for OData but would have to write one for DataVerse.

thanks - dave
Suggested answer

a33ik 84,325 Most Valuable Professional on at

Like (1)

Report

RE: Writing a Dynamics AddOn, do we need to write to one API or three?

Hello,

Not an expert in F&O and BC. Here is the information about CRM (or how it is called now DataVerse) - docs.microsoft.com/.../perform-operations-web-api
DavidThielen 10 on at

Like (0)

Report

RE: Writing a Dynamics AddOn, do we need to write to one API or three?

First off - thank you. I have been trying for 2 weeks to get the answer you just gave me.

Second, for each of the MS Dynamics products, where is the information on how to integrate with them? Their REST API, suggested functionality for integration, sample code, etc?

thanks - dave
Suggested answer

a33ik 84,325 Most Valuable Professional on at

Like (2)

Report

RE: Writing a Dynamics AddOn, do we need to write to one API or three?

Hello,

The above list is the correct list of products.

All three products have different APIs so you will have to build 3 different versions of your addon for each of the products mentioned.