I am still experiencing issues with a client regarding the ItemsIncremental table. After rolling back the breaking change from Exact Online, all tables refresh fine and quickly, except for this one.
Even when only 100 rows are requested, it fails:
itgenboe161
The data download was cancelled after 5 minutes, 6 seconds, such as by the user navigating away in the Power BI or Power Query user interface.
Het bepalen van de eerste 100 rijen vereist voor een *Incremental-tabel het verwerken van alle rijen. Zie voor meer informatie:
Advies is om de download ruim voldoende looptijd te geven om alle artikelen op te halen, bijvoorbeeld het aantal artikelen maal 10 seconden.
Het aantal artikelen kunt u vlot bepalen via het rapport Omgevingsanalyse op Get My Report for Exact Online of zoals beschreven in:
Okay, that first part is enlightening at least.
I have set the timeout duration to 2 hours in the query editor of the dataflow:
Just tried via Power BI desktop and then the table loads smoothly within one minute.
Glad it worked out.
Is the problem solved with this, or is there a second situation where it takes longer?
How many rows are involved?
No, the problem is that the refresh in the Power BI Service is not working.
I just wanted to point out that it does work in Power BI Desktop and that I find it strange that it doesn’t work in the service.
Power BI Service has different features than Power BI Desktop.
How many rows are involved?
It’s about ± 300,000
I have further split the Items table into more queries. Previously, I had one query per administration (2 administrations). The queries contained about 300,000 rows.
Now I have further subdivided the queries per administration into Modified up to 2023 and from 2024 onwards. As a result, the rows per query are now approximately 150,000.
The refreshes are now running smoothly via the Power BI service, but I find it strange that these issues already occur with queries of 300,000 rows.
Glad it worked out.
It is a known issue with the Power BI Service. Using Power BI Premium per User seems to shift the boundaries. The exact motivation can possibly be provided by Microsoft Support.
This question has been automatically closed after 1 week of inactivity. The last provided answer has been marked as the solution.
Please post a new question in a separate topic if the issue occurs again. In the new question, please include a link to this topic by pasting its URL into the text.