You’re offline. This is a read only version of the page.
20
We have a CRM solution for our non-profit that was developed for us by an ISV. This is deployed in our production and UAT environments as an unmanaged solution. We wish to achieve the following:
1. We want to be able to make minor customisations ourselves (form changes etc) in a separate solution, without "polluting" the ISV solution.
2. We want these to be able to be backed out if we find issues with them - although this should be unusual as we will test in UAT first, of course.
What we have attempted:
a. Created a new organisation "Dev" containing the original ISV solution as unmanaged, and a new solution for our changes "Internal", also unmanaged.
b. We have imported into "Internal" only those entities that we want to change.
c. When our releases are ready we want to export these as a managed solution and push them to UAT, but because the "ISV" solution in UAT is unmanaged, this means our changes will take effect in both "ISV" and "Internal" within that organisation, so if we find an issue and want to back out the latest release of "Internal" it won't be possible without manually undoing each change.
d. We therefore tried to create a new "ManagedUAT" organisation in which we mean to import both the "ISV" and "Internal" solutions - as managed this time. This is where we are having our problem. (Once we can get this sorted it is our intention to create a ManagedProduction organisation which also contains the managed versions of both solutions.
So, end game:
Dev containing unmanaged solutions for ISV and Internal
UAT and Production (managed) containing managed versions of both solutions.
Ability to promote changes from dev to UAT as a version update of the managed Internal solution, and back it out if errors are found. Likewise for promotes from Dev to Prod if UAT testing is OK.
Our problem is when we import the anaged ISV solution into the new, empty Managed UAT organisation. The import runs for a while, but fails on importing the Connection Role "Former Employee" with the error "The publisher of the solution that is being imported does not match the publisher of the solution that installed this component.". We have not customised Former Employee and don't make use of it. Other Connection Roles earlier in the solution import are imported successfully, according to the import log.
We have tried creating a blank solution in production containing just the publisher information and importing this into the ManagedUAT environment before we try to import the managed version of ISV, but no luck.
Our support organisation has suggested creating a new blank solution in Production and importing only customised entities and other elements into that prior to exporting it to UAT, but this seems to invalidate the approach of keeping the ISV solution as pristine as possible. It will also take extensive testing to make sure everything is still working as desired.
We could delete the Former Employee role and export again, and will try this, but wonder if anyone has any smarter suggestions?
Thanks
*This post is locked for comments
I have the same question (0)
Hello SeanK,
In reading your post the best way to avoid the error is to bring in your ISV to Dev and set Dev how you would like it. Then create a new solution and include those changes into that new solution and deploy just that solution to UAT. When a publisher makes a change to a field that carries over and that is why you are encountering the error that you are. By including that in a new solution and setting the publisher that should then attach the new publisher to the field.
I would also like to stress with managed solutions when you uninstall them for custom fields they will also remove any data in the database that is posted to the fields. You can still rollback versions of managed solutions, but an uninstall would potentially remove data. The only exception to this is out of the box fields with changes.
I hope this helps to resolve the issue you are seeing. If not please log a support case with us so we can work with you to help resolve this issue.
Share
Report
All responses (
Answers (
