Microsoft Dataverse Tables and Columns

Standard tables are pre-built and contain common data for various business applications. They provide a starting point for data management.

These tables are created by developers to store specific data based on their application requirements. They offer flexibility and customizability beyond standard tables.

Allows renaming a standard table for improved readability or relevance to the application using it.

Each table contains columns that define the specific type of data they hold.

The data type of a column dictates what kind of information can be stored in the column (e.g., text, numbers, dates).

This table type is used to manage tasks that create calendar entries, such as appointments, phone calls, and emails.

The organization owns the data, and permissions are managed at the organization level. This means everyone in the organization can access the information.

Access to the table's data is controlled at the user or team level, with specific permissions granted to individuals or groups.

Standard columns are predefined columns that exist in every table within a Microsoft Dataverse instance.

Custom columns allow developers to create fields specific to their application's needs that are not part of the standard set.

A one-to-many relationship exists when one record in a table can relate to multiple records in another table, like an invoice linking to multiple ordered products.

A many-to-one relationship exists when multiple records in one table can link to a single record in another table, like multiple invoices belonging to one customer.

A many-to-many relationship exists when multiple records in one table can relate to multiple records in another table, like a list of skills and a list of employees, where each employee can have multiple skills and each skill can be held by multiple employees.

Lookup fields store a reference to another record in Dataverse, allowing you to establish and manage relationships between tables.

Pre-built tables within Dataverse that provide essential data structures for common business entities like contacts, accounts, and appointments.

The Account standard table is used for storing information about businesses, such as company name, address, and website.

The Contact standard table is used for storing information about individuals associated with a business, such as name, email address, and phone number.

Business rules are automated logic that applies to data within a table, preventing conflicts and enforcing business constraints.

Conditions specify the circumstances that must be met for a business rule to be triggered.

Actions are the procedures that are executed when a business rule's conditions are met.

Real-time workflows automate processes that are triggered by specific events, such as a record being created or updated.

Actions within a workflow are specific steps that are executed, such as sending an email or updating a record.

Automated processes triggered by events without requiring user interaction. They manage tasks like creating, updating, and assigning rows in tables, and can initiate other workflows.

Features in Power Apps that allow developers to gather data from multiple sources, transform it, and store it in either the Microsoft Dataverse or Azure Data Lake Storage. Developers can schedule data refresh for the dataflows to ensure their data is up-to-date.

Packages of customizations made to the Microsoft Dataverse. They include modifications to existing solutions and components created with Power Platform tools, such as canvas apps, model-driven apps, Power Automate flows, custom connectors, and Dataverse tables.

A type of solution intended for development environments where modifications to the solution are made. Developers can export unmanaged solutions as either managed or unmanaged.

A type of solution intended for non-development environments like test and production. They are read-only and cannot be directly edited by developers.

Rules that simplify data entry for users and verify the accuracy of the data they provide. Developers can define rules to set values for fields, clear existing values, and validate data entered into fields.

A feature in Power Apps that allows developers to create custom messages with multiple steps, expanding the native capabilities of the Power Platform beyond basic actions like Create, Update, and Delete. They allow for more complex operations like Approve, Escalate, or Convert.

Conditions used in business rules to specify when actions should be executed. These conditions can be simple or complex and include Boolean AND/OR operators, allowing for multiple rules and combinations.

Actions that are executed when specific conditions defined in a business rule are met. These actions can involve setting values for fields, clearing existing values, validating entered data, and showing or hiding fields.

Similar to real-time workflows, actions in Power Apps consist of stages and steps with conditions and actions. They allow for more complex actions beyond the basic Create, Update, and Delete.