We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
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.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 6 | |
| 4 | |
| 3 | |
| 2 | |
| 2 |
| User | Count |
|---|---|
| 11 | |
| 10 | |
| 7 | |
| 7 | |
| 6 |