Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
Isn't it better/optimized to call the function in a new table for every new request made instead adding it to the main table and having it repeat all the previous data inside the table just to relate to the new data inserted? If it is definitly better, please let me know how to do it.
Power Query – Building functions to fetch web data
Example:
main_table
A | B | C |
C | A | B |
B | C | A |
>function to made web crawling with data of main_table as illustred in the link before.
main_table
A | B | C | 1
A | B | C | 2
C | A | B | 1
C | A | B | 2
B | C | A | 1
B | C | A | 2
A new table for each new request? That sounds to me like you'd end up with way too many tables.
Depends on the requested data, but it isn't better than having a lot of duplicated data?
I think it's usually easier to de-duplicate data than handle lots of tables but I can't speak to your specific use case.
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Join Fabric Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.
| User | Count |
|---|---|
| 8 | |
| 6 | |
| 5 | |
| 4 | |
| 4 |