Forum Discussion
Unable to read data from the transport connection error
The solution which I have implmenented to complete all my reports was, I created "Query" instead of "Page" in Business Central and then I loaded all the queries in Power BI.
This helped me to complete all the process very smoothly.
Hi jaineshpoojara ,
Some of these users seem to have solved the problem after deleting some tables to reduce calls to Business Central. You can try .
Anonymous I have tried the same!!
I have opened a new Power BI file and only transfromed 2 tables and when I tried merging it, the operation was successful.
But when I tried to apply the changes to move that one table into Power BI desktop, it showed me the same error.
Eduardo_SuelaHelper I
Exactly the same issue:
- read two fact tables from Business Central
- some operations: filters, column selections, replaces, calculations
- merge of those two tables
- group by
Fact tables are small (about 100k lines), so that shouldn't be the problem.
These operations make virtual memory grows as crazy.
A computer with 16GB can process it in desktop
A computer with 12GB cannot
Refreshes in service sometimes cannot do it
We have tried:
filters (short term solution. Next year the problem would be back)
buffers and stopfolding, some tiems work, sometiems don't
We need a solution for that
- Eduardo_Suela
Finally I could make it work
We had to add Table.StopFolding every where
And now it works
It looks like some optimizations folded into the source system were unfeasible after the update
The solution which I have implmenented to complete all my reports was, I created "Query" instead of "Page" in Business Central and then I loaded all the queries in Power BI.
This helped me to complete all the process very smoothly.Answering just in case it helps somebody.
In my case, querying Business Central web services and then getting the error when having a few join or merge steps, buffering the tables before doing those costly steps helped being able to refresh the report in the desktop. The report wasn't failing in the Power BI Service.
2025 edit: after still getting the error, although less frequently, I might add that as somebody has mentioned before, setting the same datatypes for the columns involved in a join helps reducing the occurrence of the problem.