topic Re: Loop through Assembly for iProperties in Inventor Programming Forum

Loop through Assembly for iProperties

NachoShaw — Mon, 10 Aug 2015 07:56:47 GMT

I need to loop through an assembly and get iProperties for each part. The iProperties i need are:

Part number

Weld Material

Material

Mass

How can i do this? I can loop through the assembly but im struggling to get all of the properties. I can only seem to get the Mass..

Thanks

Nigel

Re: Loop through Assembly for iProperties

humbertogo — Mon, 10 Aug 2015 09:00:05 GMT

Here something

 For Each oCompOcc As ComponentOccurrence In oLeafOccs

                Select Case oCompOcc.DefinitionDocumentType
                    Case DocumentTypeEnum.kPartDocumentObject
                        Dim objPartDocument As PartDocument = TryCast(oCompOcc.Definition.Document, PartDocument)
                        'Design Tracking Properties, {32853F0F-3444-11D1-9E93-0060B03C1CA6}
                        Dim iProperties As PropertySet = objPartDocument.PropertySets.Item("Design Tracking Properties")
                        MessageBox.Show(iProperties.Item("Part Number").Value)
                        MessageBox.Show(iProperties.Item("Material").Value)
                        MessageBox.Show(iProperties.Item("Weld Material").Value)
                End Select

            Next

Re: Loop through Assembly for iProperties

NachoShaw — Mon, 10 Aug 2015 13:34:37 GMT

thanks for the code sample.

will this take into account parts in sub assemblies too?

thanks

Re: Loop through Assembly for iProperties

NachoShaw — Mon, 10 Aug 2015 21:14:26 GMT

are you using the ComponentOccurrenceEnumerator? im having a hard time to get it working right. Any chance you can put the full code in please?

Thanks

Re: Loop through Assembly for iProperties

humbertogo — Tue, 11 Aug 2015 07:49:33 GMT

Yes i using ComponentOccurrenceEnumerator

below the full code

        Public Sub GetDocumentType(ByRef oAssemblyDoc As AssemblyDocument)
            Dim ComponentOccsEnum As ComponentOccurrencesEnumerator = Nothing
            Dim oAsmDef As AssemblyComponentDefinition =  oAssemblyDoc.ComponentDefinition
            Dim oLeafOccs As ComponentOccurrencesEnumerator = oAsmDef.Occurrences.AllLeafOccurrences
            For Each oCompOcc As ComponentOccurrence In oLeafOccs

                Select Case oCompOcc.DefinitionDocumentType
                    Case DocumentTypeEnum.kPartDocumentObject
                        Dim objPartDocument As PartDocument = TryCast(oCompOcc.Definition.Document, PartDocument)
                        'Design Tracking Properties, {32853F0F-3444-11D1-9E93-0060B03C1CA6}
                        Dim iProperties As PropertySet = objPartDocument.PropertySets.Item("Design Tracking Properties")
                        MessageBox.Show(iProperties.Item("Part Number").Value)
                        MessageBox.Show(iProperties.Item("Material").Value)
                        MessageBox.Show(iProperties.Item("Weld Material").Value)
                End Select

            Next
        End Sub

Re: Loop through Assembly for iProperties

MechMachineMan — Mon, 17 Aug 2015 13:32:00 GMT

This workflow is interesting. It could all also have been accomplished by:

1. Open GA

2. Open BOM

3. Set BOM to Structured - ALL levels

4. Expose necessary iProperties if not already exposed

5. Export BOM to excel

6. Open BOM in excel and delete columns that are not needed.

Re: Loop through Assembly for iProperties

NachoShaw — Mon, 17 Aug 2015 17:33:42 GMT

yes but thats a ridiculously long and manual method. Originally, i started like that but then had a need to get the list into a data table. I looped through the assembly and collected the bom however, the bom does not consider design view reps. If the assembly has a few alternate view reps with parts visiblity turned off in those reps, i get an incorrect bom for that particular view rep. So i moved away from the bom and am looking for an alternate method

thanks

Re: Loop through Assembly for iProperties

MechMachineMan — Mon, 17 Aug 2015 17:43:19 GMT

Are you planning on having it batch extract for all view reps or are you
fine doing 1 view rep at a time/ as required?

Re: Loop through Assembly for iProperties

NachoShaw — Mon, 17 Aug 2015 17:47:57 GMT

