March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
I have a model built on data from the JIRA Issues API.
It refreshes in the desktop app but it fails in the service saying"The column 'Column1' of the table wasn't found".
If I limit the number of calls to the API (temporarily modifying the query) to something small, like 3, it will refresh in the service.
The number of calls it should make is based on the number of records in JIRA and is currently around 250 calls.
Is there some sort of timeout or limit in the service that could cause the query to fail?
Is there something I can do to ensure all the data gets loaded?
Solved! Go to Solution.
That'll do it. This setting is ignored in the service, and the service will always try to run queries in parallel.
One way to prevent that is to use the Function.InvokeAfter trick.
Hi @Aron_Moore
There could be a limit on the JIRA side.
If you change your code to go from 1000 to 3 and let it run through does it all complete successfully?
If it does I would then up the number until it fails and then go one back?
Thanks for the reply.
The query runs fully in the desktop tool so I don't think there is a number of calls limit for our JIRA.
I could try to find the number of calls Power BI service can make before failing, but that is going to be less than the number of calls needed to get the whole of the data.
Did you disable parallelism in the desktop?
Hadn't changed the parallelism settings.
The desktop file is using settings of:
Global
Current File
That'll do it. This setting is ignored in the service, and the service will always try to run queries in parallel.
One way to prevent that is to use the Function.InvokeAfter trick.
Did some research on the Function.InvokeAfter and modified my code.
It fully refreshed in desktop. Also made some visual changes to ensure the changes pushed up to the Service.
Still failing in the service with same error.
Thoughts?
5 seconds is not really a delay. try something a bit higher.
I've increased to #duration(0,0,0,30). Refreshed fine in the desktop app, though took much longer.
Pushed the change to the service.... still failing. Same error.
that's the end of my rope. If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .
Was hoping to avoid doing that dance...
I'm waiting for our JIRA team to get back to me just in case there is some limit that the service is hitting that desktop does not. Maybe they'll have logs from the JIRA side that would be helpful (and will probably be asked for by help desk).
Did you find the solution? Please update having same issue here.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
37 | |
22 | |
20 | |
10 | |
9 |
User | Count |
---|---|
60 | |
56 | |
22 | |
14 | |
12 |