Episode Details

(00:00:00) The Data Verse Dilemma
(00:00:38) The Low-Code Fallacy
(00:01:56) The Model as Story
(00:04:45) Data Verse as a Semantics Engine
(00:08:02) Leadership's Role in Data Modeling
(00:12:59) The Importance of Consistent Modeling
(00:15:48) Relationships: The Backbone of Data Modeling
(00:21:00) Deployment and Governance in Data Verse
(00:32:35) The AI Imperative
(00:32:51) AI's Dependence on Clear Data Models

This episode was inspired by Bülent Altinsoy Microsoft MVP, who delivered a four-hour Dataverse deep-dive workshop at M365Con—staying firmly in the mechanics: tables, relationships, security, and solutions. The parts teams usually rush through to get an app on screen. This conversation sits above that. Most Power Platform failures aren’t about low-code limitations. They happen because teams treat data as a temporary inconvenience—something to fix after the demo. Dataverse isn’t a magic database. It’s Microsoft offering a way to model reality with enough discipline that automation and AI can survive contact with production. This episode isn’t about features.
It’s about why the model underneath your apps becomes strategy, whether you intended it or not. 1. Why “Low-Code Data” Keeps Failing in Production Low-code doesn’t fail because makers lack governance knowledge. It fails because the first data model is often a lie everyone agrees to—temporarily—to ship faster. Speed-first delivery creates meaning debt:

• Overloaded tables
• Generic columns like Status, Type, or Other
• Lookups added for dropdowns, not for shared understanding

Everything works—until real production begins: scale, audits, integrations, edge cases, and time. Scaling doesn’t just multiply transactions; it multiplies contradictions. When meaning isn’t encoded, every downstream consumer invents it. That’s how “it works” quietly turns into “it’s unpredictable.” 2. Dataverse Is Not a Database — It’s a Business Semantics Engine Databases store facts. Dataverse stores facts plus meaning: relationships, ownership, security, metadata, and behavior that travel across apps, automation, and AI. Treating Dataverse like storage strips out its value. When intent isn’t compiled into structure, every app, flow, report, and agent interprets reality differently. Dataverse behaves more like a compiler than a table store.
You write intent in structure—and Dataverse enforces consistent behavior everywhere. Weak models don’t break immediately.
They scale mistakes quietly. 3. Why Data Modeling Is a Leadership Topic Data models outlive apps. Screens change. Flows get rewritten. But the model becomes sediment—accumulated assumptions the organization builds on, even when nobody owns them. Governance doesn’t emerge from policy decks. It emerges from structure:

• Ownership
• Security scopes
• Relationships
• Constraints
• Metadata

If leaders don’t define the core nouns of the business, Dataverse will faithfully scale organizational ambiguity instead. Good models scale clarity. Bad models scale meetings. 4. From Tables to Business Concepts A table is not storage. It’s a declaration. Creating a table says: this thing exists, has a lifecycle, has rules, and matters over time. Hiding concepts inside text fields or choice values says the opposite. Screen-driven modeling always collapses.
UI is volatile. Nouns are durable. Tables are nouns.
Processes are verbs. When teams store process steps as columns, every process change becomes a breaking schema change. Modeling nouns cleanly—and processes as related entities—lets systems evolve without rewriting history. 5. Relationships: How the Organization Actually Works Relationships aren’t navigation links. They encode policy. One-to-many defines structure.
Many-to-many defines meaning when the relationship itself matters. Relationship behavior—parental, referential, rest