Share
Report
5Hi There,
Site Details:
* It is a Dynamics365 BC environment.
* We are using PowerBI with the BusinessCentralAPI connection
* Was a recent data migration from Navision where most of Navision's history was brought over. (Sales invoices, GL etc.)
* We use the webservices API (legacy) and it is fairly stable, slow but does work. The new API however seems to have issues.
* Customer has asked if there is something the vendor might be able to do to improve the performance but they have not been helpful so I am trying this forum to see if there is any advice that can help out there.
Background:
I've been trying to use Power BI to load generalLedgerEntries and expand the dimesionSetLines to get the related SalesInvoice ID.
If I run just the generalLedgerEntries it take anywhere from 2 to 4 hours to pull down the 7 million records.
If i try to expand any of the related dimenstionsets (e.g. the Sales Invoice line) it runs for 10 plus hours and returns a timeout error. Sometimes it says if might be an OLE DB or ODBC error. Unable to read from transport connection because of buffer space or an API 500 Internal Server error.
Obviously seems like it is being pushed too hard. Is this common with larger dataset sizes in BC using the APIs?
I'm recommending to the Business that we write an App to call the API in smaller chucks that downloads and caches this data in a database but they asked me to check and see if the vendor may not have setup the site correctly and that is why it can't handle these larger requests. Is that scenario likely?
Any advice would be appreciated.
Thanks
All responses (
Answers (
