Data model
SampleData model, service orders
- Customer
- Muster AG, Bern (fictional)
- Environment
- Muster Service (production), managed environment
- As of
- 20 October 2026
- Data sources
- Three SharePoint lists and one Excel file
- 7tables
- 4security roles
- 18’600records migrated
- 4applications on the same base
Summary
Orders, customers, devices and spare parts live today in three SharePoint lists and one Excel file. The model brings them into seven tables; relationships link order, device and customer, so every detail is maintained in one place. The technician app, two flows and the customer question agent work with the same data. Four roles set who sees what: technicians see their own orders, the agent reads orders and devices and only creates questions.
| Table | Content | Source | Write access |
|---|---|---|---|
| Order | Service order with status, date and report | SharePoint list Orders | Dispatch, technicians (own) |
| Customer | Company, site, service contract | SharePoint list Customers | Dispatch |
| Contact | Contact person at the customer | SharePoint list Customers | Dispatch |
| Device | Serial number, model, service interval | SharePoint list Devices | Dispatch, technicians |
| Spare part | Item and stock level | Excel file Spare parts | Warehouse |
| Parts used | Spare parts per order | New | Technicians (own) |
| Question | A customer question and the agent's answer | New | Agent (create only) |
To settle before building
- Licences: the twelve technicians need Power Apps Premium; the order runs through your licensing partner.
- The SharePoint lists stay readable for three months after migration and are then archived.
Next steps
After your approval we build the tables in the test environment and check every role with real accounts before any data is migrated.





