13 Sep 2024 07:59 PM
When updating an EF2 extension monitoring configuration, the following error appears
when the new extension version has different configuration properties in an endpoint.
This didn't happen in EF1.
It would probably be a good decision if applied only to mandatory properties, because for those where nullable=="true", they could have initially a null value.
This will have some implications in extensions upgrade, as there seems to be no way to update unless a completely new monitoring configuration is made...
Is this something that an extension can control in some way?
Solved! Go to Solution.
14 Sep 2024 10:13 AM
It depends on what changed between the different versions. If the only change was the addition of some nullable=true fields, that error should not show up. If it was any other change, such as the removal of a field or the addition of an array around the configuration and such, you’d indeed have to recreate the monitoring configurations.