Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live now!
I'm fairly new to Power Query so I'm not entirely sure exactly what you would call what I'm looking for. I wasn't even sure what to search for.
I have the query in Excel that is shown below. In the request the "Device", circled in blue, is entered. I have a list of devices that I would like to get the data from.
I have a few ideas on how I might think of doing this but I'm wondering if there is a "Best practice" way to do this, IE an easy way to do this.
The list of devices I can create either via another query or create a table in the same Excel from a query. My thoughts were.
1) Somehow make the device a variable but was not sure if it would cycle thru the list. I tried this and it gave me an error saying it was a list.
2) Try the same thing as above with a relative path.
3) Create a loop in some way combined with the variable in the path
4) Brute force it by duplicating the entire thing and having each device request with a seperate device and then combine the results.
Output I'm looking for is below but I want multiple devices in the device column.
Device list looks like this.
Any guidence would be appreciated.
Thank You
Hi @Anonymous ,
Have a look at this solution I provided a while back along these lines:
https://community.powerbi.com/t5/Power-Query/How-to-deal-with-paginated-API/m-p/3222229
It's not precisely the same as your scenario, but I think the principle is what you're after - you would just edit the solution so you start with, and parameterise, a list of device IDs rather than a list of page numbers.
Pete
Proud to be a Datanaut!
I'm playing with this and for some reason something is not working. I believe it may be a syntax issue, but I'm clueless as to what it would be.
With this code
I'm getting this "Bad request". Unless I'm entirely mistaken the bad request indicates that I'm getting where I need to be because the site is responding but something on the data I'm sending is no good. I've noticed a bunch of things that are different from what I have in the script to the response of the bad request but I have no idea what is "Normal Different" and what is "Bad request" bit.
Any help would be appreciated
Thank You
I would agree that that is the concept. In my case the results of the query will need to go into the relative path. Does that sound correct?
The Power BI Data Visualization World Championships is back! It's time to submit your entry.
| User | Count |
|---|---|
| 16 | |
| 9 | |
| 8 | |
| 7 | |
| 7 |