Unable to Create new Table

[TrevorMorrice]

Hey, 

I have been playing around with powerapps and dataverse for almost a month. 

Last week had no issues. This weekend signed in and went to create a new table Asset and it spat out an error 

"No rows could be found for entity with id .... if entity were published" 

So thought that is weird so I hit create again and it spat a new error

"Failed to create entity with logical name cr021_asset and object type code -1. Exception: Microsoft.Crm.CrmException: Identifiers cannot match existing object names. An object of type Entity with same name cr021_Asset already exists." 

So...okay maybe it published the table but I cant find it anywhere? 

This same process has happened 3 times for me trying to add different names to the a new table and the 2nd try says its created already.  

 I put in a support ticket with Microsoft, I sat in a queue for 6 hours today saying I was 2nd in line and it never changed. 

Anyone have an idea? 

[EricRegnier]

Hi @TrevorMorrice,

It seems because that table already exists and note that the table names are case insensitive. When checking the list of tables, make sure to pick the "All" table as per below:

Hope this helps!

[Ben_Langley]

I think this is a global issue. I can't create new tables on multiple tenants  - Error :"No rows could be found for Entity". Doesn't matter what you try to name the table as :

[Ben_Langley]

Having the exact same issue as you have described. Inside or outside of a solution... doesnt matter what you name the table or what settings you toggle... same error

[gscott]

Having same issue as well. 

[gidiscacciati]

Same issue here. I have tested in multiple tenants and multiple environments, could not create tables in any of them

[Ben_Langley]

@EricRegnier  Still today: 

Canada region. This is serious as all development requiring new tables has stopped for us.

Cheers,

-Ben

[chams]

I had the same issue since this week and it seems that the issue is related to the latest updates. I tried creating the table outside the solution, within the solution, with Power Apps Copilot, but nothing works. I tried to clear the cache too but it didn't change anything. This is a nightmare for developers. I am able to create tables in another completely different tenant but the tenant I am working with has the problem for all environments.

Context : France Region. My tenant is in French. The other tenants are in English. Are you guys using another language that English for your environments/tenants ?

[Ben_Langley]

As far as I know we are in an English tenant. We have a centre of excellence that manages DV configuration. That said we definitely have french users and some of our apps are translated.

[chams]

I found an alternative solution to keep my development going
1. Create a new list within a Sharepoint site.
2. Set up a virtual table with the Sharepoint list
PS: You can't create new columns from Dataverse, you need to first have them in the SP list