A sales operations team is composing a model-driven app in the app designer and wants to add components to their Dataverse tables. Which components can they add to tables when building a model-driven app? (Select 3 answers)
- AForms, used to enter and edit records Correct
- BViews, used to list and filter records Correct
- CDashboards, used to surface charts and data Correct
- DConnectors, used to reach external data sources
- EPower Fx formulas, used to set control properties
Why A is correct: Correct. Forms, used to enter and edit records is one of the keyed answers. The grounding describes model-driven app design as adding components such as forms, views, charts, and dashboards to tables using the app designer, so forms, views, and dashboards are all valid table components.
Why B is correct: Correct. Views, used to list and filter records is one of the keyed answers. The grounding describes model-driven app design as adding components such as forms, views, charts, and dashboards to tables using the app designer, so forms, views, and dashboards are all valid table components.
Why C is correct: Correct. Dashboards, used to surface charts and data is one of the keyed answers. The grounding describes model-driven app design as adding components such as forms, views, charts, and dashboards to tables using the app designer, so forms, views, and dashboards are all valid table components.
Why D is wrong: Connectors are how canvas apps reach more than 200 data sources; model-driven apps use the Dataverse data model and do not add connectors as table components.
Why E is wrong: Power Fx expressions drive control properties in canvas apps; model-driven design is no-code and component-focused, so formulas are not the components added to tables.