Set Your Preferred Solution for the Dataverse MCP
I was working with the Dataverse MCP server yesterday and noticed that when I created new tables through it, they were all getting the default cr*** prefix from the Common Data Services Default Publisher. The MCP doesn’t give you an option to select a publisher or a prefix when creating table customizations — it just uses whatever the environment default is. If you’re like me and want your tables to have a consistent, meaningful prefix tied to your own publisher, there’s a simple fix: set a Preferred Solution . What’s a Preferred Solution? By default, any customizations you make outside the context of a specific solution land in the Common Data Services Default Solution . The publisher on that solution has a randomly assigned prefix, so your tables end up with names like cr8a3_project instead of something clean like contoso_project . When you set a Preferred Solution , any new objects you create — including tables created through the Dataverse MCP — automatically use the publis...
