I want to create a table that can link and record important part information (e.g. Serial Number) across three BOM hierarchies. According to this, it is possible to link part information in two BOM hierarchies, but not in three BOM hierarchies.
Is there any way to link BOM information from 3 BOM hierarchies and display them in one table?
As an example, here is an image of linking the BOM information of three BOM hierarchies into one table.
Tulip is not capable of connecting data like this into one neat table report. You could use the table api to build this in an external system or in a custom widget.
Instead, I would think about ways to get this information into one table.
If the number of components is statically defined, then you could change your table structure to have many columns. You could also try using Automations to summarize this data from the two tables you currently have into one horizontally longer table.
My recommendation would be to switch to a more scalable traceability architecture-- I made a mock up of this below. Hopefully this makes sense. From this type of table you can export in many different ways or even create an app to recursively drill down well beyond two levels.
Thank you for your comment.
I understood the constraint.
You could also try using Automations to summarize this data from the two tables you currently have into one horizontally longer table.
I am interested in this process and would like to know more about it.
Could you share the link where I can understand the process?