Forum Discussion
Passing bearer token generated in one query to another query returning a Formula.Firewall error
The thing is that privacy levels are the cause for your Formula.Firewall error - and are a good way to warn you that you are combining data from different sources (maybe you don't trust them all) -> "ignoring privacy levels" (warning: are you sure? ARE YOU REALLY SURE?) 🙂 should clear the error and allow you to continue with the exploration.
I tested your snippets locally with minor changes and they work with "ignore privacy level" set.
P.S. Don't know how many rows you will have in that single column table, but each row will hit the api endpoint with a request... fast. If you have MANY rows and control over the api, after testing if you get not so good performance, one option could be to batch together multiple rows in a single request.
Thanks for reaching out...
The report i am building now is to explore how to the API requests from Postman to Power Query, and it will not published to a shared workspace. That is why i have hardcoded the username and api_key for now.
The next step will be to create a custom connnector, and at that step Privacy levels settings will be considered....
Hope i did answer you question/comment.
Responsive ResidentThe thing is that privacy levels are the cause for your Formula.Firewall error - and are a good way to warn you that you are combining data from different sources (maybe you don't trust them all) -> "ignoring privacy levels" (warning: are you sure? ARE YOU REALLY SURE?) 🙂 should clear the error and allow you to continue with the exploration.
I tested your snippets locally with minor changes and they work with "ignore privacy level" set.
P.S. Don't know how many rows you will have in that single column table, but each row will hit the api endpoint with a request... fast. If you have MANY rows and control over the api, after testing if you get not so good performance, one option could be to batch together multiple rows in a single request.