Hello Irene,
going your way with duplicate IDs with your xem is not the best solution IMHO. And especially not with repository. You already found your workarounds and I can tell you that you can automate your manual work using VBS script (checkout, remove old extension, attach new extension, checkin with creating baseline) for all your models in one batch.
But more appropriate way from my point of view is to create new extension with new IDs. You are saying, that some of your extended attributes don`t migrate from A to B automatically. I don`t know details, but if something like this happens, you can always create one-time-transform function (in any of those two extensions) which will be triggered at the model level and will help with proper migration of values from A to B. And this can be automated via VBS too (checkout, attach new extension, trigger function for migrating ext.attr. values from A to B, remove old extension, checkin without creating baseline).
Generally, I don`t recommend duplicating models or any resource files with the same IDs. Sooner or later, it will stab you in the back. I`ve seen it many times. For example during upgrading the models from PD 15.3 to PD 16.x.
You can share your specific scenarios that don`t migrate properly and perhaps we can find out something. But most probably it won`t change my opinion on duplicating resource files with the same IDs.
If you need more help, don`t hesitate to ask for it, I`ve been solving this kind of issues for last 14 years.
Regards,
Ondrej Divis
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.