Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get certified in Microsoft Fabric—for free! For a limited time, the Microsoft Fabric Community team will be offering free DP-600 exam vouchers. Prepare now

Reply
Aron_Moore
Solution Specialist
Solution Specialist

API data not refreshing in Service

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.

 

Refreshes.png

 

Loops.png

 

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?

1 ACCEPTED 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.

View solution in original post

11 REPLIES 11
GilbertQ
Super User
Super User

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?





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!







Power BI Blog

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

Table Loads.png

 

Current File

Table Loads2.png

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.

 

InovkeAfter.png

 

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.

Helpful resources

Announcements
OCT PBI Update Carousel

Power BI Monthly Update - October 2024

Check out the October 2024 Power BI update to learn about new features.

September Hackathon Carousel

Microsoft Fabric & AI Learning Hackathon

Learn from experts, get hands-on experience, and win awesome prizes.

October NL Carousel

Fabric Community Update - October 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors