Navigate Parts inside a Document

Javier_López_del_Pueyo

Hi!

I have a question regarding the navigation of parts inside a document. 

I have been looking for a detailed list of all the parts that are contained within a document, so I can look at their part names, part number or descriptions, for instance. 

I have tried to get that from the Workspace Properties tab, but a haven't been able to filter the results to Parts only. Also, If a want to see specific information, I have to expand the list of the Part Studio where the Part was created and left click on the specific Part, which is not very efficient.

Also, I tried the Tab Manager, which has a Search tab and filtering options, but only goes to the Part Studio level. 

Through the Insert option inside an Assembly, Parts can be viewed, but detailed information is not shown. It is not very convenient either.

I feel the best tool to do so is the Advanced Search tab outside the document. But I haven't figured a way to filter all the Parts inside a specific document. 

Any ideas?

S1mon

If you have an assembly with all the parts, you can look at the BOM view for that assembly and see names, part numbers, descriptions etc. (assuming you've set up the columns and the parts have those properties defined and filled out).

NeilCooke

javl0p_2 said:

I've seen Custom Tables being used to show Part properties of a Part Studio. Is there a way to extend that to every element of the Document?

I've dived into the corresponding FS Code and the command evaluateQuery only applies to a specific Context (the actual Part Studio). I've seen there is a opMergeContexts which could potentially expand the Context to every Part Studio inside the document but I am a bit stuck on how to actually do it.

Anyone?

Custom tables will not work across contexts. 

S1mon

If you have an assembly with all the parts, you can look at the BOM view for that assembly and see names, part numbers, descriptions etc. (assuming you've set up the columns and the parts have those properties defined and filled out).

Javier_López_del_Pueyo

Yes, that could be a workaround, although not exactly what I was looking for. 

Thanks!

Javier_López_del_Pueyo

I've seen Custom Tables being used to show Part properties of a Part Studio. Is there a way to extend that to every element of the Document?

I've dived into the corresponding FS Code and the command evaluateQuery only applies to a specific Context (the actual Part Studio). I've seen there is a opMergeContexts which could potentially expand the Context to every Part Studio inside the document but I am a bit stuck on how to actually do it.

Anyone?

NeilCooke

javl0p_2 said:

I've seen Custom Tables being used to show Part properties of a Part Studio. Is there a way to extend that to every element of the Document?

I've dived into the corresponding FS Code and the command evaluateQuery only applies to a specific Context (the actual Part Studio). I've seen there is a opMergeContexts which could potentially expand the Context to every Part Studio inside the document but I am a bit stuck on how to actually do it.

Anyone?

Custom tables will not work across contexts. 

chadstoltzfus

You could create a custom feature that sets the output of the custom table as a variable, use that custom feature in each part studio, then create a "compiled" part studio that uses a custom feature (like Super Derive) to import the variables from each part studio. Then all you would need to do is program your custom table to also look for those variables and concatenate the variables together. 

EDIT: Actually, thinking about it you could use Variable Studios and just keep appending to the same variable