ExamFinch.com My Study

Study guide

4.2 Configuring Table Properties

Practice this exam

Microsoft Certified: Intelligent Applications Builder Associate AB-410

Track your progress as you read

Finished sections get a check mark.

1 Introduction

1.1 About the AB-410 Exam 1.2 How to Use This Study Guide

2 Chapter 2: Designing Power Platform Solutions with AI-Enabled Tools

2.1 Analyzing Requirements and Identifying Components 2.2 Evaluating Built-in Agents for Business Solutions 2.3 Recommending Extensibility Options

3 Chapter 3: Environments and ALM Strategy

3.1 Recommending Environment Types 3.2 Solution and Application Lifecycle Management Strategy

4 Chapter 4: Dataverse Tables and Columns

4.1 Creating and Editing Tables in the Data Workspace 4.2 Configuring Table Properties 4.3 Creating and Modifying Columns

5 Chapter 5: Relationships, AI Data Features, and Data Security

5.1 Configuring Table Relationships 5.2 Configuring Prompt Columns and Row Summaries 5.3 Configuring Public Views and Main Forms 5.4 Configuring Dataverse Security

6 Chapter 6: Model-Driven App Forms and Views

6.1 Creating and Configuring Forms for Model-Driven Apps 6.2 Creating and Configuring Views for Model-Driven Apps 6.3 Creating Generative Pages with Natural Language

7 Chapter 7: Composing, Securing, and Visualizing Model-Driven Apps

7.1 Composing a Model-Driven App 7.2 Configuring Access to Model-Driven Apps, Forms, and Views 7.3 Model-Driven App Charts and Dashboards

8 Chapter 8: Creating and Designing Canvas Apps

8.1 Creating a Canvas App Using Data 8.2 Designing for Accessibility, Performance, Responsiveness, and Usability 8.3 Automating Business Processes from Canvas Apps

9 Chapter 9: Canvas App Components, Variables, and Error Handling

9.1 Reusable Components, Named Formulas, and User-Defined Functions 9.2 Managing Variables and Collections 9.3 Implementing Error Handling in Canvas Apps

10 Chapter 10: Testing Canvas Apps and Creating Agents from Apps

10.1 Testing Canvas Apps with Monitor 10.2 Creating a Copilot Studio Agent from a Canvas App

11 Chapter 11: Cloud Flow Triggers, Connectors, and Approvals

11.1 Recommending Cloud Flow Triggers 11.2 Evaluating and Recommending Connectors 11.3 Managing Approvals with Cloud Flows

12 Chapter 12: Cloud Flow Actions, Control, and Troubleshooting

12.1 Configuring Cloud Flow Actions 12.2 Implementing Flow Control with Conditions and Loops 12.3 Testing and Troubleshooting Cloud Flows

13 Chapter 13: Building Prompts in AI Hub

13.1 Building Prompts from Templates or from Blank 13.2 Adding Inputs to a Prompt 13.3 Adding Knowledge to a Prompt

14 Chapter 14: Prompt Settings, Models, and Consuming AI

14.1 Customizing Prompt Settings and Models 14.2 Consuming Prompts in Apps and Cloud Flows 14.3 Consuming AI Models in Apps and Cloud Flows

15 Chapter 15: Business Rules and Business Process Flows

15.1 Configuring Business Rules 15.2 Configuring Business Process Flows

16 Chapter 16: Calculated Columns and Business Logic Strategy

16.1 Calculated, Rollup, and Formula Columns 16.2 Evaluating Use Cases for Business Logic

4.2 Configuring Table Properties

Key Takeaways Explain This Topic AI

Display name, plural display name, and description can be changed after save; the schema name, which carries the publisher prefix, cannot

Track changes enables efficient delta synchronization and is a documented prerequisite for Azure Synapse Link for Dataverse and mobile offline sync

Auditing must be enabled at three levels — environment (Power Platform admin center), table, and column — before a change is recorded

Lookup columns are not enabled for auditing by default when table auditing is turned on; each lookup column must be opted in individually

Duplicate detection requires three things: environment-level enablement, the table's Apply duplicate detection rules option, and published duplicate detection rules

Last updated: July 2026

