Some solution changes not reflecting after managed solution import

(0) Share

Report

Posted on by Walespop

520

Hi All,

Please I need help here. I have a dev org with a managed solution of form section title change and also a change to form ribbon custom button display criteria. These changes are not showing after installing the exported managed solution to another organisation.

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (1)

Suggested answer

Community Member on at

Like (0)

Report

Hi Walespop

My name is Andres Guzman, I'm glad to help you

I recommend you to check the "Customization.xml" file included in the zip solution file.

There, when you export the solution, you can check if the change is included in the package.

If not, you need to verify what happen. Maybe you forgot to publish your changes.

If the change is there, and after import your solution and publish it, you can export again a default solution in your environment and validate if this same description with the change exist there.

Let me know if you need additional info

Regards,

Was this reply helpful? Yes No
Verified answer

Royal King 27,686 on at

Like (1)

Report

This seems to be known issue and i come across this issue multiple times. To fix this issue create a new section and move all the fields to this new section and delete the old section.If you export and import this solution then you will see all the changes.

Was this reply helpful? Yes No
Mithilesh Kumar 10,047 on at

Like (0)

Report

Hi Walespop,

How can you export a Managed Solution. Can you please elaborate on your query.

Thanks

Was this reply helpful? Yes No
Walespop 520 on at

Like (0)

Report

Thanks for your help Andres. I have tried that procedure above and I can confirm that the exported solution's customization.xml have the changes but the default solution's customization.xml of the destination org after import does not.

Was this reply helpful? Yes No
Suggested answer

ScottDurow 21 on at

Like (3)

Report

This is usually because there have been some unmanaged customization made to the managed layer. Once this has been done, then importing the managed customizations will not update those changes unless the 'overwrite' option is selected when importing the managed solution.

Unfortunately, the exception to this is form customisations. Once you have changed the form, then re-importing the managed solution will never over write those changes.

Hope this helps,

Scott

Was this reply helpful? Yes No
Suggested answer

Walespop 520 on at

Like (0)

Report

Thanks for the response Scott. I have been able to resolve the issue.

Was this reply helpful? Yes No
Suggested answer

Walespop 520 on at

Like (0)

Report

Thanks Chitra. That works for one which is form section related

Was this reply helpful? Yes No
CRMYogi 505 on at

Like (0)

Report

How did you fix it Walespop?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Scott,

I am facing same issue below is overview of description can you please help me on this.

I have one dynamics crm organization and in that we have installed one UnManaged solution and that contains Javascript on form and onload event on quote form after that i am going to install other managed package that also contains javascript with different name on quote form and onload event and it successfully installed with out any error but my javascipt changes on quote form and onload event are not applied.

Thanks,

Vaibhav

Was this reply helpful? Yes No
Suggested answer

Andras Fordos 112 on at

Like (0)

Report

Good Afternoon Vaibhav,

.

The short answer is: they will never be applied like this, as you have local (unmanaged) changes in your target instance to the form. Related MSFT documentation: msdn.microsoft.com/.../gg334576.aspx

.

However, you can manually apply the required changes to the form in the target instance, as this is now an environmental issue...

.

To properly solve it for future projects (or instances):

- if you can, install your first solution too as managed next time, not just the second

- stop making unmanaged customization (installing unmanaged solution does this too) to the same element in two (or more) different instances

- if the current target instance is your "last" instance (eg production), definitely stop installing unmanaged solutions or making local (unmanaged) customizations

.

Best regards

Was this reply helpful? Yes No