DevPortal - API Version dropdown mismatch between API in two different environments about api-management-developer-portal

[malincrist]

Hello @christophmantsch3302 ,

1. It looks to be related to this issue #2287 (which was fixed and will be shipped with the next release).
   This would mean that you have more than 100 APIs in environment 2 and the request to GET the versions is not returning the selected API with version "Original".
   Could you please check if this is the case? If not, could you please share the instance name to [email protected] to investigate it further?
2. yes, the string "Original" is the default, in case there is no Version identifier (as you can see here: https://github.com/Azure/api-management-developer-portal/blob/7d46bedb0ba96c35f22c4e99491e0119379cc96e/src/components/apis/details-of-api/ko/runtime/api-details.ts#L86C4-L86C74)
3. It is not mandatory as versioning an API is not mandatory. You can create an API and decide to version it only later. And when you create a first version over an existing API, the API up until that point is considered "Original", and doesn't have any version identifier initially (as we cannot predict the versioning scheme that customers will choose)
4. If you navigate to the "Original" API in Azure portal, you can edit the version identifier to match your portal versioning scheme.

Also, when you create a new API, you have the option to create it already versioned, meaning that the initial version will be whatever you specify in the Version Identifier field (instead of the "Original"):