web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Unable to remove/desel...
Power Apps
Unanswered

Unable to remove/deselect Dataverse entities once marked for export in Fabric OneLake export.

(4) ShareShare
ReportReport
Posted on by 14

I have configured Fabric OneLake export in PowerApps to export D365FO entities configured in Dataverse. The issue I am facing is that when a entity is marked/selected for Fabric export it is locked and can never be deselected again. In my case all 400+ available Dataverse ententes were pre-selected (erroneously) when configuring the Fabric export, and they can now not be deselected. In reality I am only interested in a few specific D365FO (mserp) entities. 

 

Is this intended behavior, or am I experiencing some bugs in my PowerApps solution? 

 

I have tried from multiple machines, and multiple browsers. Still no luck.

I have tried recreating the PowerApps environment, but still experiencing the same issue with a new environment.

 

The below image shows the view I am referring to. New tables/entities can be marked for export here - and the export works fine. But once marked, they can never be removed. Nothing happens if I click on the check marks / circles. They cannot be unselected.

 

Fel_0-1705475259704.png

 

The documentation states that you should be able to both add and remove selected tables..

Link your Dataverse environment to Microsoft Fabric and unlock deep insights - Power Apps | Microsoft Learn

Fel_1-1705475489608.png

 

What am I missing here? 

 

Thanks!

I have the same question (0)
  • Jonathan Manrique Profile Picture
    2,687 on at

    Hi @Fel 

     

    Remember that these functions are in preview and can fail sometimes, it has happened to me before with Virtual ENtity to connect in DFO or dual write, when they come out they can have unexpected behaviors.

    Suggestion of what I had to do, restore the last copy at the time, I understand that you are not doing it in production

    Open the typical ticket to Microsoft

     

    If I have answered your question, please mark your post as Solved.
    If you like my response, please give it a Thumbs Up.
    You can accept more than one post as a solution

  • Fel Profile Picture
    14 on at

    I will report this to Microsoft as suggested. 

    What do you mean when you say "restore the last copy at the time"? 

    Thanks!

  • Jonathan Manrique Profile Picture
    2,687 on at

    Hi @Fel 

     

    The work environments keep backup copies of your database and components when there are circumstances where there may be damage, you can restore the latest backup version you have

     

    Jmanriquerios_0-1705480823876.png

     

    If I have answered your question, please mark your post as Solved.
    If you like my response, please give it a Thumbs Up.
    You can accept more than one post as a solution

     

  • Fel Profile Picture
    14 on at

    I see, thanks. Since the problem is re-introduced even if i scrap the entire PowerApps environment and create a new one from scratch, I would assume restoring wont fix anything for me. I will contact MS and see if they can assist! 

  • stekum70 Profile Picture
    5 on at

    Should all be GA already ... Documentation is just very limited and as a result of this it is difficult to tell whicvh limitations are by design or more of a bug. Think this applies to Fel questions very much - I am experiencing the same and am desperately waiting for Microsoft to clarify this... 

  • Andrey_Hamburg Profile Picture
    5 on at

    Hello, I can confirm this behaviour: tables from Dataverse, which are initially copied to OneLake when creating a link, cannot be unselected later. Even more: also tables from "D365 finance & operations" (which are available via Synapse link) cannot be unselected if once exported.

     

    This is surprsing me, because some time ago (a month or so) I COULD unselect Dataverse-tables after we exported them. So, the feature of "unselect" has disappeared)

     

    Regards from Hamburg

  • Andrey_Hamburg Profile Picture
    5 on at

    Update: "Unselect" on Dataverse-tables works properly after all of them once exported. So, I left my initial copy over night, and today I could unselect all of them with one click.

  • stekum70 Profile Picture
    5 on at

    Thanks for the update Andrey! Unfortunately i don't understand what you did to make it work - can you provide a few more details on how you do this? Thxs!

  • HelgeSchroeder Profile Picture
    2 on at

    I am also very curious about this! Did you really manage to unselect?

    I am not able to unselect any Dataverse tables. Annoying to have 499 dataverse tables synced and it seems to slow down all views for managing tables + my Onelake is full of unneccessary items.

  • CU06080623-0 Profile Picture
    on at
    Any update on this? 
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 796 Most Valuable Professional

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 327 Super User 2025 Season 2

#3
Power Platform 1919 Profile Picture

Power Platform 1919 268

Last 30 days Overall leaderboard