Updating Dataverse Table Schema in Power Apps Solutions
Short answer
For the Services table, select the table and enable Change Tracking in its metadata. For the Equipment table, select the table and add the four new columns to its schema. Both actions require modifying the existing table components directly.
Question
A company is updating a Power Apps solution that contains two tables named Services and Equipment.
The company is creating a new solution to update the current solution for the following requirements:
• The Services table must be updated to include change tracking.
• The Equipment table must be updated to include four new columns.
• The solution must update only the components that need to be added or changed.
You need to create the solution.
Which table option should you use? To answer, move the appropriate options to the correct tables. Each option may be used once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Key Takeaways
Tests the ability to differentiate between record updates and schema modifications, requiring selection of the table entity to alter its metadata or columns.
Learn how to update existing Dataverse tables in Power Apps by enabling change tracking for the Services table and adding new columns to the Equipment table using component-specific updates.
Common mistake: Learners often try to create new tables or import data instead of modifying the existing table schema, missing the requirement to update specific components.
Expert Analysis
The core challenge in this question is understanding how Power Apps solution components handle schema changes, specifically regarding version control and incremental updates. The requirement to 'update only the components that need to be added or changed' dictates a targeted approach rather than a full redeployment.
For the Services table, the requirement is to include change tracking. In the context of Microsoft Dataverse (the data platform for Power Apps), enabling change tracking is a metadata-level setting. Therefore, you must select the option that allows modification of the table's definition or metadata. This typically involves selecting the table entity itself and ensuring the 'Change Tracking' property is checked within the table settings or by including the table metadata in the update package.
For the Equipment table, the requirement is to add four new columns. Adding columns is also a schema change. You cannot simply update records; you must alter the table structure. Thus, the correct action is to select the table component and modify its columns.
The key insight here is that both scenarios involve modifying the structure (schema) of existing tables, not just adding new records or creating new tables from scratch. The solution must target the specific table entities and apply the necessary schema modifications (enabling change tracking for one, adding columns for the other). The phrase 'update only the components that need to be added or changed' implies using the 'Selected Components' or similar granular update mechanism in the Power Platform admin center or maker portal, rather than updating the entire solution if possible, though in practice, schema changes often require republishing the affected table component.
A common mistake is trying to use 'Import Data' or 'Create New Table' instead of modifying the existing table schema. Another error is assuming that column additions don't require explicit table selection because they are part of the table definition; however, in solution management, each modified component must be explicitly selected for inclusion in the update.
The operational consequence of getting this wrong would be either failing to enable change tracking (leading to inability to audit service changes) or failing to add the columns (leading to incomplete equipment data models). The adjacent decision point is whether to update the whole solution or just specific components; the prompt’s constraint favors specific component updates.
Official Reference
- https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/working-with-data-modify-table-schema
- https://learn.microsoft.com/en-us/power-platform/admin/change-tracking-overview
- https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-update-delete-dataverse-tables
These links open the official vendor documentation in a new tab.
Exam Strategy
When asked to modify existing table structures (adding columns, changing properties like change tracking), always select the existing table entity as the component to update. Do not create new tables unless explicitly required. Focus on the 'Properties' or 'Schema' tab of the table component in your solution to apply these changes incrementally.
Frequently Asked Questions
Why can't I just add columns without selecting the table?
What does 'change tracking' mean in Dataverse?
How do I ensure only changed components are updated?
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
exam_upskill 👍 11. Include table metadata 2. Selected Components
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.