Announcements
No record found.
Hi,
We have developed an integration to the Business Central v3 OData. We have a source query object that contains 725,000 transactions and when we query for this object we get the first 625,000 in under 2 minutes. at the bottom of the result set is an odata.nextlink that we then send a request for but this always times out after 8-10 minutes. It seems strange that we are timing out on the next odata result set that is only 1/6th the size of the first, successful result set.
Has anyone experienced this any have any suggestions as to what might be causing this. We are basically passing off these two requests.
OData V3 endopoint is no longer maintained and will be deprecated (completely removed) from the service stack in the upcoming 2021 spring release. This is documented here
Deprecated Features in W1 - Business Central | Microsoft Docs
...
The following feature will be Removed with Business Central 2021 release wave 1.
There is also a simple query to find out if your customers are implementing OData V3 in the aka.ms\bctelemetrysamples
BCTech/samples/AppInsights/KQL/Queries at master · microsoft/BCTech (github.com)
See below
Hi Duilio, thank you for the information. I have done some research and tested using OData v4 and it behaves these same way.
If you could reproduce the same with ODataV4 then you might have your CSP Partner open a request on your behalf to Microsoft support.
Thanks Duilio, we will take a look with Odata v4.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our community stars!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
OussamaSabbouh 715 Super User 2026 Season 2
YUN ZHU 452 Super User 2026 Season 2
AndrewThomas81 371 Super User 2026 Season 2