Unanswered

Dataverse tables refusing to use the names i set

(0) Share

Report

Posted on by BIanon

Hello,

I have set up a blank canvas apps before with SQL server as a backend, which has always been easy for me.

Now, I am trying to create a "Power Apps Teams App" which is apparantly a different thing than Powr Apps? After spending a couple of hours trying to decipher the docs I think my license type allows it but I ended up deciding I had to test it out to be sure.

I'm trying to understand how this "Dataverse" stuff works and am having a hard time

Sometimes Dataverse will just pick some random name instead of respecting the name I give the table:

When I create a table and give it a name, it's either just loaded in as "new table" or as "Reserve entity"? Is there a way where I can name my own tables?

For some reason the primary col has to be a string value? Multiple data modelling books on the shelf behind my spontanously combusted as I read that - what's the deal here?

When I create my table and organize the cols, Dataverse scrambles it so the view is nonsensical when I want to look at or edit the data. The cols I've created myself and need to see are hidden and instead it displayes useless auto-generated cols I never asked for or wanted. Can I turn this off and make Dataverse respect my decisions as the developer?

Does anyone actually use this or is it just gimmicky and I'm going to hit some wall and have to buy the big licenses anyways?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (0)

gulshankhurana 1,397 Moderator on at

Like (1)

Report

Hi @BIanon

Dataverse operates on a common data model, which includes predefined or reserved tables (formerly known as entities). For instance, attempting to create a table named 'Product' might be impossible because it's a reserved name, already utilised in Dynamics 365 CE modules that are built on Dataverse as their foundational data solution.

When you create a new custom table, it automatically generates certain components consistent with the common data model architecture, such as columns, views, and forms.

Each table comes with key columns (formerly called fields) that are created automatically, like 'created on' and 'status'. This explains the presence of several 'auto-generated' columns in the tables you create. Dataverse allows you to create/modify views to display only the desired columns. You can also sort and filter records according to your requirements.

I acknowledge that you have reviewed several documents thus far. Nevertheless, I would recommend exploring the structured learning module titled 'Getting Started with Microsoft Dataverse' to help address some of your concerns:

Get started using Microsoft Dataverse - Training | Microsoft Learn

If, like me, you prefer watching videos over reading documentation then you may find this video helpful:
Preparing for PL-200 - Configure Microsoft Dataverse (1 of 6) | Microsoft Learn

I'd also recommend watching Lisa Crosby's video on YouTube:

How to Design and Build a Data Model in Microsoft Dataverse (youtube.com)

If you have any specific questions/issues then please feel free to post them in this forum and the community members will be happy to answer those.

I hope you found this information useful.

Kind regards

Gulshan
Please give it a thumbs up 👍🏻 if you appreciate my efforts.
If my answer helped you resolve your issue then please also mark it as a solution ✅ so that it helps others experiencing the same problem.

Was this reply helpful? Yes No
Fubar 8,338 Super User 2025 Season 2 on at

Like (0)

Report

in addition to the other post,

First Dataverse for Teams is not as fully functioning as normal Dataverse.

When you create a Table (or a Column), the system will take the Display Name you have provided and remove spaces etc and use that as the suffix part of the schema name (there will be a prefix that is defined for the Publisher you are using - if you create a Solution you will be prompted to select a Publisher and you can create one at this time if desired). If the schema name conflicts with an already created table then you will not be able to create the Table, but you can just change the schema name so there is no conflict (the Display Name can be the same as an existing Table) - the schema name is hidden under an expandable Advanced link when creating. Once a Table is created you cannot change its schema name (you can change its Display Name)

When a Table is created the system automatically creates a Primary Key, the schema name of this field will be the schema name of the table with the suffix "id" e.g. for a Table "new_testtable" its primary key will be in "new_testtableid". This column will always hold a system generated GUID for the respective record.

When you create a Lookup column this is actually creating a 1-to-many relationship where the table with the Lookup column is the Many side. The link between the Parent and Child table will be the Primary Key guid of the Parent (always - it cannot be configured differently).

For Lookup columns the value that the user will see is the value in the Primary Name column of the parent table (remembering actual link between the 2 records is the parents guid).

The Primary Column does not have any uniqueness constraint applied to it (whereas the guid is unique).

Generally, speaking the make.powerapps.com is a developer interface. For each table you can configure the existing Views (under the Views link) and create your own (believe at the moment you are just looking at the columns in the Dataverse Table level - not the Views themselves). You then use the Views in either Model Driven App or Canvas App. When you edit or create a View under the Views link you need to Save it and Publish it.

Was this reply helpful? Yes No