Solution patch not working

(0) Share

Report

Posted on by gujjar

Hi,

I was wondering if someone can shed some light on this issue.

I recently made some changes to an existing solution in DEV. Therefore I cloned a patch and added the modified components as I have to move it to UAT where the parent solution already exist.
I then exported the patch in the relevant environment (UAT). But for some reason, I cannot see the new changes at all?

Is there a wait time or am I doing something wrong? The parent solution got locked and I can see that notification, which mean the patch got imported correctly in the environment. So I am confused now why it is not working?

Thanks

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Verified answer

Ram Prakash Duraisamy 5,593 Super User 2025 Season 2 on at

Like (0)

Report

Hello @gujjar,

Hope its Unmanaged Solution. If yes, try clicking PUBLISH ALL CUSTOMIZATION to get the solutions updated.

Please mark as Answer if it is helpful and provide Kudos

Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Blog : https://microsoftcrmtechie.blogspot.com

Was this reply helpful? Yes No
Devikumari Krishna 988 Super User 2024 Season 1 on at

Like (0)

Report

Hi Gujjar,

Make sure you published the changes after importing in UAT, incase it is an unmanaged solution.
Clear all your browser cache / open in incognito mode to see if it a issue at the browser level.
If the issue continues try to publish from a different browser once. we faced this issue once when we tried publishing from Chrome browser and it was not getting reflected.

Please mark my answer as verified if you find this useful.

My Blog: Dynamics 365 Key Topics – https://d365topicsbydk.com/
My Youtube Channel : https://www.youtube.com/channel/UCxSIryP2ah2VpEFr-Z72t
Regards
Devi

Was this reply helpful? Yes No
EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report

Hi @gujjar,

Why are you exporting a patch from UAT? The patch should be exported from the dev environment and only imported into UAT and then the same patch into Prod. Also note that cloning a solution is an operation used to merge a patch(es) into your main solution. Cloning is performed in the dev environment not in UAT or prod. Once cloned, you can then export an updated version of your main solution to upstream environments.

Patch is a mechanism to create a smaller solution from an existing solution generally for hotfix purposes. You can import a patch into upstream environments (e.g. UAT and Prod). While patches are present in dev, you cannot make further changes to the main solution while patches exists.
Hope this helps!

Was this reply helpful? Yes No
Prakash4691 1,332 on at

Like (0)

Report

@gujjar,
In UAT are you importing as managed solution? If yes, then check whether any unmanaged layer customization might have done in that component directly in UAT.

If that is the case, then you need to clone the solution, export as managed from DEV. While importing to UAT, upgrade and overwrite the customization for the new changes. Overwrite customization option will only available in classic not from power apps import solution wizard.

If it answers your question, kindly give kudo and accept it as solution.

Regards,
Prakash

Was this reply helpful? Yes No