59
Mainly for power bi scenarios. Retrieving large amount of data via odata is far too slow. Instead this data should be avalable via a read-only replica which can be accessed via sql directly.
This gap prevents us from providing a power bi based analysis portfolio to cloud customers, which is a show stopper for many deals.
Category: General
STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for your feedback. Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future. 

 

There is a way to achieve read scale-out through Odata though: Use API queries and set the DataAccessIntent property to Readonly. See more in the performance tuning guide here: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/performance/performance-developer#performance-patterns-do-this


Sincerely, 

Kennie Nybo Pontoppidan

PM, Microsoft 


Comments

A

@Steven Renders

Hi Steven

I wonder if you find any good method for this issue? We have the same problem now.

Thanks

Category: General

A

Hi Kenny,

The DataAccessIntent to ReadOnly is nice, but the problem is that page web services are slow and query web services aren't that fast too ;-)

Having a possibility, on a copy of the production database, to create stored procedures (and select queries and views) provides a lot more flexibility. Stored procedures can contain logic and parameters, and can also query multi-company, which AL-query objects can not.

I'm currently also investigating alternatives, for example:
-pull/push BC data to an Azure SQL DWH
-dataflows
-Azure Data Factory
-...
But I can imagine this being too complex and expensive for many customers...

Kind regards,
Steven Renders

Category: General