03 · Dealership: manage vehicles, customers and visits

The dealership's problem

Motor Demo organizes test drives through messages. One salesperson confirms an appointment without knowing the vehicle is reserved; another ends a visit without recording the customer's interests.

You will bring together three related records. Brands, customers, and transactions are fictitious. File email addresses use example.com and must not be used as automation recipients.

1. Create the sales model

In a solution named Motor Demo Ventas, create these tables. Make each primary column business-required:

Disponibilidad choices: Disponible, Reservado, Vendido. EstadoVisita choices: Pendiente, Confirmada, Realizada, Cancelada.

In Motor Visitas create two many-to-one relationships: Cliente → Motor Clientes and Vehiculo → Motor Vehiculos. One person and one vehicle can appear in several visits.

For FechaHora use behavior User Local and check that the user's time zone is Madrid. CSV times are expressed in Madrid time.

2. Load operational data

Create the three vehicles and three customers from the CSVs. Import simple fields or enter rows manually. Check that imported choices match the choices you created.

Then create the three visits and select customers and vehicles through lookups. C001 and VH-101 are business references: do not paste them as Dataverse GUIDs.

Review PR-003: it is canceled because VH-103 is reserved. This consistency is prepared in the sample data; you have not yet built a rule automatically preventing appointments on reserved vehicles.

3. Prepare useful forms

In the Vehiculos main form, group reference, make, model, price, and availability. In Visitas include all columns, both lookups, and Resultado.

Add a business rule in Motor Visitas:

1. Condition: EstadoVisita is Realizada.
2. True branch: Resultado is required.
3. False branch: Resultado is not required.
4. Set scope to the main form being used, validate, save, and activate.

Resultado and EstadoVisita must be present on that form. The rule controls this form experience; enforcing the requirement across all integrations needs appropriate server-side validation.

4. Create working views

From the solution, open each table and go to Views. Create a view, add the listed columns, and use Edit filters in the properties pane to define the condition.

Save and publish the views and forms.

5. Assemble the app

In the solution, select New → App → Model-driven app. Name it Motor Demo Comercial. In the designer, add Dataverse table pages for Vehiculos, Clientes, and Visitas.

Include the prepared forms and views, save, and publish the app. Open Play to work through the salesperson's experience.

6. Check the process

Submit the app and evidence for these six checks. A real scheduling system would also need overlap handling, transactional availability, and sales-team permissions; do not attribute those capabilities to views.

Official documentation

• Build a model-driven app.
• Tables and relationships.
• Forms and business rules.
• Create and edit view filters.