First Dataverse Table: Column Types, Relationships, Roles

You create a first table in Microsoft Dataverse via the Tables area in the Power Apps portal, define at least one column there via the respective data type, and, if needed, link the table to another table via a relationship. Whether Dataverse is even necessary for this or a simple SharePoint list is enough depends mainly on how many linked tables and how strict security roles your process needs. As of: August 2026.

How do I create a column correctly?

Before you create a new column, check according to Microsoft Learn whether an existing column doesn't already serve the same purpose, because Dataverse comes with many system columns out of the box. New columns can be created via the form editor of a model-driven app using the New table column command, by importing a solution that already contains the column definition, or via Power Query when populating a table with data. A special type of column is the lookup column: according to Microsoft Learn, it is created automatically when you create a one-to-many relationship on a table, and it then references records of the linked table.

What types of relationships exist between tables?

According to the Table relationships documentation, Dataverse fundamentally distinguishes between two relationship types: one-to-many relationships, in which many records of one table refer to exactly one record of another table, and many-to-many relationships, in which records of both tables can be linked to each other any number of times. Technically, a one-to-many relationship arises because the linked table receives a lookup column pointing to the parent table. For each relationship, you can additionally specify what should happen to the linked records when a parent record is deleted, assigned, shared, or merged, for example whether they are automatically deleted along with it, assigned to the new owner, or left unchanged.

When is a SharePoint list enough instead of a Dataverse table?

A SharePoint list is usually enough as long as you only need a single, flat list without complex relationships and without fine-grained security roles. As soon as multiple tables need to work together with one-to-many or many-to-many relationships, you want to define deletion rules for linked records, or different security roles are needed for different user groups, Dataverse is the more robust foundation, because according to Microsoft Learn these very features are a core part of the data model and cannot be added to a SharePoint list after the fact.

What role do security roles play for a new table?

Security roles determine who is allowed to create, read, modify, delete, or assign records of a table to others, and they apply regardless of which app or flow is used to access the table. For relationship actions such as assigning or sharing, security roles additionally interact with the cascading rules of the relationship: if a parent record is assigned to a new owner and the relationship is configured as a so-called parental relationship, this assignment can automatically be passed on to linked records. If you are planning a first Dataverse table for a specific process and also want to clarify the question of roles, we support this as part of our automation consulting.

Frequently Asked Questions About the First Dataverse Table

Do I need to create a separate security role for each table?

Not necessarily. Security roles can be defined jointly for multiple tables and reused; what matters is that the permissions match the actual tasks of the respective user group. For a first, simple table, an existing standard role is often enough; differentiated custom roles only become worthwhile as complexity grows.

Can I remove a lookup column afterwards?

A lookup column is tied to the underlying one-to-many relationship, so removing it effectively affects the entire relationship, not just the column. Before deleting it, you should therefore check which forms, views, or flows already use the relationship.

What happens to linked records when I delete a parent record?

That depends on the deletion rule configured for the relationship. Microsoft Learn names three options for this: automatically delete all linked records along with it, remove the reference to the deleted record, or prevent the deletion of the parent record as long as linked records still exist.

Do I really need an entire Power Platform environment with a Dataverse database for a single, simple table?

Yes, according to Microsoft Learn this is one of the minimum requirements for Dataverse tables: you need a Power Platform environment with a Dataverse database set up before you can even create a first table. For very simple, single lists without relationships, it is therefore often worth checking whether a SharePoint list can fulfill the same purpose more economically.