For the Objects API and ZGW APIs there can be inconsistencies that must be caught and rectified before the upgrade to 4.0 is done. This check script will thus need to be backported to 3.5 as part of our migration tools.
It's possible that file upload components end up with a different catalogue in the registration options than what's configured in a registration backend - or even the same file component may be configured with different backends that use different catalogues. We cannot guarantee that this will all still resolve.
The migration can copy the descriptions, and set up the catalogues in the backend options accordingly, but cannot solve merge conflicts. That's a manual action.
For the Objects API and ZGW APIs there can be inconsistencies that must be caught and rectified before the upgrade to 4.0 is done. This check script will thus need to be backported to 3.5 as part of our migration tools.
It's possible that file upload components end up with a different catalogue in the registration options than what's configured in a registration backend - or even the same file component may be configured with different backends that use different catalogues. We cannot guarantee that this will all still resolve.
The migration can copy the descriptions, and set up the catalogues in the backend options accordingly, but cannot solve merge conflicts. That's a manual action.