Table of Contents

    Tables, Columns & Relationships

    Tables, Columns & Relationships in Microsoft Dataverse

    Microsoft Dataverse is the backbone of the Power Platform. It stores and manages business data in a structured and scalable way. The three core building blocks of Dataverse are:

    • Tables
    • Columns
    • Relationships

    1. What is a Table?

    A Table in Dataverse is used to store data. It is similar to a table in a database or a sheet in Excel. Each table represents a specific type of business data.

    Example:

    • Employee Table
    • Customer Table
    • Order Table

    Each table consists of:

    • Rows (Records) → Individual entries (e.g., one employee)
    • Columns (Fields) → Attributes of data (e.g., Name, Age)

    👉 A table is the main container where business data is stored and managed. [1](https://blog.nashtechglobal.com/working-with-data-in-dataverse-a-comprehensive-guide/)


    Types of Tables

    Table Type Description Example
    Standard Table Pre-built by Microsoft Account, Contact
    Custom Table Created by users based on business needs Employee, Leave Request
    Activity Table Tracks interactions and tasks Email, Appointment
    Virtual Table Data from external systems without storing it SQL or SharePoint data

    2. What is a Column?

    A Column defines the type of data stored in a table. It represents a field or property of a record.

    Example (Employee Table):

    • Name
    • Email
    • Joining Date

    Columns control:

    • Data type (Text, Number, Date, etc.)
    • Validation rules
    • How data is displayed

    👉 Columns define what kind of data can be stored in each record. [2](https://sumairanoor.com/2026/05/13/blog-12-pl-900-describe-tables-columns-and-relationships-in-dataverse/)


    Common Column Data Types

    Data Type Description Example
    Text Stores string values Name, Address
    Number Stores numeric values Age, Quantity
    Date Stores date values Joining Date
    Choice Predefined options Status (Active/Inactive)
    Yes/No Boolean values Is Approved
    Lookup Reference to another table Department ID
    Currency Stores money values Salary

    3. What is a Relationship?

    A Relationship defines how data in one table is connected to data in another table.

    👉 Relationships allow you to connect business data and avoid duplication. [3](https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-entity-relationships)

    Example:

    • A Customer can have many Orders
    • An Employee belongs to one Department

    Types of Relationships

    Type Description Example
    One-to-Many (1:N) One record relates to many records One Customer → Many Orders
    Many-to-One (N:1) Many records relate to one record Many Employees → One Department
    Many-to-Many (N:N) Many records relate to many records Students ↔ Courses

    How Relationships Work

    Relationships are created using Lookup Columns. A lookup column connects one table to another and allows users to select related records.

    • Creates connection between tables automatically
    • Helps retrieve related data
    • Ensures data consistency

    👉 Adding a lookup column creates a relationship between tables. [3](https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-entity-relationships)


    Cascade Behavior (Important Concept)

    Relationships can control what happens when data changes:

    • Cascade Delete → Delete related records
    • Restrict → Prevent deletion
    • Cascade Assign → Assign related records automatically

    👉 These rules help maintain data integrity and business logic. [4](https://bing.com/search?q=Dataverse+tables+columns+relationships+explanation)


    4. Real-Life Example

    Let’s understand using a simple business scenario:

    • Table: Customer
    • Table: Order

    Relationship:

    • One Customer → Many Orders

    Columns:

    • Customer Table → Name, Email
    • Order Table → Order Date, Amount, Customer (Lookup)

    👉 Here, the Customer column in Order is a Lookup that creates the relationship.


    5. Key Benefits

    • Better data organization
    • Reduces duplicate data
    • Enables automation & workflows
    • Supports reporting & insights
    • Improves data integrity

    Conclusion

    Tables, Columns, and Relationships form the foundation of Microsoft Dataverse. Understanding these concepts is essential for building scalable Power Apps, Power Automate flows, and enterprise applications.

    👉 If designed properly, they enable powerful data-driven solutions, automation, and AI integration.