Stephan,
While it might work if your POTA location has already been updated in the database, I would not trust it. The POTA org is not just changing program prefixes, I’ve found numeric database “unique key” values for some locations are being changed. The complexity of tracking every user and every database (SOTA Associations/Regions/Peaks and POTA Programs/Locations/Parks) with every timestamp across all the different services is not simple on the back-end. While it might work, and probably would work, why risk a busted activation? I don’t have time to debug all the implications at the moment, as I am focused on having my code automatically recognize when POTA is changing what used to be immutable keys.
73 de AB6D - Brian