Enterprise Administration > Windchill Data Loading > Introduction to Data Loading and the LoadFromFile Framework > Existing Load Methods > More About wt.part.LoadPart.beginCreateWTPart
  
More About wt.part.LoadPart.beginCreateWTPart
The method wt.part.LoadPart.beginCreateWTPart supports versioning. This allows a part to be created at a specified version and iteration. Multiple part versions imply a sequence. For example, subsequent bulk load runs can fill in the gaps, but they do so by attaching to the latest iteration of the previous version. If a newer iteration is added to the previous version, the new version is attached to the new latest iteration.
For example: Load set 1 (E.1, A.1, C.2) results in (A.1, C.2, E.1).
The predecessors of: C.2 is A.1, E.1 is C.2. Load set 2 (B.1, A.2, C.1, C.3) results in (A.1, A.2, B.1, C.1, C.2, C.3, E.1).
The predecessors of: B.1 is A.2, C.1 is B.1, E.1 is C.3.
The iteration history of B.1 shows both A.2 and A.1
The iteration history of C.1 shows B.1, A.2 and A.1
The iteration history of E.1 shows C.3, C.2, C.1, B.1, A.2 and A.1
Any new versions or iterations that are added continue to change the predecessor links to the new latest iteration of the previous version.
* 
Versioning supports gaps in the ordering.
Examples of valid versioning are: (A.1,A.3,B.2,B.5,E.4,E.5)
When you load versions out of sequence and load relationships to those parts, there are a few things that you should understand about ordering your data:
Relationships are copied forward from what is identified as the predecessor to the new version. For example, in an ordered case, you create part 1 A.1 with references or a describe relationship to doc 2. When you revise to get part 1 B.1, the relationships of A.1 are copied to it, so it has the relationship to doc 2 as well.
Relationships are not copied forward if they are created after the new version has already been created. For example, if part 1 A.1 and B.1 are created and then part A.1 has a relationship created to doc 2, part 1 B.1 will not automatically have the relationship to doc 2 copied to it. If you want that relationship to be created, you must explicitly create it.
Relationships from predecessors are not cumulative. (This point further clarifies the first point in this list.) Relationships are only copied from the one identified predecessor, and not the accumulation of predecessors. If you create part 1 B.1 that is related to doc 2 and part 1 A.1 that is related to doc 3, part 1 C.1 inherits only the relationship to doc 2.
Given these basic rules, you can imagine other scenarios. When sequencing the creation of versions or iterations and their relationships, consider your plan very carefully to ensure that you obtain the results that you intend.