Im fine doing just one view rep at a time 🙂
Its only the active view rep i need, i have a switch to select different view reps incase its not the correct rep. My current method however, doesnt provide a qty list. I have to use linq at the end and it takes ages...

Thanks

Re: Loop through Assembly for iProperties

MechMachineMan — Mon, 17 Aug 2015 18:26:39 GMT

Yeahhhhh... Trying to get quantity of an assembly and exclude invisible/suppressed parts is tough. Inventor really doesn't seem to like that workflow.

Have you thought about using multiple similiar sub-assemblies; except instead of making parts invisible/suppressed you make a new assembly document which has them deleted?

This would also go along easy with drawings as the parts have the same internal name. You would just have to replace model reference in the drawings were you to want to use a different "view rep".

Re: Loop through Assembly for iProperties

NachoShaw — Mon, 17 Aug 2015 18:41:33 GMT

dont know if that would work or not. The assemblies are already done and we have a catalog that goes back a long way. We use view reps alot as they are quick and easy to show different permutations of a fixture assembly.

I do have a working routine for bom items to be listed based on their visibility but its like a multi loop and takes a long time. For example:

for each item in bom, loop assembly, find it and xheck its visibility.

this means, for every bom item iteration, there is an assembly loop. So, 100 bom items becomes 100 assembly loops instead of just one loop. I couldnt find a method of looping through a bom and for each item, checking its visibility. I tried component definitions and occurrences but nothing worked

cherrs

Re: Loop through Assembly for iProperties

jlane — Fri, 04 Mar 2016 22:22:52 GMT

Referring back to the original post on this thread, I would like to do something similar, but using AllReferencedDocuments instead of ComponentOccurance.

I found a sample in this blog, but it doesn't provide the code to loop through any sub-assemblies should they be found.

Could someone help me out with the code?

Thx!

Re: Loop through Assembly for iProperties

MechMachineMan — Fri, 04 Mar 2016 22:25:39 GMT

For each oDoc as Document in
ThisApplication.ActiveDocument.AllReferencedDocuments
'Do something with oDoc here
Next

Re: Loop through Assembly for iProperties

jlane — Fri, 04 Mar 2016 22:33:11 GMT

Hi MechMachineMan, thx for your quick reply.

Yes, that's what exactly what I have. I have it successfully looping through each referenced document in the active assembly, and it works very well.

How can I get it to iterate though any sub-assemblies when they are encountered? (Sorry if I wasn't clear on that, my bad)

Re: Loop through Assembly for iProperties

MechMachineMan — Fri, 04 Mar 2016 22:49:39 GMT

It goes through each loaded document thats referenced by the primary
assembly only once, and thus will loop through sub-assembly parts in an
unpredictable order. You will need to test the parts to find what criteria
it needs to meet in order for it to have your changes implemented.

Re: Loop through Assembly for iProperties

jlane — Mon, 07 Mar 2016 14:18:51 GMT

Excellent, thx for that clarification! I'm new to this and still becoming familiar with the behaviour. I tried it out and it worked exactly as you described.

Re: Loop through Assembly for iProperties

Jef_E — Thu, 10 Mar 2016 07:55:12 GMT

Why do you need the BOM to do this? I'm trying to understand what is going on here.. But if i'm correct ( let me know if i'm not ).

You want to export the iProperties for all VISIBLE components in the assembly and sub-assemblies? And count their quantity also based on the visibility?

If this is the case you could do this in 1 inventor loop and 1 internal loop with sub-loop? and not use the BOM?

Inventor loop:

You can create an array, store all iProperties on the found occurences IF visible.

When the array is made, you could loop through it. Read the first row it's partnumber. Start a sub-loop counting the matching partnumbers you encounter IF a partnumber matches you could set it to "0" or nothing in example, just something you can recognize as already counted. If the sub-loop is done you can export the first row it's iProperties to a spreadsheet along with the counted QTY.

Now your loop chechs all the next items in the array. If the partnumber returns "0" or nothing in example, you can skip it and do the next because that occurence is already counted in the spreadsheet.

In my humble experience a loop in a self created array always works alot faster then looping in the Inventor occurences. This because you only have data you want in you selfmade array and in Inventor the items are much larger because they hold data you don't need.

Maybe i'm missing something why this would not be an solution. Please let me know 🙂