Assembly mapping strategy details

OnePart proposes 5 strategies to resolve the relationships between parent and children files received by a Files connector. The original path is the part’s path location when saved in the CAD software. The file path is the location where OnePart found the part at import time. The following table details the elements for the example Skateboard.CATProduct assembly scenario. In many cases, certain elements are not provided so OnePart cannot find the children.

Item

Description

Path

Provided?

parent.filename

Assembly name

Skateboard.CATProduct

Always 

parent.originalFolder

Where the assembly was last saved

C:\users\bc\Desktop\

Sometimes

parent.currentFolder

Where OnePart accesses it

D:\OnePart\data

Always

parent.child0.filename

Child name. Applies for every child 0-n.

Board.CATPart

Always

parent.child0.originalFolder

Where last saved

C:\users\bc\Desktop\stuff

Sometimes

parent.child0.currentFolder

Where OnePart accesses it

D:\OnePart\data

Sometimes

parent.child0.relativeFolder

=originalFolder+(child0.currentFolder-parent.currentFolder)

stuff

Processed

child.filename

Name of potential child

Board.CATPart

Always

child.originalFolder

Where the child was last saved

C:\users\bc\Desktop\

Sometimes
child.currentFolder Where OnePart accesses it D:\OnePart\data Sometimes

Which elements are used when we apply the different strategies? The table below details their behavior.

Item

Description

Path

S0

S1*

S2*

S3*

S4*

parent.filename

Assembly name

Skateboard.CATProduct

 

 

 

 

 

parent.originalFolder

Where the assembly was last saved

C:\users\bc\Desktop\

 

 

 

 

parent.currentFolder

Where OnePart accesses it

D:\OnePart\data

 

 

 

 

parent.child0.filename

Child name. Applies for every child 0-n.

Board.CATPart

parent.child0.originalFolder

Where last saved

C:\users\bc\Desktop\stuff

 

 

 

 

parent.child0.currentFolder

Where OnePart accesses it

D:\OnePart\data

 

 

 

 

parent.child0.relativeFolder

=originalFolder+(child0.currentFolder-parent.currentFolder)

stuff

 

 

 

 

child.filename

Name of potential child

Board.CATPart

child.originalFolder

Where the child was last saved

C:\users\bc\Desktop\

 

 

child.currentFolder

Where OnePart accesses it

D:\OnePart\data

 

 

 

 

Note: * This table details the general behavior for the strategies. However, in some cases, OnePart is able to find the children because it looks in both referenced paths: parent.child0.originalFolder and parent.child0.currentFolder This applies to all strategies except for S0.

Therefore, when Strategy 0 looks for child0 in the C:\users\bc\Desktop\stuff originalFolder AND for the Board.CATPart filename there is no match since the children are not located in stuff.

However, Strategy 1 looks for child0 in the C:\users\bc\Desktop\ originalFolder AND for the Board.CATPart filename therefore there is one match.