Small and medium business | Business Central, N...

Reporting

(0) Share

Report

Posted on by Colin Stokes

We have recently transferred to Business Central as SaaS. We are using Jet Reporting to run reports from Business Central, but they are taking over 3 hours to run. Our IT partner has investigated and have informed us its because Business Central SaaS has a restriction of 600 requests per minute, and our reports contain significantly more than this. Can anyone verify if there are indeed restriction in Business Central to 600 requests per minute? Is there anyway round this, as it means if we make a last minute change to underlying data we have to wait over 3 hours before we can get updated reports.

All responses (7)

Answers (0)

Sort by

Suggested answer

Stefano Demiliani 37,172 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Yes this is the default value for SOAP and APIs services. You cannot change this limit now.
Colin Stokes 5 on at

Like (0)

Report
Copy link

Link copied!

Thanks Stefano. Is there any other reporting mechanism youre aware of that would help us? Currently it takes over 3 hours, but we expect to be double the size within the next couple of years so we could be having to wait over 6 hours to get reports. We can schedule overnight but doesnt help when we have to make urgent changes to numbers. The system almost becomes unfit for purpose if we can effectively only report on numbers that run overnight.
Suggested answer

THE Italian Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

The API limit is clearly documented here

https://docs.microsoft.com/en-us/dynamics-nav/api-reference/v1.0/dynamics-current-limits

https://docs.microsoft.com/en-us/dynamics-nav/api-reference/v1.0/dynamics-rate-limits

You have to be sure that you have the latest Jet Reports app that implements a retry logic avoiding throttling.

This is one of the current constraints for SaaS, unfortunately.

if you are in version 16.x already, then it would be good for you also to implement telemetries to keep monitored high volume requests. Below where you could find template, documentation and a useful PPTX

https://github.com/microsoft/BCTech/tree/master/samples/AppInsights
Colin Stokes 5 on at

Like (0)

Report
Copy link

Link copied!

Thanks Duilio. Thats helpful
Stuart Passey 5 on at

Like (0)

Report
Copy link

Link copied!

Hi Duilio,

You reference version 16.x, is this in relation to Jet reports or BC please? If Jet reports, we currently run v20.6.

Can you tell me if the retry logic (to avoid throttling) will be enabled by default and also, how much of a difference in performance could we expect if this if it is not currently enabled and we enable it?

What are the benefits of monitoring the high volume requests? Could this data then be use to identify areas of improvement or perhaps mis-configured reports?

And one more question, what other options are available for a us aside moving the BC to an on-prem environment? Could hosting in Azure or changing the reporting platform make any significant improvements?

Sorry for all the questions,

Many thanks,

Stuart.
Suggested answer

Steven Renders 5,698 Moderator on at

Like (1)

Report
Copy link

Link copied!

I suggest having a look at Power BI in combination with Query objects that you create in AL. Query objects support table joins and aggregates, so you need to pull less records from BC.

docs.microsoft.com/.../devenv-query-overview

(That is if you implement a group-by in the query...)

(Power BI Pro also supports incremental refresh, that might also help.)

Having said that, you can (and probably will) also experience performance issues when retrieving many records from BC using query web services. In order to fix this, it might be a good idea to create an external DWH, for example in SQLAzure, then push data from BC to the DWH and connect Power BI (or another reporting tool) to that DWH. And then also implement some kind of incremental refresh mechamism.

But, queries support Read-Scale Out, so that might also provide an advantage:

docs.microsoft.com/.../database-read-scale-out-overview

But of-course, you first need to enable that in your queries:

docs.microsoft.com/.../devenv-dataaccessintent-property
Colin Stokes 5 on at

Like (0)

Report
Copy link

Link copied!

Thanks Steven, much appreciated