Migration form 2020 to 2024 - Positional Constraint to Modelstate

[GermVanDerBij]

We're going to migrate to 2024 from 2020. In this migration, we need our assys to change from PosReps to ModelState.
For this I've made a tool which changes all PosReps to ModelState (with the same name as in PosRep) and deletes all the PosReps. This is working like charme 💪

Now the tricky part; these PosRep assys are used in other assys where we've selected a PosRep state. After running my tool to migrate PosReps to ModelState, I get an error when opening an assembly it is used in: "One or more referenced Positional Representations could not be found. Positional Representation associativity has been removed"

My idee is to cut in just before this message and read out the reference line, where it is mentioned which PosRep needs to be selected, and activate the ModelState with the same name instead. I can already fire a process on opening the main assy and read out some stuff. But all sub assys, already migrated, don't have a PosRep anymore. So I need to know whats inside the main assy......

Anyone knows how to get this reference read out?

Old situation:

New situation:

[bradeneuropeArthur]

I think this process is not needed, because every "Positional Representation" en "View Representation" is automatically translated to Model States....

[GermVanDerBij]

I'm sorry... If that was the case, I would not have posted this thread. I know from testing, the pos reps will remain as they are when opening 2020 files in 2024.

To clairify; becaus when pos reps are used, the weight calculation states N/A. In large assys, recalculating the physical properties takes a lot of time. We need these props in our ERP system.