Forum Discussion
Convert storage mode from direct query to import, data source as power bi datasets
Hi Anonymous ,
You can go to Power BI Desktop, go to Model view-->Advanced and change the storage mode from DirectQuery to Import .Similar issue is also resolved in this particular community post . You also follow that post :
https://community.powerbi.com/t5/Desktop/How-to-change-direct-query-to-import-query/m-p/100996Thanks ,
Pratyasha Samal
Has this post solved your problem? Please Accept as Solution so that others can find it quickly and to let the community know your problem has been solved.
If you found this post helpful, please give Kudos C
Hi Anonymous ,
As far as I know, it is not possible to convert import mode to direct query mode, But direct query mode can be converted to import mode
If you really need to change it to direct query,
my suggestion is to create a new one using direct query then copy your applied steps from your previous report.
It will be quite time consuming but it will achieve your requirement.
Thanks ,
Pratyasha Samal
Has this post solved your problem? Please Accept as Solution so that others can find it quickly and to let the community know your problem has been solved.
If you found this post helpful, please give Kudos C
Wow, how did this question get marked as resolved? Reading through this thread I can only tell that so far you haven't understood the original question, which others are asking too, and I am experiencing.
The following Microsoft articles describe that we should be able to change the import mode for semantic model tables and I certainly can't because the option is greyed out:
<https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-storage-mode>
<https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-composite-models>
Agree. I had the same issue and posted the solution I came up with, but it got placed in the middle of the thread for some reason. Here's what I did and it worked for me. And I've done it on two different reports and it worked for both. And on the second report, it was simpler because I was only pulling in one direct query table from another Power BI dataset. In that case, all you have to do is create a calculated table in your report that selects all the columns from that direct query table, and then build all of your relationships and visuals off of your calculated table instead of the direct query one. That worked fine for me.
I had this issue and was able to work around it. I believe my situation was similar to the original post in that I had a PBIX desktop report with several imported data tables from various sources. I then wanted to get data from a published Power BI dataset and be able to create relationships between that data and the other data within my report. To do this I 1) created a calculated table for each of the Power BI dataset tables I wanted, removing extra columns I wasn't interested in using the SELECTCOLUMNS function, naming each column something unique by simply prefixing the column name with the name of the original table - this is required for a future step to work, 2) created relationships between those newly calculated tables, 3) created a calculated table using NATURALINNERJOIN to combine all of those tables together into one (which will use the relationships for the join conditions and requires unique column names to work in DAX). Now I have an imported table with all of the data from the Power BI dataset that I was interested in that can be used across the other data that has been imported. Hope this helps for you.
Hey, just tried your workaround but when I come to publish the report I still get the following message. The message talks about the dataset needed to be configured to use an explicit connection but im not clear on what this means.
