Finance | Project Operations, Human Resources, ...

Optimization of OData entity API

(2) Share

Report

Posted on by SA-20091232-0

Hi, I have created an Odata API of Sales orders, That is nothing but the copy of the default order headers API. We are trying to send information on orders to the other system, so it is being used as an outbound API. We are facing an issue in the optimization, as it returns records in thousands, and the modified orders are large. It takes approximately 3 minutes in every call to synch data to the portal(the other system), which gives timeout to the portal and synching data from D365 FO to the other system fails. My API does not have any extra joins, all are needed. How can I optimize it more, or is there any pagination kind of concept available to send data to the portal in chunks like if there are 5000 records available in the modified datetime >= 4th December , I want to send data in chunks of 1000, or suggest any of the best way to avoid the timeout situation.

Categories:

Microsoft Dynamics AX

I have the same question (0)

All responses (6)

Answers (0)

André Arnaud de Cal... 301,210 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

Can you explain more about this integration? From what application to what application are you moving sales orders? Is it real-time or batch-based? What integration app are you using? In case you need to copy thousands of records, probably a file-based integration using data management APIs would be a better option.

Was this reply helpful? Yes No
SA-20091232-0 89 on at

Like (0)

Report

Hi André Arnaud,

We have to send data from D365 FO to the portal system that is developed in .Net. This integration works in a way that Portal calls the Odata API of D365 FO asynchronously, So the number of orders piles up. and in every call then it has to synch all the orders. The number is a huge count and D365 FO API takes time to return data. I.e. to return the data of 5000 records, the D365 FO Data entity takes more than 3 minutes. We want to optimize that.

Was this reply helpful? Yes No
Anthony Blake 2,963 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

Are you creating large volumes of sales orders and sending new & changes only, or is it a full list or orders every run?

Anthony

Was this reply helpful? Yes No
SA-20091232-0 89 on at

Like (0)

Report

Hi Anthony Blake ,

We are sending all the orders but the portal has made the filer to call the data in a specific date range. So our API is run without any date range will return all orders. But Portal applies filter to get only limited orders from that API.

Was this reply helpful? Yes No
Anthony Blake 2,963 Super User 2025 Season 2 on at

Like (0)

Report

How often is it running, are you limiting new to & updated or outputting everything? so Are you limiting by modified date or just all orders created for a large date range? I'm just trying to get an idea as to whether you could implement a quick win with some filtering or if you might need to consider changing your approach.

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 237,990 Most Valuable Professional on at

Like (0)

Report

OData has $top and $skip URL parameters for this purpose and, as far as I know, it's supported in F&O too.

For example, /data/MyEntity?$top=1000&$skip=2000 will give you the third batch of 1000 records.

Was this reply helpful? Yes No