Forum Discussion
Power BI downloaded PBIX does not contain Power Query queries
Hi everyone,
I am having a very confusing issue with a Power BI report and I would appreciate some guidance.
Background
I inherited a Power BI report created by another developer.
The report is published in Power BI Service and uses several Azure Functions as data sources (REST APIs returning JSON).
Current sources include endpoints like:
- /api/get_jira_epics
- /api/get_jira_tasks
- /api/get_jira_sprints
The report itself works correctly in Power BI Service.
Problem 1 – Downloaded PBIX has no queries
When I download the report from Power BI Service as:
“A copy of your report and data (.pbix)”
and open it in Power BI Desktop:
- the report visuals appear correctly
- the dataset exists
- BUT when I go to:
Transform DataNo queries are visible at all.
So I cannot see or edit the original queries created by the previous developer.
This makes me think the report may be:
- connected to a semantic model
- or partially live-connected
but I am not fully sure.
Problem 2 – Adding a new Azure Function breaks the report
I created a new Azure Function endpoint:
/api/get_pmo_weeklyWhen I add it in Power BI Desktop using:
Get Data → WebHowever, after:
Close & ApplyAll visuals start showing errors such as:
There was a problem with one or more fields
The column 'CW_Tasks_Expanded[Week Start]' either doesn't exist
Error fetching data for this visual- existing tables disappear
- relationships break
- measures become invalid
- old visuals lose references
even though I only added one new Web source.
Additional context
The report uses:
- Azure Functions (REST APIs)
- MySQL Azure database
- multiple DAX measures
- custom visuals
- slicers based on week ranges
My goal was simply:
- add a new table (PMO_Weekly)
- keep all existing tables intact
- create new visuals/measures using the new weekly data
But adding the new source seems to destabilize the whole model.
Questions
- Why are the original Power Query queries not visible in the downloaded PBIX?
- Is this behavior expected for reports connected to semantic models/thin reports?
- Why would adding a single new Web source cause existing tables/measures/visuals to disappear or fail?
- What is the correct approach to extend this kind of report architecture?
Any help would be greatly appreciated.
Hi aliciaortega93,
Thank you, MFelix jgeddestayloramy for your insights,
The PBIX file uses a DirectQuery or composite model architecture rather than the standard Import model, which is why the Power Query view appears empty. According to Microsoft documentation, adding local or import tables to a DirectQuery semantic model creates a composite model, which can result in limited relationships across sources and may lead to unexpected calculation or relationship issues. Adding the PMO_Weekly source probably changed the model’s structure and affected existing relationships or metadata. The best practice is to extend the original semantic model rather than make changes directly in the downloaded PBIX.Use composite models in Power BI Desktop - Power BI | Microsoft Learn
Composite model guidance in Power BI Desktop - Power BI | Microsoft Learn
Download a Report from the Power BI Service to Power BI Desktop - Power BI | Microsoft Learn
Use DirectQuery in Power BI Desktop - Power BI | Microsoft Learn
Thank you.
11 Replies
- jgeddes
Super User
- aliciaortega93Regular Visitor
Thank you so much for your reply! If I go there, I see the following:
Any ideas what should I do next?- jgeddes
Super User
You can drag any of the elements from the Expression list, or any of those categories, onto the main screen. The coding will then populate. From there hopfully you can get a bit more insight into the connections in the model.
- aliciaortega93Regular Visitor
When I add the new conecction (PMO_Weekly table) it shows errors:
And I reallized that all the relationships of the model are gone:
- v-saisrao-msft
Community Support
Hi aliciaortega93,
Thank you, MFelix jgeddestayloramy for your insights,
The PBIX file uses a DirectQuery or composite model architecture rather than the standard Import model, which is why the Power Query view appears empty. According to Microsoft documentation, adding local or import tables to a DirectQuery semantic model creates a composite model, which can result in limited relationships across sources and may lead to unexpected calculation or relationship issues. Adding the PMO_Weekly source probably changed the model’s structure and affected existing relationships or metadata. The best practice is to extend the original semantic model rather than make changes directly in the downloaded PBIX.Use composite models in Power BI Desktop - Power BI | Microsoft Learn
Composite model guidance in Power BI Desktop - Power BI | Microsoft Learn
Download a Report from the Power BI Service to Power BI Desktop - Power BI | Microsoft Learn
Use DirectQuery in Power BI Desktop - Power BI | Microsoft Learn
Thank you.
- MFelix
Super User
Hi aliciaortega93 ,
This can be because of the type of connection that the report uses check on the bottom rigth corner of your model what is the type of connection, Live connection, Direct Query, Import.
That will allow to pin point the question.
- tayloramy
Super User
Hi aliciaortega93,
If you open the report in desktop, then click the dropdown right beneath the transform data button in the ribbon, and click data source settings, what do you see in there?
As MFelix mentioned, nothing being in power query implies that the model is using direct query connections and not import mode.
- aliciaortega93Regular Visitor
Thank you for your reply! When I click on that, I see the following:
The last one, get_pmo_weekly is the new one I'm trying to use in the data.- tayloramy
Super User
At the top select the the first radio button to show only data sources in the report.