Domain 1 of 3 · Chapter 2 of 2

Build Dataverse data models

Unlock the complete study guide.

Bundled into the existing Building Intelligent Applications premium course — no separate purchase.

14-day refund guarantee on one-time purchases and your first subscription charge.

Included in this chapter:

  • Model business data as related tables
  • Create and edit tables in the data workspace
  • Table types and ownership
  • Table properties and capabilities
  • Alternate keys
  • Duplicate detection rules
  • Column basics: names, data types and settings
  • Text and number data types
  • Choice, date, lookup and file data types
  • One-to-many and many-to-many relationships
  • Relationship behavior: actions, behaviors and presets
  • Inherited-access cleanup
  • Prompt columns: setup, inputs and testing
  • How prompt columns run and report status
  • Row summaries
  • Public and system views
  • Configure Dataverse search through the Quick Find view
  • Main forms
  • Security roles, privileges and access levels
  • Business units
  • Teams
  • Hierarchy security
  • Column-level security
  • Moving security to another environment
  • Dataverse tables, columns, relationships, views and security by requirement

Dataverse table types: Standard vs Activity vs Virtual vs Elastic

CriterionStandardActivityVirtualElastic
Where the rows liveDataverseDataverseAn external source, read at runtimeDataverse, powered by Azure Cosmos DB
Choose it whenMost business dataCalendar-style work with a subject and time dimensions (calls, appointments)Records must remain in the external systemVery large datasets (tens of millions of rows) at high throughput
Limits and contrastsOwnership is fixed at creation, as for every table typeOwned only by a user or team; primary name column is always SubjectImporting a file instead would create a separate stored copyNot the default: Standard is the type for most tables

Decision tree

Rows must stay inan external system?Virtual tableYesNoTens of millionsof rows?Elastic tableYesNoAn out-of-box tablelike Account fits?Customize theout-of-box tableYesNoCalendar-style workwith subject, time?Activity tableYesNoNew tableof Standard type

