claude

ppbp-dataverse-metadata

Dataverse schema design best practices: table, column and global Choice conventions, model review, and dev-only, confirm-first change principles — whatever tool applies the changes.

1 on GitHubby Théophile Chin-ninv3.0.0MITupdated 11 days ago
/

Plugin ppbp-dataverse-metadata from marketplace powerplatform-bestpractices in tchinnin/powerplatform-bestpractices-skills. Commands read from the repo's manifest — 10 days ago.

What it installs

Skills (5)

  • ppbp-dv-columns

    Dataverse column design best practices. Use when the user is creating or reviewing columns — naming rules (Display Name, Schema Name, no project code prefix), type-specific suffix and prefix conventions (Lookup Id, Choice Code, Boolean Is/Has), column type selection, local option sets vs. global Cho

  • ppbp-dv-global-choices

    Dataverse global Choice best practices. Use when the user is creating or reviewing global Choices (OptionSets) — naming rules (Display Name ending in " Choice", schema name with _choice_ segment), translations, option values, and binding choice columns to a global Choice. Also use when a global Choi

  • ppbp-dv-metadata-overview

    Dataverse schema design domain overview. Use when starting any schema task — tables, columns, global Choices, lookups — or when asking where the data model lives. Provides the repository layout (dataverse/model for review docs), the core naming rule (language split between Display Name and Schema Na

  • ppbp-dv-metadata-review

    Read-only quality review of a Dataverse data model against the ppbp schema conventions, with a report ranked by severity (error / best practice / suggestion). Accepts any input: dataverse/model docs, schema-as-code files of any tool, an exported solution's customizations.xml, a metadata dump, or pas

  • ppbp-dv-tables

    Dataverse table design best practices. Use when the user is creating or reviewing tables — naming rules (Display Name singular, Schema Name with publisher prefix, project code in shared environments), table ownership (User Owned vs. Organization Owned), primary name column configuration, AutoNumber,

View source on GitHub

More from tchinnin/powerplatform-bestpractices-skills

All 7 plugins →

Power Apps Code Apps best practices: tooling, UI/logic architecture, component reuse and async states, server-side Dataverse data access through TanStack Query, centralised error handling, app review, and UX/UI theming with the shared uxui/ design system.

9 skills

1

Dataverse plug-in best practices: project scaffolding and build, step and Custom API design, and dev-only, confirm-first registration principles — whatever tool registers them.

4 skills

1

ppbp-alm

claude

Power Platform ALM best practices: solution design, naming, versioning, segmentation, and deployment pipelines.

3 skills

1

Dataverse data manipulation best practices: script naming and lifecycle, idempotency, initial data import, bulk operations, dependency ordering, and environment segmentation.

3 skills

1

Power Platform project orientation: canonical repository layout, skill routing, README requirements, and agent instruction files.

3 skills

1

Power Apps Generative Pages best practices: repository organisation, page naming and splitting, and Fluent v9 branding with the shared uxui/ design system.

2 skills

1

Maintain ppbp-dataverse-metadata?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins7 plugins