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.
Reference my post:
Does this sound like a disparity between the desktop functionality and what's available as GA on the service?
I didn't think I was doing anything unusual. Its an ODBC error but I wonder if this is slightly misleading... IDK?
Any help or further advice would be great thanks.
Hi @music43 ,
It seems that you use parameter in datasource, right? As I know, Power BI currently does not support parameterized data source definitions, also known as dynamic data sources. For example, you can't parameterize the data access function Sql.Database("SqlServer01", "AdventureWorks"). If your dataset relies on dynamic data sources, Power BI informs you that it detected unknown or unsupported data sources. You must replace the parameters in your data access functions with static values if you want Power BI to be able to identify and connect to the data sources. For more information, see Troubleshooting unsupported data source for refresh.
You could refer to Data refresh in Power BI for details.
Best Regards,
Zoe Zhi
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi Zoe
Thank you for your reply. I am confused and I will explain why:
Model A: This refreshes in the PBI desktop and has been successfully setup to refresh in the service each night.
This model uses a parameter to hold the ODBC DSN name.
The query that pulls in the parameter value looks like this:
As you can see this is successfully returning data in the desktop:
And in the service allowed configuration and has been working for several months.
Model B: This refreshes in the PBI desktop but refresh displays an error in the service preventing setup of scheduled refreshes.
This model uses a parameter to hold the current Environment.
Which in turn filters a small table holding the appropriate ODBC and Database library details.
It is these results which are being split out to referenced queries and “Drill Down” as follows:
These work like parameters and feed into the query:
And in the desktop, return data as expected.
But in the service we just get this error:
Sorry for all the images, but I guess it explains better than I can 🙂
Hi @music43 ,
As I mentioned above, then you set refresh, the dynamic datasource can't support, so you need to make sure you have set fixed parameter value in Dataset setting ->Parameters. Then it should work well.
Or you also could open a support ticket(create a support ticket, which might not be for free) on https://powerbi.microsoft.com/en-us/support/
Best Regards,
Zoe Zhi
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Power BI Version: 2.76.5678.782 64-bit (December 2019)
Gateway Version: 3000.21.18 (December 2019)
I have tried to establish if this is a limitation or a bug:
https://community.powerbi.com/t5/Power-Query/ODBC-Unsupported-function/m-p/902260#M30910
Hopefully you can shed some light...
Thanks
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 | |
11 | |
8 | |
8 | |
7 |
User | Count |
---|---|
15 | |
13 | |
9 | |
6 | |
6 |