I've been trying unsuccessfully to replicate functionality of a multilevel BOM report using a custom itemtype before implementing any changes in production tables. I have the following structures:
xBOM - a table with BOM items
xBOM Child Rel - a RelationshipType listing next lower assembly parts for BOM items, source: xBOM, Related: xParts
xParts - a table with standard parts
Getting a Report to cycle thru the BOM isn't working, only receiving one level down from any given BOM item.
Attempt 1:
<Item type="xBOM" action="GetItemRepeatConfig" select="part" id="{@id}">
<Relationships>
<Item type="xBOM_Child_Rel" select="related_id,qty"/>
<Item type="xParts" select="related_id,part,title" repeatProp="related_id" repeatTimes="6"/>
</Relationships>
</Item>
Attempt 2:
<Item type="xBOM" action="get" id="{@id}" select="part">
<Relationships>
<Item type="xBOM_Child_Rel" action="get" select="related_id,qty">
<related_id>
<Item type="xParts" action="get" select="part,title" order_by="part">
<Relationships>
<Item type="xBOM_Child_Rel" action="get" select="related_id,qty">
<related_id>
<Item type="xParts" action="get" select="part,title" order_by="part">
</Item>
</related_id>
</Item>
</Relationships>
</Item>
</related_id>
</Item>
</Relationships>
</Item>
Suggestions?
Hello,
The standard Multilevel BOM Report is built off of the Part->Part BOM->Part relationship structure. Because Parts can be linked directly to other Parts, you can end up with a potentially infinite number of levels to the relationship structure.
The data structure described doesn't seem suited to the same kind of Multi-level report since it appears to only allow for one level of relationships from xBOM to xParts. Could you clarify if there's a missing link from xParts to xBOM that would allow this structure to continue for multiple levels?
Chris
Christopher Gillis
Aras Labs Software Engineer
Hello,
The standard Multilevel BOM Report is built off of the Part->Part BOM->Part relationship structure. Because Parts can be linked directly to other Parts, you can end up with a potentially infinite number of levels to the relationship structure.
The data structure described doesn't seem suited to the same kind of Multi-level report since it appears to only allow for one level of relationships from xBOM to xParts. Could you clarify if there's a missing link from xParts to xBOM that would allow this structure to continue for multiple levels?
Chris
Christopher Gillis
Aras Labs Software Engineer