Support Ticket Lab: The Data Model
Create the solution boundary, the Support Ticket and Ticket Update tables, and the lookup relationship everything else in this lab stands on.
Field guide for builders and architects
A field guide for architects, governance teams, COE builders, and advanced makers. Longform, opinionated, and written from production environments — not from the marketing site.
Explore articlesLatest articles
View all articles →Create the solution boundary, the Support Ticket and Ticket Update tables, and the lookup relationship everything else in this lab stands on.
A five-module hands-on lab: model a support ticket solution in Dataverse and learn why each component exists, not just how to click it.
Not a product comparison. A category question: does the requirement need relational integrity, roles and audit, or a place for a team to keep a list?
How to read a requirement, name the signals it contains, and pick the component that owns the center of gravity, with the condition that would change your mind.
Create the solution boundary, the Support Ticket and Ticket Update tables, and the lookup relationship everything else in this lab stands on.
A five-module hands-on lab: model a support ticket solution in Dataverse and learn why each component exists, not just how to click it.
Scripted videos rendered from the article library. Coming after the first articles ship.
The layering model and the one rule that keeps upgrades boring.