Cheat sheet

  • The data workspace can generate and refine tables from natural language
  • Removing an existing table from the workspace does not delete its data
  • The data workspace supports only a subset of relationship configurations
  • Some column types require a designer outside the data workspace
  • External-data table creation previews only part of the dataset before saving
  • The data workspace supports an existing parent with a new child
  • Standard tables can be extended when their customizable property allows it
  • A table's display name can change while its schema name cannot
  • Activity tables provide a shared structure for time-based work
  • Virtual tables expose external data dynamically rather than importing it
  • Elastic tables suit very large high-throughput datasets
  • Change tracking and auditing solve different data-history requirements
  • Enable Attachments lets a table's records carry notes and files
  • Enabling activities makes the table available to the Regarding lookup
  • Table ownership must be chosen before the table is created
  • Alternate keys identify records through unique business values
  • A duplicate detection rule must be published before it is usable
  • Base and matching record types define which records a duplicate rule compares
  • Duplicate matching can compare whole values or a specified end of a value
  • Case-sensitive duplicate rules distinguish letter casing
  • Inactive matching records can be excluded from duplicate detection
  • Ignore Blank Values prevents missing data from counting as an equal match
  • Dependencies can block deletion of a custom table
  • A configured Quick Find view does not by itself enroll a table in global search
  • Can be taken offline enables a table to participate in offline data access
  • Both participating tables must allow connections
  • Table-level SharePoint document management participates in organization-level integration
  • Can have a contact email enables sending email using a table's stored address
  • Choose a column's schema name and data type before saving it
  • Use Multiline Text for content beyond the Text Area limit
  • Choice stores one selection while Choices allows multiple selections
  • Global choices centralize option sets reused by multiple columns
  • Decimal numbers preserve specified values while floating point stores approximations
  • Currency columns support transaction currencies and base-currency values
  • Date and time behavior determines whether users see timezone conversion
  • Customer columns can reference either an account or a contact
  • Autonumber generates formatted text when a row is created
  • Searchable controls discovery in Advanced Find and view customization
  • Business-required columns do not impose SystemRequired enforcement on API writes
  • A File column stores binary content associated with a row
  • File uploads and deletions take effect before a model-driven form is saved
  • Required-field validation does not enforce File columns
  • Choose the Autonumber format to match the required reference structure
  • The Autonumber seed sets the starting numeric value
  • Status Reason options provide configurable detail within a Status
  • Whole number is the column type for integral values
  • Whole number minimum and maximum settings define the permitted range
  • Duration formats a Whole number as an interval measured in minutes
  • Email format validates an email address and presents a mailto link
  • URL format validates an address and renders a link to open it
  • Rich text supports formatted multiline content
  • A lookup on the child table implements a one-to-many relationship
  • Many-to-many relationships use an intersect table for reciprocal associations
  • Remove Link preserves child records when the parent is deleted
  • Restrict prevents parent deletion while related rows exist
  • Cascade All deletes dependent rows with the parent
  • Cascade User Owned limits cascading to children owned by the same user
  • Cascade Active selects active children while Cascade None leaves children unchanged
  • Formal table relationships and informal connections serve different modeling needs
  • Association-specific data requires an explicit junction table
  • Referential presets keep parent operations from propagating to child records
  • The Parental preset makes related records follow parent actions
  • Custom relationship behavior permits different policies for different actions
  • Share cascading controls access propagation when a parent is shared
  • Unshare cascading controls propagation when parent sharing is withdrawn
  • Reparent cascading addresses access effects when a child changes parent
  • Self-referential N:N relationships need labels that distinguish their two roles
  • Deleting a native N:N relationship deletes its stored associations
  • An existing cascading parent can block a new cascading relationship
  • A custom parent table cannot cascade actions to a system child table
  • Changing access cascading to Cascade None requires cleanup of earlier inherited access
  • Inherited-access cleanup preserves directly granted access
  • Separate related business entities to avoid repeated and sparse data
  • Prompt columns persist AI-generated enrichment in the table
  • Prompt columns ignore unsupported input column types
  • A table can have up to five prompt columns
  • Asynchronous prompt definitions require a single record-ID text input
  • Prompt-column tests can target a specific record before saving
  • Prompt columns execute on record creation or changes to referenced inputs
  • Updated prompt columns generate values asynchronously
  • Prompt-column filters determine whether an eligible record receives AI processing
  • Prompt-column Status and Details distinguish failures from skipped execution
  • Existing rows can be backfilled through an enabled asynchronous bulk job
  • Imported prompt-column bulk jobs require review by default
  • Prompt-column execution requires both platform enablement and the column execution setting
  • A configured row summary applies to all main forms and views for its table
  • Row summaries require environment enablement and existing table data
  • Row-summary prompts define the included columns and presentation
  • LanguageCode makes row summaries follow the user's language preference
  • Some Dynamics 365 tables use their own summary features instead
  • Show row summary hides custom summaries without deleting the prompt
  • Row summaries move through solutions as selected AI Skill Config records
  • Row summaries are not a supported engine for arithmetic or date decisions
  • A table view defines displayed columns, row filtering, and default sorting
  • Quick Find determines which columns are searched in Quick Find and lookup searches
  • The Lookup view defines the record-selection presentation for a lookup
  • The Associated view controls the default listing of related records
  • Advanced Find supplies default columns for new views without a template
  • Special-purpose system views cannot be deleted or deactivated
  • Set and publish the table's default public view explicitly
  • Quick Find find columns define the fields searched by Dataverse global search
  • Quick Find view columns define the displayed global-search result fields
  • Quick Find filter conditions constrain Dataverse global-search results
  • Main forms are the primary table assets for record interaction
  • Tabs provide primary grouping and sections organize content inside each tab
  • The form designer separates table fields from structural components
  • A main form's title is user-visible while its description explains it to makers
  • Displaying a record image requires both a primary image column and the form setting
  • Save and publish main-form changes to make them available to users
  • A main form can be reused across device sizes
  • Dataverse combines privileges from all assigned security roles
  • Each table privilege has its own access level
  • Business Unit access excludes subordinate units unless Parent: Child access is granted
  • Organization-owned tables expose organization-wide or no access rather than owner-level scopes
  • Associating records requires the correct Append and Append To privileges
  • Sharing grants access while assignment changes ownership
  • Environment Maker access does not automatically grant Dataverse data access
  • Table customization authority is separate from business-record access
  • Solutions can transport security roles and column security profiles
  • Configure the security structure and assignments in each destination environment
  • Business units form a hierarchy beneath a single root
  • The root business unit cannot be deleted
  • Owner teams hold records and roles while access teams receive shared access
  • A team can include users from multiple business units
  • Microsoft Entra group teams derive membership from the directory group
  • Hierarchy security extends record access but still requires table Read privileges
  • Manager hierarchy follows reporting lines while position hierarchy follows assigned positions
  • Hierarchy access is broader for direct reports than for indirect reports
  • Dataverse maintains a business unit's default team membership automatically
  • Column security requires enabling the column and granting profile permissions
  • Column security separates reading, creating, and updating a value
  • System administrators bypass column-level security
  • Primary name values are unsuitable for sensitive information
  • Sensitive prompt inputs do not automatically secure generated output
  • Not every Dataverse column supports column-level security
  • Secure the contributing columns to protect composite address data

