"Version Comparable" value get disappeared on migrated APIs when restoring revisions.

[DilsiChandrasena]

Description

We found an issue on migrated apis, where the "Version Comparable" value of the apis getting lost when restoring revision via publisher portal. After that we can't update and save that specific API anymore.

Steps to Reproduce

• Start APIM 2.6 (updated) and use MySQL as the DB
• Create an API and publish.
• Execute the latest migration client to migrate from APIM 2.6 to 4.1
• Start the APIM 4.1 after the migration and check the APIs and the DB. You should be able to see the "version comparable" value in the DB (AM_API) table and on the carbon console as well.
• Login to publisher portal and create a new revision (revision 2) and deploy it.
• Restore again the initial revision (Revision 1)
• After that, check the API information via carbon console and you will be able to see that the "version comparable" field is empty. Since it is a required filed, from that point onward it is not allowing us to update the API via publisher and giving a "GovernanceException" in the error logs.
  

We can update registry value directly through the carbon console by providing the version comparable value from the AM_API table and then after publisher is allowing us to update and save the API. This issue only occurs on migrated APIs and does not affect any APIs which are created after the migration.

Affected Component

Analytics

Version

4.1.0

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

No response

Suggested Labels

No response