The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
Hi Team,
@Anonymous
We have a dashboard created with Bex Query(Test1) due to some complexity in this query we are planning to change the data source to Bex Query(Tes2) only the query name changes rest everything remains same . How to perform this and what are the precautions that need to be taken care ? and after publishing will there be any problem for refresh?
Regards,
Husna
Solved! Go to Solution.
@Anonymous ,
What I typically do is create a new source/connection to the new report from the Power Query Editor. Once you've connected to the query (in power query) then I open the advanced editor and then I copy the m-script for both queries to notepad and compare then and update my primary query where needed. If you look at the image below the only things that could potentially change and need to be updated are in red. If the query is against the same data source then your Source (line3) will proably not need to be changed. Line 4 is the query name and that will need to be updated. You'll need to pay attention to the parameters and make sure that you're user the same type of parameters in the bex query, if not pay special attention and make the changes to lines 7 and 8 where needed. The last part will be the measures, make sure you look at those as (I beleive) measueres have a different value in each report. It may be the same measure in each report but I beleive that value of that measure when stored in the database gets a unique name that associates it with that query. So you'll want to look at those and make changes where necessary.
However, If the queries are identical, same columns, same measures in (I believe in teh same order) then you should just be able to copy the m-script from the advanced editor of the new query and paste it into the primary query advanced editor screen and it should just work.
HI @Anonymous,
As lmf232s said, you need to confirm these data sources have the same data structure first. (check query steps to fix not matched keys and fields if their structure not matches)
You can refer to the following links to know how to parameterize your report connection string or create a template file that can generate reports based on different connection strings:
Deep Dive into Query Parameters and Power BI Templates
Using the Power BI Service Parameters to change connection strings (To possibly change between Dev
Regards,
Xiaoxin Sheng
HI @Anonymous,
As lmf232s said, you need to confirm these data sources have the same data structure first. (check query steps to fix not matched keys and fields if their structure not matches)
You can refer to the following links to know how to parameterize your report connection string or create a template file that can generate reports based on different connection strings:
Deep Dive into Query Parameters and Power BI Templates
Using the Power BI Service Parameters to change connection strings (To possibly change between Dev
Regards,
Xiaoxin Sheng
@Anonymous ,
What I typically do is create a new source/connection to the new report from the Power Query Editor. Once you've connected to the query (in power query) then I open the advanced editor and then I copy the m-script for both queries to notepad and compare then and update my primary query where needed. If you look at the image below the only things that could potentially change and need to be updated are in red. If the query is against the same data source then your Source (line3) will proably not need to be changed. Line 4 is the query name and that will need to be updated. You'll need to pay attention to the parameters and make sure that you're user the same type of parameters in the bex query, if not pay special attention and make the changes to lines 7 and 8 where needed. The last part will be the measures, make sure you look at those as (I beleive) measueres have a different value in each report. It may be the same measure in each report but I beleive that value of that measure when stored in the database gets a unique name that associates it with that query. So you'll want to look at those and make changes where necessary.
However, If the queries are identical, same columns, same measures in (I believe in teh same order) then you should just be able to copy the m-script from the advanced editor of the new query and paste it into the primary query advanced editor screen and it should just work.
Thank you @Anonymous
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
User | Count |
---|---|
110 | |
82 | |
63 | |
54 | |
52 |
User | Count |
---|---|
127 | |
118 | |
81 | |
65 | |
64 |