One request, related records
The fictional Tern Willow team records repairs for several sites. A request has its own ID and a SiteId. A separate Sites table stores the site’s name. Two sites can have similar names, so a copied display label cannot replace the relationship key.
A canvas app gives the maker control over the screen and its formulas. A model-driven app uses Dataverse tables and components such as forms and views. In this original case, a repair intake screen can be canvas work while an operations review needs reliable navigation through related records. The business requirements decide the choice.
The local course models selected table, view and rule behavior. It doesn’t create an actual Dataverse environment or implement every model-driven designer feature.
SharePoint-style and Dataverse-style data
Define a number column for hours, text for the description and a supported relationship representation for SiteId. Check a missing site and an invalid numeric value. A form that displays a site name can still save the wrong related ID.
SharePoint has connector-specific type mappings and delegation rules. Dataverse has its own table and relationship model. Moving a formula between the two requires a fresh check of supported column types, query operations and effective access. Neither source becomes a live connection in the browser practice.
App and flow responsibilities
The app gathers a repair request and validates the values it sends. A flow can perform a separate automation task and return a result. A click proves only that the app attempted the call; the response and downstream evidence establish what finished.
The course’s supplied flow response is local. It doesn’t send a message or run a production Power Automate flow. Use the separate Power Automate course for that tool’s modeled flow work. Continue with forms, delegation or the Power Apps course.