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

Join us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.

Reply
karimm
Helper II
Helper II

Best Practice for handling empty API response

Hi All

 

I have several queries that import data from SAAS systems via REST APIs.

I call the API giving a query/filter as input, and parse the API response via several steps (some columns return as records/lists). The final result is a table of X columns.

 

The query usually looks like this:

- Create the query

- Call API

- Expand Field 1

- Expand Field 2

.

.

- Expand Field n

 

In some scenarios, the API response is empty based on the given response. So the query fails on the first Expand step saying "the column 1 of the table wasn't found".

 

I would like the query not to fail when I try to expand the fields, and to have an empty table eventually with same X columns.

 

What would be the best practice for writing a more resilient query?

 

Thank you

2 REPLIES 2
pieduke88
Frequent Visitor

hi - how did you end up resolving this? I'm having the same issue

lbendlin
Super User
Super User

@karimm First thing to do is to enable ManualErrorHandling in your Web.Contents() call.  After that you will want to utilize the built in try ... otherwise ...  feature in Power Query.

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June 2025 Power BI Update Carousel

Power BI Monthly Update - June 2025

Check out the June 2025 Power BI update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

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