Unlock with Premium — includes all practice exams and the complete study guide.

References

  1. https://learn.microsoft.com/en-us/troubleshoot/microsoft-365-apps/access/database-normalization-description
  2. https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-entity-relationships
  3. https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/ab-410
  4. https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-entities
  5. https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-field-solution-explorer
  6. https://learn.microsoft.com/en-us/power-apps/maker/data-platform/types-of-fields
  7. https://learn.microsoft.com/en-us/power-apps/maker/data-platform/types-of-entities
  8. https://learn.microsoft.com/en-us/power-platform/admin/wp-security-cds
  9. https://learn.microsoft.com/en-us/power-platform/admin/manage-dataverse-auditing
  10. https://learn.microsoft.com/en-us/power-apps/mobile/setup-mobile-offline
  11. https://learn.microsoft.com/en-us/power-apps/maker/data-platform/define-alternate-keys-reference-records
  12. https://learn.microsoft.com/en-us/power-platform/admin/set-up-duplicate-detection-rules-keep-data-clean
  13. https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-field-portal
  14. https://learn.microsoft.com/en-us/power-apps/user/advanced-find
  15. https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/rich-text-editor-control
  16. https://learn.microsoft.com/en-us/dotnet/api/microsoft.xrm.sdk.metadata.memoformatname
  17. https://learn.microsoft.com/en-us/power-apps/maker/data-platform/autonumber-fields
  18. https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-platform-entity-lookup
  19. https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-nn-relationships
  20. https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-nn-relationships-portal
  21. https://learn.microsoft.com/en-us/power-apps/maker/data-platform/prompt-column
  22. https://learn.microsoft.com/en-us/power-apps/maker/data-platform/configure-form-row-summary
  23. https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/create-edit-views
  24. https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/specify-default-views
  25. https://learn.microsoft.com/en-us/power-platform/admin/configure-relevance-search-organization
  26. https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/create-and-edit-forms
  27. https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/design-considerations-main-forms
  28. https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/add-move-or-delete-tabs-on-form
  29. https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/add-move-or-delete-fields-on-form
  30. https://learn.microsoft.com/en-us/power-platform/admin/security-roles-privileges
  31. https://learn.microsoft.com/en-us/power-platform/admin/database-security
  32. https://learn.microsoft.com/en-us/power-apps/developer/data-platform/businessunit-entity
  33. https://learn.microsoft.com/en-us/power-platform/admin/manage-teams
  34. https://learn.microsoft.com/en-us/power-platform/admin/about-team-templates
  35. https://learn.microsoft.com/en-us/power-platform/admin/hierarchy-security
  36. https://learn.microsoft.com/en-us/power-platform/admin/field-level-security
  37. https://learn.microsoft.com/en-us/power-platform/alm/overview-alm