Microsoft Dynamics 365 | Integration, Dataverse...

How to work with solutions with different publishers?

(0) Share

Report

Posted on by EmmaCRMadmin

Hi!

We have been working with a consultancy firm (lets call them XXX) to help us with our Dynamics Customer engagement. We are working with a production environment where all the solutiuons are managed. And one Development environment where the solutions created by XXX are unmanaged. When they make changes they do it in DEV environment and then import it to the production. The solution has the publisher XXX.

Now the project is over and we would like to be able to do changes by our own. We have created a new unmanaged soultion in development environment with another publisher YYY, to be able to separate our changes.

But our problem is that when we use an existing entity that was created in a solution with publisher XXX, we can not import our new solution to the production environment because we have another publisher YYY on that solution. Then we need to add all the required components.

I have an idea of creating 2 solutions with publisher YYY.

Solution A - Add all required components to this solution.

Solution B - Use this solution to make changes and to be able to quickly import it to production environment.

Our aim is to be able to have one solution that I can make quick changes, which goes fast to import to the production environment. And as I understood I need to have the components in a solution with the same Publisher.

Have anyone had a similar issue and how did you solve it? and what do you think of my suggestion above?

Best Regards,

Emma

Thank you for your time!

All responses (6)

Answers (0)

dian74 2,475 Most Valuable Professional on at

Like (0)

Report

RE: How to work with solutions with different publishers?

Hi Emma,

Using the same publisher but editing the prefix when you start a new solution. That way all the new components will have the different prefix. You can access the publisher by opening the solution and clicking on the publisher or by navigating to Settings>Customization>Publishers.
EmmaCRMadmin on at

Like (0)

Report

RE: How to work with solutions with different publishers?

How do you mean? changing the publisher and prefix every time I do an export? how and where can I do this?

/Emma
dian74 2,475 Most Valuable Professional on at

Like (0)

Report

RE: How to work with solutions with different publishers?

How about editing the Publisher record and changing the prefix? That way you would be able to tell which changes were made by your organization?
EmmaCRMadmin on at

Like (0)

Report

RE: How to work with solutions with different publishers?

Hi Dian!

I tried that before and It didn't work because it required components in my solution. And yes my source instance is a copy of my target instance.

I reported this issue to microsoft and they told me that it has to do with different publishers on my solutions, so the system will think that the required components are not in my system (even if they are).

/Emma
EmmaCRMadmin on at

Like (0)

Report

RE: How to work with solutions with different publishers?

Hi Dian!

I tried that before and It didn't work because it required components in my solution. And yes my source instance is a copy of my target instance.

I reported this issue to microsoft and they told me that it has to do with different publishers on my solutions, so the system will think that the required components are not in my system (even if they are).

/Emma
Suggested answer

dian74 2,475 Most Valuable Professional on at

Like (0)

Report

RE: How to work with solutions with different publishers?

Hi Emma,

What I would recommend is create a new solution with publisher YYY and only put the items in there that were changed/added. You don't need to add the required components, as you only want to move your changes. (I assume your source instance is a copy of your target instance, hence no need to put the required components in as they are already in the target instance.)

Please mark this answer as verified if this was helpful.