Creating a table is step one; configuring its properties is where most AB-410 'build data models' questions live. Open any table in make.powerapps.com and select Properties , or set them at creation through New table > Set advanced properties .

  • The Basics: Names and Description
  • Display name — the singular name shown in apps ('Inspection'); changeable later
  • Plural display name — shown in lists and navigation ('Inspections'); changeable later
  • Description — documents the table's purpose for future makers

Schema name — the API name, auto-generated from the display name and prefixed with the solution publisher's customization prefix; immutable after save

The exam hammers this distinction: display names are cosmetic and editable, while the schema name is permanent. Under Advanced options at creation you also pick the Type (standard, activity, virtual, or elastic), Record ownership , a table image used on design surfaces (not in apps — that is what image columns are for), and a Color used in model-driven apps.

Attachments and Activities

The Enable attachments checkbox on the create panel appends notes and files to rows — one checkbox powers the notes timeline, including file attachments, in model-driven apps. Decide on it deliberately when you design the table, because retrofitting notes later means revisiting the table's classic settings. Separately, the Creating a new activity option lets users associate activities — emails, tasks, appointments — with rows, which is what lights up the full activity timeline on a form.

Track Changes

Track changes enables efficient delta synchronization: Dataverse detects what changed since data was last extracted or synced instead of re-reading everything. It is a hard prerequisite for:

  • Azure Synapse Link for Dataverse — the Microsoft Learn table-properties documentation names this explicitly
  • Mobile offline synchronization profiles
  • Performant data-export integrations
  • Exam trap

Track changes is about sync and export performance , not who changed what . If a scenario says 'record who edited a row and when,' that is auditing — choosing track changes there is the classic wrong answer.

Auditing: Three Switches, Three Levels

Dataverse auditing records a change only when it is enabled at all three levels :

  • Organization level — turned on in the Power Platform admin center under the environment's settings
  • Table level — Audit changes to its data in the table's advanced options
  • Column level — Enable auditing on each individual column

When you enable table auditing, many column types — owner, number, text, and choice — are audited by default, but lookup columns are not ; opt those in one by one. Users review changes through the audit history on the row. Classic exam question: 'Table auditing is on, but changes to the Assigned To lookup are never recorded — why?' Because column-level auditing for that lookup is off.

Duplicate Detection

Duplicate detection has its own three-part chain: an administrator enables it for the environment, you select Apply duplicate detection rules on the table, and then duplicate detection rules must be created and published . A rule left unpublished silently does nothing — a favorite distractor.

Offline and Search Availability

Can be taken offline — makes the table's rows available in the Power Apps mobile app while disconnected; combine with track changes and an offline profile that scopes which rows download

Appear in search results — includes rows in in-app search; pair it with environment-level Dataverse search (relevance search) configuration

Canvas Apps, Model-Driven Apps, and Availability

Any Dataverse table — standard or custom — can be connected from a canvas app through the Dataverse connector; there is no per-table switch that hides it from canvas makers (security roles control actual data access). Model-driven apps , by contrast, only surface the tables a maker explicitly adds in the app designer . So when a scenario says 'inspectors must use the table on phones with no connectivity,' the complete answer is three settings working together: Can be taken offline on the table, track changes for efficient sync, and a mobile offline profile that scopes which rows download.

A realistic exam scenario: Fabrikam's field inspectors create Inspection rows on site, snap photos, and sync when back online. The maker enables attachments for photo notes, activities so each inspection can carry follow-up tasks, track changes, and offline availability — one coherent advanced-options conversation.

The Rest of the Advanced Panel

Know these toggles by name for 'which property do you enable' questions:

  • Property Effect
  • Leverage quick create form if available Fast record creation from the nav bar's Create button
  • Enable long term retention Cost-efficient long-term data retention policies
  • Setting up SharePoint document management Store documents in SharePoint from rows

Setting up OneNote integration Take and review OneNote notes from rows (requires SharePoint document management)

  • Can have connections Ad-hoc connections between records
  • Can be added to a queue Route work through queues
  • Can be linked to feedback Ratings and feedback on rows
  • Provide custom help Custom Help URL for the table

One last discipline point: Type and Record ownership choices are constrained after creation, and deleting a table destroys its rows, so treat the advanced panel as an architecture decision, not a settings afterthought.