Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for a $400 discount.
Register nowGet inspired! Check out the entries from the Power BI DataViz World Championships preliminary rounds and give kudos to your favorites. View the vizzies.
I have a published report (report A) which is pulling data using import mode from a datasource.
I created another report B which is pulling data from semantic model of report A.
The data is automatically pulled in the directquery mode and there is no bar in the model view which allows me to change to import mode.
Is this the default behaviour in this situation and is there any way to circumvent this?
Solved! Go to Solution.
Thanks for the reply from vicky_ , please allow me to provide another insight:
Hi, @afaro
Thanks for reaching out to the Microsoft fabric community forum.
My idea is basically similar to vicky_'s.In fact, when you use the semantic model of Power BI as a data source, its connection mode is Live connection. Below is a screenshot from the official documentation:
What's the difference between live connections and DirectQuery? - Power BI | Microsoft Learn
This is my test result:
Once this connection mode is established, it cannot be directly converted to other storage modes (such as Import mode or DirectQuery mode).
The reason you believe it to be DirectQuery is that you have added other data sources to the PBIX file, transforming it into DirectQuery storage mode.
However, within a composite model, the original storage mode cannot be altered.
If you need to maintain their storage mode as Import, it is recommended that you connect the data source of Model A and select the storage mode as "Import". This will transform it into the composite model referred to by LL, which is currently the most efficient solution.
Of course, if your newly connected data sources are also in DirectQuery storage mode, then the overall storage mode will remain DirectQuery.
Of course, if you have any new discoveries or questions, please feel free to get in touch with us.
Best Regards,
Leroy Lu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks for the reply from vicky_ , please allow me to provide another insight:
Hi, @afaro
Thanks for reaching out to the Microsoft fabric community forum.
My idea is basically similar to vicky_'s.In fact, when you use the semantic model of Power BI as a data source, its connection mode is Live connection. Below is a screenshot from the official documentation:
What's the difference between live connections and DirectQuery? - Power BI | Microsoft Learn
This is my test result:
Once this connection mode is established, it cannot be directly converted to other storage modes (such as Import mode or DirectQuery mode).
The reason you believe it to be DirectQuery is that you have added other data sources to the PBIX file, transforming it into DirectQuery storage mode.
However, within a composite model, the original storage mode cannot be altered.
If you need to maintain their storage mode as Import, it is recommended that you connect the data source of Model A and select the storage mode as "Import". This will transform it into the composite model referred to by LL, which is currently the most efficient solution.
Of course, if your newly connected data sources are also in DirectQuery storage mode, then the overall storage mode will remain DirectQuery.
Of course, if you have any new discoveries or questions, please feel free to get in touch with us.
Best Regards,
Leroy Lu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Yes, it is normal that you won't be able to change to import mode. However, you are able to use a composite model - https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-composite-models
basically the model from Report A can't be changed, but you will be able to import new tables, add columns etc. to those new tables. However, you cannot create calculated columns based on data from Report A (so something like CALENDARAUTO() would prevent your report from refreshing once it's published)
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the February 2025 Power BI update to learn about new features.