Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
I have a powerquery custom connector that authenticates against Auth0. The authentication call has a bunch of parameters (such as clientId, environment, audience, etc...), most of which don't change when different users log in. I have reduced the UI that prompts the user at signin-time to the bare-essential information (project name and clientId in this case) and the rest of them I get from an array containing default values.
This works, but what I want to do is have those "hard coded default values" put into some more easily accessible config location, such as a config file. I think a complicating factor in my request is that this place where I want to put my default parameters will have to be accessible before the user authenticates and has full access to the Power BI environment.
Is this possible? Or am I stuck with having these parameters hard-coded in the powerquery code?
Anyway, I hope my question is clear enough.
Thanks for the suggestion. Unfortunately, your idea assumes (if I follow your thinking correctly) that the config data is fixed and unchanging. Unfortunately, it is dynamic content and may be different every time you sign in. Also, the source data is, unfortunately, secured, so it is only accessible after the client has been authenticated.
I am wondering if it would be possible to add some sort of code in the "finish login" function, (somewhere else) that then gets the secure data and displays it to the user
Hi @apdams ,
Has your problem been solved? If so, please kindly accept the helpful reply as solution, then we'll close the thread, other people who has the similar problem will benefit here.
Best regards,
Communtiy Support Team_yanjiang
Hi @apdams ,
Try to use a JSON file to store your configuration data. You can then read this file using Power Query's Web.Contents() function and parse the JSON response using the Json.Document() function. To make this configuration file accessible before the user authenticates, you can store the file in a location that is accessible to all users, such as a shared network drive or a cloud storage service. Alternatively, you can embed the configuration data directly in your Power Query code as a variable or a table.
Best regards,
Community Support Team_yanjiang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
15 | |
12 | |
8 | |
8 | |
7 |
User | Count |
---|---|
15 | |
13 | |
9 | |
7 | |
6 |