Returning Error @ New Dataverse Table Save

[kent-culpepper]

I'm receiving a very long cryptic error (attached) upon attempting to save a new dataverse table. 

[dpoggemann]

Hi @kent-culpepper 

This appears to be an issue with a database deadlock or similar.  I would give it a bit to see if Microsoft clears it up themselves and if not open a case with Microsoft.

[FrankTheDoorman]

Solution is in import mode sounds like the solution is in a state of installation behind the Scenes. 

If you go to the power app maker portal, then choose solutions, then choose to publish all customizations. 

Also, can you check the history and post an image here?

[kent-culpepper]

It is very odd. Only if I use "Id" in the Primary Name column it results in the error.

[FrankTheDoorman]

What happens if you check solution history? Do you see any pending or stuck updates?

[kent-culpepper]

I can create\save a table no problem. Only when I use "Id" in the name of the Primary Column does it return an error.

[Fubar]

Is your Primaty Name field the same (but with Id at the end) as the Table Name.  When you create a Table it will auto create a column that is the same as Table Schema Name with a suffix of 'id' that is used to hold the records internal GUID - you cannot change this behavior - it will not let you then create a Column that has the same Schema Name as that column.

If this is the case, when you are setting the Primary Name select advanced and alter the auto generated Schema name to something else 

[poweractivate]

@kent-culpepper I tried to create a Table with Primary column name named Id and I did not get any such exception. You should not be getting this.
Are you using the full Dataverse or the lightweight Dataverse for Teams? I tested on Dataverse, and not Dataverse for Teams.

Check on admin.powerplatform.microsoft.com/environments, select the environment, and check the Dataverse version just in case, your environments should update automatically however, maybe your environment is not on the latest version?
If so you may want to file a support ticket here with Microsoft to check on it.