Book a Demo

Author Topic: Use of version= in cloning relationship  (Read 3381 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Use of version= in cloning relationship
« on: December 13, 2016, 12:23:55 pm »
So we cloned some elements firstly via creating a clone diagram with the original elements then cloning within that diagram.

We have «trace» relationships back to the clonees from the cloned.  these relationships have the VOF=1; clause, as mentioned in Using SQL to filter out elements superseded by the Clone Element Feature, with the version set as at the time of the cloning.  Now that we understand better how it works, we want to change the version.  I presume we can do that via SQL. 

Are there any other implications to changing the version in the row?  There doesn't (on a quick check) seem to be anyhting attached to t-object to say it is a clone.

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Use of version= in cloning relationship
« Reply #1 on: December 14, 2016, 05:42:44 pm »
BUMP!

Do I need to submit a formal support request?

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!