As I already asked in ECOHELP-13540, it is still unclear what will happen to Cloud licenses and transactions that don’t have an appEntitlementNumber/Id or hostEntitlementNumber/Id. Will we be able to reference those by their previous addon/hostLicenseId in the license and transaction reports? If not, how should we reference them in our internal CRM system going forward?
Hi @BenRomberg - yes, for the licenses and transactions that don’t have an appEntitlementNumber/Id or hostEntitlementNumber/Id, you will still be able to see the previous addon/hostLicenseId identifiers. So, at any given time, you should have definitely have one of the two.
We will work on updating the API changes documentation as well to reflect this clearly. Thanks!
Thanks for the clarification! If you could please update this post once the documentation has been updated, it would be very much appreciated. I think there’s (at least) 3 cases to consider after the October removal of old license IDs:
How do new licenses/transactions look like (probably without any values in addon/hostLicenseId)
How do migrated licenses/transactions look like (do they still have the old values in addon/hostLicenseId?)
How do non-migrated licenses/transactions look like (probably without any changes)
Also, there are licenses that have a hostEntitlementNumber/Id, but no appEntitlementNumber/Id (see screenshot above). How will they look like? There are also licenses with appEntitlementNumber/Id but without hostEntitlementNumber/Id, but as far as I understood in ECOHELP-13540, this will be fixed soon.