This is an auto-generated question from the MPS Slack community:
I have a strange scenario now. One of my colleague who was working in v.1 (verison 1)_ and created a project.. He opened up the project in v.2..
Meanwhile v.2 had some concept changes underwent for a particular concept C... i.e C had a new child in v.2... Now the user opened the same model in v1 again.. And he gets a error 'Child does not belong to the concept' -- which is quite understandable...
How to programatically fix it??
If I write a quickfix like 'if concept.child is not null -- will this be readable in v1? because the definition of the child itself is not present there isnt it?
Please help. What other impact wil it cause?