Error: PluginPackage version cannot be updated

[steverasmussen]

Just started getting this error today when trying to update a plugin package:

PluginPackage version cannot be updated. Exiting Package Version 2024.5.1, New Package Version 2024.5.14 (Fault Detail is equal to Exception details:
ErrorCode: 0x80040265
Message: PluginPackage version cannot be updated. Exiting Package Version 2024.5.1, New Package Version 2024.5.14
TimeStamp: 2024-05-14T17:00:40.9651485Z

Even though it is only the 'Minor' version that is updating... it's throwing this error.  This does not make any sense to me.  Anyone else having issues?  This was working just fine previously.

[steve-rasmussen]

Looks like the documentation has been updated:

I was having issues before with changes to the plugin not getting picked up if the version was not changed.  I wonder if this behavior has changed as well.  Need to do some testing now.

[JakobNilsson]

I'm had the same issue updating a .nupkg file in Plugin Registration Tool. I suspect it comes from someone else in the project uploading a package file with an earlier version than mine. What I did to solve it was to edit the FileVersion value in the Plugins.csproj file to match the exiting package version from my error message. I hardly think this is best practise, but it solved it for me. Another reason might be a larger rollback causing a disconnect in version numbers.

[Ayan28]

Whenever I update the .nupkg file in Plugin Registration Tool, it is not getting updated properly. Sometimes the old code is coming back as well. Is there any best practice I need to follow?

[srasmussen · Accepted solution]

What I have found is this:  They must have pushed an update that disallows updating the version of the NuGet package.  Not sure why... versioning the package in the past caused the changes to be picked up by D365.  Oh well, here is what has worked for me:

1) Leave the package version as 1.0.0.0

2) Add code to automatically update both the version and file version of the assembly. You can add the following to your CS proj file:

<GeneratePackageOnBuild>True</GeneratePackageOnBuild>
<PackageVersion>1.0.0.0</PackageVersion>
<GenerateAssemblyInfo>true</GenerateAssemblyInfo>
<Deterministic>false</Deterministic>
<Version>$([System.DateTime]::Now.ToString("yyyy.M.d.HHmm"))</Version>
<FileVersion>$([System.DateTime]::Now.ToString("yyyy.M.d.HHmm"))</FileVersion>

3) You MUST do either a 'Clean' and then 'Build', or a 'Rebuild' of the project.  This will clear out the old NuGet package and generate a new one.

4) Upload the package.

I use XrmToolkit (Dynamics 365 / Dynamics CRM Toolkit - XrmToolkit.com) to do this which performs the clean and build and uploads the package to D365 all in a single click from Visual Studio. Full disclosure - I am the author of XrmToolkit 🙂

[Ayan28]

@srasmussen As you suggested I have updated the project file like this

But unfortunately still facing the same issue. Code is not getting updated in Dynamics after multiple deployment using Plugin registration tool.
Tried everything, Clean & Build or Rebuild.

[PabloRoldan]

Yes, MS updated PR tool so now you can not push higher version or lower of the package but this can be bypassed by using CLI

00000000-0000-0000-0000-000000000000 = pluginId

00000000-0000-0000-0000-000000000001  = environment id

---
pac plugin push -id 00000000-0000-0000-0000-000000000000 -c debug -env 00000000-0000-0000-0000-000000000001   run that command in using CLI in where your .csproj is

[imranakram]

Thanks for the explanation. For the life of me, I just can't understand how this makes any sense. What is Microsoft thinking here, can anyone explain

[Pchan3]

We are seeing the same behaviour. Plugins do not get updated if they are the same version number. We have to delete the plugin and upload it again. recreating all steps.