Publisher in Dataverse: Not Just a Name – It’s Your Solution Identity
In Microsoft Dataverse, a Publisher is a logical container for customizations, especially used when you're creating solutions (managed or unmanaged). It identifies who created or owns a component or solution, and prefixes all schema names (e.g., table names, field names, plugin steps) with a custom prefix defined by the publisher.
Why is a Publisher Important?
Schema Prefixing
- When you create custom components (tables, fields, views, etc.), they get a prefix from the publisher (e.g., abc_ContactType). This avoids naming conflicts across different solutions.
Component Ownership
- It logically associates solution components with the team or organization that built them — useful for managing and tracing customization origins.
Solution Segregation
- Multiple teams can work in the same environment with separate publishers to ensure isolation and clarity between their solutions.
What to Care About During Publisher Design in Dataverse:
1. Use a Unique and Meaningful Prefix
- The customization prefix is added to every schema name (table, column, etc.).
- Choose a short, unique, and identifiable prefix.
Example: For “Contoso Ltd.” use `con_` or `cts_`, not `new_`.
Avoid:
- Generic prefixes like `new_` (default)
- Confusing or reused prefixes
2. Define a Dedicated Publisher per Solution Group or Team
Use different publishers for:
- Product teams
- ISV solutions
- Departments
Helps in traceability, ownership, and modular deployment.
3. Set a Proper Option Value Prefix
- When you create custom option sets (Choice fields), this value prefix ensures uniqueness.
- Default is often `10,000`, but you can customize it (e.g., `20100`).
- Avoid clashes in environments with multiple publishers or ISVs.
4. Avoid Using the Default Publisher
- The default one uses `new_` prefix and is shared across ad hoc customizations.
- Difficult to track, migrate, or maintain later.
- Not suitable for ALM or managed solution strategy.
5. Align Publisher Naming with Governance Policy
Define standards for:
- Prefix format (e.g., company initials)
- Naming conventions (e.g., lowercase, underscore-separated)
- Helps ensure consistency across environments and projects.
6. Use Meaningful Metadata
Useful for documentation, support, and solution cataloging.
7. Plan for Long-Term Use
Publishers are not easily changed after components are created.
Plan wisely because:
- Changing the prefix later requires deleting and recreating components.
- Imported solutions carry their own publisher.
How Publisher Impacts Security in Dataverse (Simplified)
Although a Publisher doesn’t directly manage security, it plays an important supporting role in secure solution design and governance.
Key Impacts:
- Schema Isolation
- Publisher adds a unique prefix (e.g., abc_), helping separate components created by different teams or vendors.
- Ownership & Traceability
- Identifies who created a component (internal team, ISV, etc.), useful for auditing and support.
- Secure Role Assignments
- With unique prefixes, admins can assign security roles to control access to specific custom tables.
- Prevent Conflicts
- Avoids accidental permission overlaps between similar names in different solutions.
- Governance Support
- Metadata (name, email, description) helps enforce change control and compliance.
Developer Tip:
When creating custom solutions:
- Always define your own publisher instead of using the default (new), so your components are cleanly namespace.
- This is especially crucial when exporting Managed Solutions for ISV or multi-environment deployments.
Final Advice:
Think of the Publisher as your solution’s digital identity. Design it intentionally—like you would design namespaces or code modules in enterprise systems.
Summary:
The Publisher in Microsoft Dataverse is more than just a label—it's a foundational element in solution architecture, governance, and security strategy. By assigning a unique customization prefix, publishers ensure clear ownership, schema isolation, and modular deployment.
For architects, it's essential to:
- Define a publisher strategy early, avoiding the default new_ prefix.
- Use publishers to separate internal, external, and team-based solutions.
- Design security roles around publisher-based schema prefixes to avoid accidental access overlaps.
- Ensure traceability with complete metadata and align publishers with ALM pipelines.
A well-planned publisher setup supports clean solution management, secure deployments, and enterprise-scale governance—making it a key architectural decision in any Dataverse implementation.
Published on:
Learn more