roalexan's avatar
roalexan
Microsoft Employee
10 years ago
Status:
Needs Votes

Support changing a dataset query from DirectQuery to import

I didn't see a way to change an existing dataset query from DirectQuery to import (I didn't check vice-versa, but probably that way isn't supported either). I hit this when I was using a query and hoping NLP would work, and found out that it has to be import, not DirectQuery. I could't find an easy way to change my dataset query, so I made a new one. BTW, I was considering asking for NLP to support DirectQuery, but let me think about that one a little more.
power bi

5 Comments

  • ankitpatira's avatar
    ankitpatira
    Community Champion
    6 years ago
    you can do this now wtih power bi desktop latest update. Once connected to data source via DirectQuery there will be an option on bottom right hand corner to change to import.
  • mpiecyk's avatar
    mpiecyk
    Microsoft Employee
    6 years ago
    I would also like this feature to be able to import the latest data to RAM instead of query a slow data source with historical data. There is still no option to change this in the Data Source Settings once you spent the time to write your .pbix.
  • michael_seim's avatar
    michael_seim
    New Member
    1 year ago

    I'm going to be blasting this same comment in all of these ideas. Idea consolidation is clearly in order. I recommend others who agree to upvote all the listed ideas.


    This really needs to happen. The issue of being unable to switch from IMPORT-to-DIRECTQUERY is truly a problem. I know it's possible to switch from IMPORT-to-DIRECTQUERY. The lack of IMPORT-to-DIRECTQUERY is a productivity killer. Field renaming. Measure recreation. Calculated column recreation. Visuals coping and pasting. It's an awfully unproductive exercise.


    I understand there are differences between the two storage modes and that there are some things that might break if one switches from one direction to another. That's fair. But why not just alert the developer? As it is, there's no alert or guidance to make it happen because the entire concept of switching is not possible. Stranger still, what of those situations where there are no confounding problems? Even then it's just not possible.Look at all these tickets saying the same thing as early as 2018!


    Please, would someone please chart a path forward to finally allow switching from IMPORT-to-DIRECTQUERY as you've previously provided the ability to go from DIRECTQUERY-to-IMPORT?

  • michael_seim's avatar
    michael_seim
    New Member
    1 year ago

    SAME IDEAS EFFECTIVELY: https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=092d297b-314a-4055-b9b9-54612da7fa90 - https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=583aebfa-28e8-ee11-a73d-6045bd7ec416 - https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=5a31afd5-2fde-ed11-9139-281878e6855d - https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=5cff6c7b-4749-ec11-a3ee-281878bd6ffd - https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=5d7750ca-02ec-4ecc-80c9-c9002bd99483 - https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=71b6a580-6a4a-4ae0-b30c-055382be84f1 - https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=7dd9e8f0-836a-4e1f-90ab-a45e9f789d35 - https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=826baedb-37b1-4213-be9f-2119e127c347 - https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=a172bf22-6dca-4fa8-9ff1-e63bdace8f2e - https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=a210eee1-6f5d-ec11-a3ef-281878bd2252 - https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=bbbf8b73-072a-ef11-8ee8-000d3a0dfcaf - https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=d4743ce5-2ffa-4645-909e-e57ecbaa3c7f - https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=f57712dc-948d-4645-b5b3-4595ad6d2bff

Recent ideas