Microsoft support for Dataverse

[Tal22]

I need to send a request to have a few Dataverse columns deleted. Does anyone know where I can reach the right tech support to request this? 

[a33ik]

Hello,

Which columns and in which entity do you want to delete?

[Jmanriquerios]

Hi @Tal22 

To open a ticket to MSFT you can do it at https://admin.powerplatform.microsoft.com/environments, and in the icon that I show you in the image

Except that MSFT may not eliminate any columns since all the columns present in the data model are necessary within the logic of the model. Additionally, by definition, managed solutions cannot delete elements.

Therefore, it would be important to know which column you want to delete, because if they are personalized you can delete them yourself.

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

[Tal22]

I want to delete two columns using choices. Unfortunately, these columns are linked to dependent objects, Views, which cannot be deleted. I suspect the only way to delete these types of columns is for Microsoft to do so.

[Jmanriquerios]

Hi @Tal22 

IF they are managed components, they will not be removed,

[Tal22]

I don't have Global admin privileges so I cannot access to the "Host" environment you displayed. I will have to send this to IT person and hope they can figure this out. 

[Fubar]

@Tal22 I am not sure what your experience level is, so if this is not relevant please ignore it.  Generally speaking when there are dependencies all you need to do is edit the item showing in the dependency to remove it and then Publish e.g. edit a view, remove the column, then Publish, then remove the column from the Table.  

Exceptions to this would generally be where the items are in Managed Solutions and those solutions components have been locked down by the Publisher of those solutions so you cannot modify their components.  If your issue is that it has been locked down in a managed solution, then Microsoft probably won't assist you, you would need to discuss with the Publisher of the Managed Solution.

[Tal22]

The table I want to remove two columns from is not managed. I am not sure we are on the same page, but on my system, Dataverse tables with any columns with Choice data types cannot be removed. Dependencies are baked in and cannot be modified. I am developing in Access, using it as a front end. I initially decided to use Dataverse as the backend to migrate to mobile apps. However, with these types of Dataverse issues and poor editing and modification features, I am hesitant to invest my time in Power Apps. Should I go back to tried and true SQL server and forget about mobile apps and the Power Platform until it becomes a more mature product?  

I could use some guidance here. 

[Jmanriquerios · Accepted solution]

Hi @Tal22 

Power Apps are applications that have many years of experience and are mature enough for large organizations to use, even the Dynamics 365 modules are Power Apps with other business logic based on the nature of the process.

Another thing you should know is that Dataverse is a SQL with rich logic and metadata included and this is where you should start to understand how the model works.

There are certain components like Choices that cannot be removed because they are part of that meta, but the fact that they cannot be removed does not mean that you have to use them.

Dataverse and Model Driven Apps bring a series of components already built that you decide whether to use or not.

I'll give you an example, there is a table called account, you decide if you use it or not, if you don't want to use it you can create a new table.

In the case of Choises it is exactly the same, for example there is one called industry, you decide if you use it under the given scheme, or create a new one.

The issue having dependencies is not necessarily a problem because in the end you decide what is seen or not within an application, if you do not want that field to be seen you remove or hide it from the form or a view.

In the end it is understanding how a tool that has been working perfectly for years and that evolves to improve many processes works.

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