Hi there,
Have others who have moved from 16.1 to 16.5 noticed this behaviour ?
We recently upgraded our repository from 16.1 to 16.5.
I merged a local project development data model to a production model that I check-out in memory(i.e I do not save it to a file) from repository. I then check-in this in memory production model back to repository and PD Repository thinks it is a brand new model and asks for folder name to save it in.
I noticed that in the merge differences results screen it has started to show difference in some Extended meta model signature. Wondering if this is causing it to think it is a brand new model.
As I cannot save a new copy of my production model and loose all the version history on the existing one. I save this in memory model to a file locally. I then once again check-out the production data model from repository in memory and now merge my recently saved prod model file locally into this in-memory model. The merge goes fine and now when I check-in this in memory model back to repository, it correctly recognizes it as existing in repository.
Why this difference in behaviour when doing the same task ?
I have noticed that it does this even on a model that I just check-out from repository and save back so that it does the one time conversion/version upgrade from 16.1 to 16.5.
And I have noticed that it does this even with a production data model that I merged two Dev models one after another.
Something has gone wrong with 16.5 upgrade. We did have repository upgrade error issues and our upgrade failed and messed up the repository. SAP support had to get involved and our repository was out of service for around 3 weeks before the upgrade was attempted again and went through.