Requiring Multiple Deploys in order to deploy current solution to CRM

(0) Share

Report

Posted on by Community Member

Recently I had deployed a managed solution to a CRM organization. I also hit the publish all customizations button. As I tested the solution I realize that the although the deploy succeeded with no errors that it certainly didn't have the newly developed code I had recently written. Upon redeployment with the same zip file the changes I had made in the code appeared and everything was working normally. Another note was that the first time I deployed the solution I was using IE and the second time I was using chrome. I was wondering is there a tool I could use to check if the currently deployed solution has the correct code. I was thinking that maybe by using the plugin registration tool and trying to debug Visual Studio would tell me whether the code is the same or not. Is there another way? I was using CRM On Premise 2016.

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Community Member on at

Like (0)

Report

RE: Requiring Multiple Deploys in order to deploy current solution to CRM

yeah it was the first time it happened to me. Took a long time to figure out that just redeploying the solution would have fixed the problem

Was this reply helpful? Yes No
ScottDurow 21 on at

Like (0)

Report

RE: Requiring Multiple Deploys in order to deploy current solution to CRM

I've noticed that due to the serverside caching of plugin and workflow activity assemblies - it can sometime take a while before all currently running processes have released the previous version and the new verison is picked up.

I've never seen a plugin not actually get deployed. I always use the PackageDeployment tool in the SDK - since this automatically creates a holding solution for you when upgrading a solution version.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: Requiring Multiple Deploys in order to deploy current solution to CRM

Thanks for your help. Unfortunately I do have build numbers on the managed solution. After it was deployed I checked and it seemed that my javascript changes went through just not the plugin code itself. Unfortunately my client won't let me enable the trace log or wants to smoke test. They also aren't satisfied with the answer of just redeploying if the situation appears again

Was this reply helpful? Yes No
Suggested answer

M I Mostafa 4,257 on at

Like (0)

Report

RE: Requiring Multiple Deploys in order to deploy current solution to CRM

If you have build numbers on the managed solution, you should be able to check which one is imported. You can also smoke test your code as soon as you deploy it. Unfortunately I'm not aware of any to do debugging using plugin registration tool.

If you don't want to smoke test the functionality (or you can't), then you could try pushing build number through the Plugin trace log to check if your code has been updated. This way you can see which version of the plugin is being executed.

Hope this helps!

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: Requiring Multiple Deploys in order to deploy current solution to CRM

Sadly this was not the case. I had refreshed my cache and it was happening on multiple computers accessing the organization

Was this reply helpful? Yes No
Suggested answer

M I Mostafa 4,257 on at

Like (0)

Report

RE: Requiring Multiple Deploys in order to deploy current solution to CRM

It could be that the code was deployed but you needed to refresh the browser cache. If you already have a record open for example, its script could well be still in the browser cache and that's why you didn't feel that the code was deployed. Other than that, if you import a managed solution without errors, then its code must have been deployed.

If you found my response helpful, please mark "yes" to confirm it helped you.

Was this reply helpful? Yes No