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

The Fabric community is upgrading! Read all of the details including the timeline and what you can expect. Learn more

Reply
icassiem
Post Prodigy
Post Prodigy

ELT JSON Semi Structured Loop

Good day,

 

Apologies this is a bit of a duplicated but because i only recently have plan approved, so i dont get the time to do deep research or learning as yet

Solved: Re: ELT JSON / Semi structured - Microsoft Fabric Community

 

My source are mostl API JSON that i have to transform but before i can transform i need to loop, i dont know if dataflow is like powerbi powrqury window or i do it in powerbi one example and past the script in dataflow but how would i do api loops then unpivot the json, would i need pythin to first downlad all looped api content then pass on dataflow etc?

 

Regards

1 ACCEPTED SOLUTION
Parchitect
Solution Sage
Solution Sage

For this scenario I would not use Power BI Desktop as the main ingestion engine.

 

Power BI Desktop / Power Query can handle simple JSON, but it becomes difficult to maintain for complex API loops, pagination, nested JSON, schema drift, retry logic, and Bronze/Silver landing patterns.

 

The pattern is more appropriate:
API
→ Pipeline / ForEach pagination
→ Raw JSON to Lakehouse Files
→ Notebook/PySpark to flatten nested JSON
→ Silver Delta tables
→ Gold Warehouse / semantic model
→ Power BI report

 

Power Query can technically do pagination with functions like List.Generate, but for production-style API ingestion I would use Fabric Pipeline + Notebook instead.

 

Also, dynamic API URLs in Power Query can cause scheduled refresh issues in the Service unless Web.Contents is structured correctly with a static base URL and RelativePath/Query.

 

So the limitation is not “Power BI Desktop cannot read JSON”.
The limitation is that Desktop is not a durable orchestration tool for API ingestion and semi-structured ELT.

🔍Parchitect
Solutions Architect · Microsoft Fabric Specialist

💡Helpful? Kudos are appreciated.
✔️Solved? Mark as Solution so others can find it faster.

View solution in original post

2 REPLIES 2
Parchitect
Solution Sage
Solution Sage

For this scenario I would not use Power BI Desktop as the main ingestion engine.

 

Power BI Desktop / Power Query can handle simple JSON, but it becomes difficult to maintain for complex API loops, pagination, nested JSON, schema drift, retry logic, and Bronze/Silver landing patterns.

 

The pattern is more appropriate:
API
→ Pipeline / ForEach pagination
→ Raw JSON to Lakehouse Files
→ Notebook/PySpark to flatten nested JSON
→ Silver Delta tables
→ Gold Warehouse / semantic model
→ Power BI report

 

Power Query can technically do pagination with functions like List.Generate, but for production-style API ingestion I would use Fabric Pipeline + Notebook instead.

 

Also, dynamic API URLs in Power Query can cause scheduled refresh issues in the Service unless Web.Contents is structured correctly with a static base URL and RelativePath/Query.

 

So the limitation is not “Power BI Desktop cannot read JSON”.
The limitation is that Desktop is not a durable orchestration tool for API ingestion and semi-structured ELT.

🔍Parchitect
Solutions Architect · Microsoft Fabric Specialist

💡Helpful? Kudos are appreciated.
✔️Solved? Mark as Solution so others can find it faster.

@Parchitect  Thank You, i was wondering how to do this

Helpful resources

Announcements
FabCon and SQLCon Barcelona 2026

FabCon & SQLCon – Barcelona 2026

Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.

July Fabric Update Carousel

Fabric Monthly Update - July 2026

Check out the July 2026 Fabric update to learn about new features.

Top Solution Authors