---
title: "#solution-management articles | Hashnode"
description: "Explore the latest #solution-management articles, tutorials, and guides on Hashnode."
url: "https://hashnode.com/tag/solution-management"
---

Tag

# #solution-management

0 posts · 0 followers

[SapotaCorp](https://hashnode.com/@sapotacorpvn) · [May 24](https://hashnode.com/posts/dataverse-naming-convention-publisher-prefix-and-schema-discipline/6a127db92018432660411fa1)

### [Dataverse naming convention: publisher prefix and schema discipline](https://sapotacorpvn.hashnode.dev/dataverse-naming-convention-publisher-prefix-and-schema-discipline?utm_source=hashnode&utm_medium=feed)

The schema name you pick for a Dataverse column is a decision you live with for the life of the solution. Here is the convention we enforce on every project, including the publisher prefix rule that new teams wish they had set earlier.

5 min read · [sapotacorpvn.hashnode.dev](https://sapotacorpvn.hashnode.dev/dataverse-naming-convention-publisher-prefix-and-schema-discipline?utm_source=hashnode&utm_medium=feed)

[SapotaCorp](https://hashnode.com/@sapotacorpvn) · [May 24](https://hashnode.com/posts/publisher-prefix-in-power-platform-the-decision-you-cant-undo/6a127d8c201843266040d686)

### [Publisher prefix in Power Platform: the decision you can't undo](https://sapotacorpvn.hashnode.dev/publisher-prefix-in-power-platform-the-decision-you-cant-undo?utm_source=hashnode&utm_medium=feed)

Your publisher prefix ends up in every schema name, every Web API URL, every managed solution file. Changing it after a system is live is a multi-week migration. Here is how we pick one on day zero and the two exceptions we make.

6 min read · [sapotacorpvn.hashnode.dev](https://sapotacorpvn.hashnode.dev/publisher-prefix-in-power-platform-the-decision-you-cant-undo?utm_source=hashnode&utm_medium=feed)
