Unanswered

After updating D365 plugin package( .nupkg), it is not getting reflected in system

(4) Share

Report

Posted on by Ayan28

I am updating .nupkg plugin package, using plugin registration tool. But after updating it the latest code is not get reflected properly. Sometimes even the older version is coming back automatically. Only one developer is working on it so there no chance of overwrite by other developer. Creating the package by rebuilding the solution or clean and then Build.
I found out older code is coming back or new code not updated properly by using traces.

Not sure what is wrong, can anyone please help? If there any best practice to follow while working with .nupkg plugin package, please let me know.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (0)

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

Like (1)

Report

Hi @Ayan28

Try Unregistering Assembly and install it again create a step and try using it.

Please mark as Answer if it is helpful and provide Kudos

Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Follow me on Twitter : @rampprakashd
Blog : https://microsoftcrmtechie.blogspot.com

Was this reply helpful? Yes No
Ayan28 16 on at

Like (1)

Report

Thanks for your response.
I did it and it worked. But I can't unregister and register the whole package multiple times. I need to re-register all the steps and images as well.
In development phase I am changing the code and deploying it multiple times.
Not a practical solution.

Was this reply helpful? Yes No
PV-23082238-0 3 on at

Like (1)

Report
Unfortunately, this is not an answer but I'm hoping to add some color to this post. I am facing the same issue in one of the environments I am working in now. I found the following in the documentation.

After Microsoft Dataverse instantiates the plug-in class, the platform caches that plug-in instance for performance reasons. Dataverse manages the length of time that a plug-in instance is held in cache. Certain operations, such as changing a plug-in's registration properties, trigger a notification to the platform to refresh the cache. In these scenarios, the plug-in is reinitialized.

Because the platform caches plug-in class instances, the constructor isn't called for every invocation of plug-in execution. For this reason, IPlugin implementations shouldn't depend on the timing of operations in the constructor apart from obtaining static configuration data.

Here's what I've tried so far:

Full rebuild with deleting of the old nupkg files

Updating the file version of the nupkg

Updating the registration details (async to sync)

Adding another step to the plugin

Adding a dummy plugin to the package assembly

Publish All (I was desperate)

The most success I've seen is changing the Execution Mode. It ran the correct version after the change but reverted back when I changed back to the old version again.

Was this reply helpful? Yes No
Suggested answer

CU30012133-0 2 on at

Like (0)

Report

Just putting this out there but have you tried updating the assembly version and recompiling.

Was this reply helpful? Yes No