Notifications
Announcements
In Power Apps, under tables either directly under environment or solution the creation process fails with the error message "Failed to create entity with logical name..." Tried in multiple environments. The one that worked in the morning is not working in the evening.
Followed other suggestions to check the user roles and i have System Administrator and also now added System Customiser. But no luck
@LearnerPP
Are you trying to create the table with the same name or under a different name?
Any more details about the error message?
It's a new developer environment and creating the table for the first time.
Found it really intriguining. I tried to create table in the name of "Test". I got the same error message. I tried create a table in the name of "Tesst". It got created. Any other table name it is not accepting and getting the same error message.
I have the exact same issue. This is a production environment where i have been regularly creating tables . About a month ago there was a perhaps related issue that happened to me (and some others) where new tables were being created without default forms and views. This issue was solved for some people and not for others. I wrote to support a month ago and it took them 15 days to just have initial contact. They said this is a known issue that the product team has mitigated but it wasn't working for me.
About a week ago the issue worsened and now table creation fails completely with the same error mentioned in this thread. This means adding new functionality in my production environment has become impossible and yet the request remains at just severity C.
Have tried to contact support repeatedly but there is zero communication save for initial contact a fortnight ago! On another support request I was told they are facing a lot of backlog ( I am in India and this may be region specific). Unbelievable that such critical support requests for businesses are being marked as lowest severity and taking weeks to even begin communication.
Thanks Rutu01. But couldn't find anywhere MS acknowledging this as problem and the ETA for this. The problem still persists.
Hi LearnerPP. Support told me that tables being created without default forms is a known issue. This was 15 days ago and haven't heard again from them inspite of repeated emails. And now the issue has worsened where table creation is failing entirely with the exact same error that you are facing. Also this is happening in all my environments ( production, default etc) and even across my other tenants so i don't think this is related to any setting or permission on your side but most likely a Microsoft bug. I would suggest you to raise a support ticket too, especially with the long wait times (it's been a month for me) . Will update you if i find any solution
Thanks Rutu01. Wow, a bug without workaround!
When we create tables, i don't remember seeing an option for default form.
I tried connecting through SQL Studio, but it allows read-only. Are there other ways to connect with Dataverse?
Interestingly found a workaround when I checked what you leave everything default and try. Earlier I was entering the Primary Column details as well while creating the table. Now i just only entered the table name and hit save with all default selected options. it worked.
Also I could see a "UniqueIdentifier" type column is also created now. Earlier, we were able to change this column type (as per the learn portal) to autonumber and provide a seed value. Now that has become un-editable.
@LearnerPP You're right, as long as any of the advanced options are not changed the error does not arise. As far as i know, the unique identifier column is system generated, it is the primary name column that can be set to autonumber/simple text.
I spoke to support and now I am getting regular updates on the issue status. Today table creation is proceeding without any errors in all of my environments and tenants even on selecting advanced options.
Default forms and views are still not being created however they said that is a known issue and they will push the changes for that soon. On creating a form manually the defaults then do get created
Thanks Rutu01 for the update. The noted difference was the Id was automatically prefixed to the autogenerated uniqueidentifier type primary column. The previous day it was not the case. Not sure whether it allows two fields with same name but of different types.
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.
In our never-ending quest to improve we are simplifying the forum hierarchy…
We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
WarrenBelz 721 Most Valuable Professional
Michael E. Gernaey 320 Super User 2025 Season 2
Power Platform 1919 268
