cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Change Bex query as source to anothe Bex query with only name change

Hi Team,

@lmf232s 

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

2 ACCEPTED SOLUTIONS
lmf232s
Responsive Resident
Responsive Resident

@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.

2020-03-26_8-14-48 2.png

 

View solution in original post

v-shex-msft
Community Support
Community Support

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

Community Support Team _ Xiaoxin
If this post helps, please consider accept as solution to help other members find it more quickly.

View solution in original post

3 REPLIES 3
v-shex-msft
Community Support
Community Support

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

Community Support Team _ Xiaoxin
If this post helps, please consider accept as solution to help other members find it more quickly.
lmf232s
Responsive Resident
Responsive Resident

@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.

2020-03-26_8-14-48 2.png

 

Anonymous
Not applicable

Thank you @lmf232s  

Helpful resources

Announcements
Carousel_PBI_Wave1

2023 Release Wave 1 Plans

Power BI release plans for 2023 release wave 1 describes all new features releasing from April 2023 through September 2023.

Power BI Summit Carousel 2

Global Power BI Training

Make sure you register today for the Power BI Summit 2023. Don't miss all of the great sessions and speakers!

Thank you 2022 Review

2022 Monthly Feature Releases

We had a great 2022 with a ton of feature releases to help you drive a data culture.