Perfect Table Checklist

It's so easy to build a Dataverse table now with AI, unfortunately it also means it's so easy to miss critical configurations that are so hard to undo later.

1️⃣ Naming matters - It's more than just vanity

Avoid adding “s” to table names.

𝘞𝘩𝘺 𝘉𝘪𝘨 𝘩𝘦𝘢𝘥𝘢𝘤𝘩𝘦 𝘭𝘢𝘵𝘦𝘳? -> Dataverse automatically pluralizes it and now you're testing Web API calls and cant remember if its new_cars, new_cares, new_carss?

2️⃣ Many-to-many - It saves clicks but causes earthquates

Native N:N relationships are convenient but limited.

𝘞𝘩𝘺 𝘉𝘪𝘨 𝘩𝘦𝘢𝘥𝘢𝘤𝘩𝘦 𝘭𝘢𝘵𝘦𝘳? -> If you need extra columns, better control, or flexibility, you get none of that.

3️⃣ Cascade deletes = No mess to clean

“Referential” is often safer than “Cascade All.”

𝘞𝘩𝘺 𝘉𝘪𝘨 𝘩𝘦𝘢𝘥𝘢𝘤𝘩𝘦 𝘭𝘢𝘵𝘦𝘳? ->You have a bunch of "orphaned" records laying around.

4️⃣ One-to-one is usually a modeling smell

Two tables with circular lookups often signal they should be merged—or rethought.

𝘞𝘩𝘺 𝘉𝘪𝘨 𝘩𝘦𝘢𝘥𝘢𝘤𝘩𝘦 𝘭𝘢𝘵𝘦𝘳? ->You thought you're clever by doing a 1 x 1 by having two tables have looks ups point to themselves. Cool, but how are you enforcing them to stay that way?

Click the download link above to get the full PDF.