I can't drop a table in Dataverse

[TonyCasilla]

For a few weeks now I have been trying to delete a dataverse table, this table is a virtual table connected to SQL server, I have already tried several solutions that are proposed in this forum, the practical solution is to delete the connection or the table, the problem is that I create an application and I added a button then delete that application but don't delete the botton now I just can't delete the references that that table has nor can I restart the connection since that connection tried to delete the references to that connection but it has orphaned references from PowerAutomate now simply the table cannot be dropped.

[dpoggemann]

Hi @TonyCasilla ,

Have you checked dependencies on the table? Please see the following article https://carldesouza.com/how-to-find-dependencies-when-deleting-resources-in-dynamics-365-power-apps/ that explains how to check for dependencies.  I expect you might have this table setup in a relationship with another table (i.e. N:N or lookup column on another table).  

If you did remove the dependencies on all other tables, verify you "publish all customizations" and then try to remove the table.

[TonyCasilla]

@dpoggemann  Thanks for answering, Yes I checked all the dependencies in the table, I removed most of them but there are a couple of those references that were found in a modeldriven application that I had already removed now, so they are orphan dependencies, or is there another way to access that application that I already deleted so I can delete those dependencies?

[EricRegnier]

Hi @TonyCasilla,

The 2 dependencies you highlighted are custom command bar button(s) in your model-driven app. Open the command designer and look for those and delete the button(s) or remove the references in PowerFx of the table you want to delete. Note you'll also have to delete the table in the Component Library, to do this:
In the command designer, open the Component Library:

Then click on Data on the left, --> find that table you want to delete and remove it. Don't forget to save all and publish the Component Libary.

Hope this helps!

[dpoggemann]

Hi @TonyCasilla ,

It looks like you might still have a custom action and a canvas app that still have dependencies.  Do these still exist?  I have had a situation recently where we could not remove the dependency and we had to contact Microsoft Support for them to remove but that is very rare for me.  

Do you have a custom workflow action that might exist as well that would be the app action?

Help for removing dependencies here:  https://learn.microsoft.com/en-us/power-platform/alm/removing-dependencies 

[TonyCasilla]

@EricRegnier  Thanks for your answer, but maybe I don't explain the problem well, the problem is that the model-based application to which those dependencies refer has already been eliminated and I can't access it. I wanted to know if there is another way to access that application that I deleted

[EricRegnier]

Are you saying you can’t access the model-driven app anymore once you deleted the table? What is the error you are getting, a screenshot would help. Thanks

[TonyCasilla]

Act One :Delete the model-driven app.

Second Act: Then I tried to delete the table but I couldn't because it made references to those 2 buttons that were inside the application that I deleted previously.

Third Act: Contact the Microsoft service without receiving a response

[dpoggemann]

Hi @TonyCasilla ,

Did you open your component library and try removing the custom buttons and table as a data source?

[TonyCasilla]

Hola @dpoggemann ,

I deleted the solution in which I created the model-based application, so I can't access that component library, I assume that those buttons that I highlighted above are orphan dependencies, I mistakenly assumed that if I deleted the solution I also deleted all the dependencies but This was not the case, the dependencies were orphaned, now I cannot access the component library because it no longer exists.

I tried to add that table to another solution and thus be able to access the component library but those buttons do not appear.