Data management API vs recurring integration

(0) Share

Report

Posted on by Yuji

4,131

Hi,

Is there any comparison about Data management API vs recurring integration

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/data-management-api

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/recurring-integrations

When should we use Data management API?

Thanks,

I have the same question (0)

All responses (6)

Answers (1)

Sort by

Verified answer

Sukrut Parab 71,741 Moderator on at

Like (0)

Report
Copy link

Link copied!

One of the link given by you has decesion point about when to choose section

docs.microsoft.com/.../data-management-api

Was this reply helpful? Yes No
Yuji 4,131 on at

Like (0)

Report
Copy link

Link copied!

Since Data management API service type is Odata, could this support large volume file import?

Was this reply helpful? Yes No
Sukrut Parab 71,741 Moderator on at

Like (0)

Report
Copy link

Link copied!

How many records you want to import and which entity you are using ?

Was this reply helpful? Yes No
Yuji 4,131 on at

Like (0)

Report
Copy link

Link copied!

100,000 Sales Orders per hour.

Was this reply helpful? Yes No
Indrox 70 on at

Like (0)

Report
Copy link

Link copied!

Hi Yuji,

With this volume I think recurring integrations is a better option.

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 239,680 Most Valuable Professional on at

Like (2)

Report
Copy link

Link copied!

That it uses a standard protocol for RESTful web services, i.e. OData, doesn't mean that it's slow. Whether it's slow or not depends on how much work the web service does and how much data it returns.

You seem to believe that the usual OData service is slow because it uses OData standard for communication and not because of what it does. But that's not the case, as far as I can say.

The newer metadata API does the same thing as the older recurring integrations API: it exports and import files. I don't see why process should be slower just because you make a slightly different HTTP request. The usual F&O OData service does a very different thing and therefore it behaves differently also from the performance point of view.

The key difference between these APIs is how they handle scheduling, not whether they use a standard protocol or something custom.

Was this reply helpful? Yes No