Create empty Parts List on drawing and fill rows by itterate the assembly browser pane
Hi @checkcheck_master. It might be doable, but you would have to use a 'CustomTable' instead of a regular PartsList. But then, the thought of traversing the model browser by code to find each component, then extract data, then record all its data into the individual cells that table, makes my head hurt, so I would avoid that process if possible, but that's just my current personal opinion. What about creating a regular PartsList, with all data present, then use something like the PartsListRow.Reposition method to sort the rows into the needed order. With that route, you would still need to get the proper order ahead of time, but then you could not only use a real PartsList, but also skip the whole data entry process. Just a thought.
Wesley Crihfield
(Not an Autodesk Employee)
I haven't tried it before, so I don't have any code sample for you to try out right now, but it certainly sounds doable. I have definitely navigated through the model browser to certain degrees by code before, but never completely, for a purpose like this before. Might get complicated, so I'll have to maybe look into it further tomorrow.
Wesley Crihfield
(Not an Autodesk Employee)
Been a bit busy today, but squeezed in some time for this. I assumed your drawing's parts list is only focused on stuff found in the first level of the Structured BOM view, because I think trying to go deeper with this specific process would likely be more trouble than its worth. I tried collecting a few different object types (BrowserNode, ComponentDefinition, etc.) while looping the browser pane, each with its drawbacks, until going back to the basics and just using a String. What I came up with is working in my test files so far (assembly document & drawing document for that assembly). The code is started while the drawing is active, then gets the model reference from the first view on the active sheet. Then either finds or creates a parts list. Then I call my custom function to search through the model browser of the model, and return a List of FullFileName's. In the function, each component it comes across, it attempts to extract the full file name of the document it is representing. And if it encounters an OccurrencePattern, it just works with the 'source/input' components, because all the rest are just quantity/copies, not originals. Then back at the main Sub area, we use the 'Index' of each name returned to reposition each PartsListRow. As you can see, it is a pain in the butt digging down into a PartsListRow to get a full file name to compare to, but it works. In retrospect, the assembly BOM angle does look like less trouble.
Here's the code I came up with:
Sub Main
If ThisApplication.ActiveDocumentType <> DocumentTypeEnum.kDrawingDocumentObject Then
MsgBox("A Drawing Document must be active for this rule to work. Exiting.", vbCritical, "iLogic")
Exit Sub
End If
Dim oDDoc As DrawingDocument = ThisApplication.ActiveDocument
oTG = ThisApplication.TransientGeometry
oSheet = oDDoc.ActiveSheet
oView = oSheet.DrawingViews.Item(1)
Dim oADoc As AssemblyDocument = oView.ReferencedDocumentDescriptor.ReferencedDocument
Dim oPList As PartsList
If oSheet.PartsLists.Count = 0 Then
oPos1 = oTG.CreatePoint2d(0, 0) '<<< WE CAN CHANGE THIS LATER >>>
oLevel = PartsListLevelEnum.kStructured 'fist level only Structured view
oSheet.PartsLists.Add(oADoc, oPos1, oLevel)
Else
oPList = oSheet.PartsLists.Item(1) 'or Pick, or find by Title
End If
'now get order needed
Dim oFileNames As List(Of String) = GetFileNamesInOrder(oADoc)
' MsgBox("oDocs.Count = " & oFileNames.Count, , "")
' For Each oFileName In oFileNames
' MsgBox("oFileName = " & oFileName,,"")
' Next
'now reposition rows to match needed order
For Each oRow As PartsListRow In oPList.PartsListRows
Try
Dim oDBOMRow As DrawingBOMRow = oRow.ReferencedRows.Item(1)
oCD = oDBOMRow.BOMRow.ComponentDefinitions.Item(1)
Dim oRowDoc As Document = oCD.Document
'check what 'Index' this one is in our list
oIndex = oFileNames.IndexOf(oRowDoc.FullFileName)
oRow.Reposition(oIndex + 1, True) 'specify next index, then use insert before, to position at that index
Catch oEx As Exception
MsgBox("Reposition method failed." & vbCrLf & _
oEx.Message & vbCrLf & oEx.StackTrace,,"")
End Try
Next
End Sub
Function GetFileNamesInOrder(oAsmDoc As AssemblyDocument) As List(Of String)
'oAsmDoc.Activate
Dim oList As New List(Of String)
oTopNode = oAsmDoc.BrowserPanes.Item("Model").TopNode
For Each oNode As BrowserNode In oTopNode.BrowserNodes
Try
If TypeOf oNode.NativeObject Is ComponentOccurrence Then
Dim oOcc As ComponentOccurrence = oNode.NativeObject
Dim oDoc As Document = oOcc.ReferencedDocumentDescriptor.ReferencedDocument
If oList.Contains(oDoc.FullFileName) Then
Continue For 'don't dig into any possible sub-components
Else
oList.Add(oDoc.FullFileName) 'add to the end
End If
ElseIf TypeOf oNode.NativeObject Is OccurrencePattern Then
Dim oOccPatt As OccurrencePattern = oNode.NativeObject
'process 'input' items only - others are just extra quantity items, not originals
For Each oObj In oOccPatt.ParentComponents 'ObjectCollection
If Not TypeOf oObj Is ComponentOccurrence Then Continue For
Dim oPOcc As ComponentOccurrence = oObj
Dim oODoc As Document = oPOcc.ReferencedDocumentDescriptor.ReferencedDocument
If oList.Contains(oODoc.FullFileName) Then
Continue For 'don't dig into any possible sub-components
Else
oList.Add(oODoc.FullFileName) 'add to the end
End If
Next
End If
Catch
End Try
Next
Return oList
End FunctionIf this solved your problem, or answered your question, please click ACCEPT SOLUTION.
Or, if this helped you, please click (LIKE or KUDOS) 👍.
If you want and have time, I would appreciate your Vote(s) for My IDEAS 💡 or you can Explore My CONTRIBUTIONS
Wesley Crihfield
(Not an Autodesk Employee)
Hi @checkcheck_master. Here is something very similar, for doing about the same thing with the BOM, when ran from the 'active' assembly document. The BOMRow object doesn't have a Reposition method, so what we are doing here is changing the row's ItemNumber value, according to the Index of the List. Then whet that process is done, we simply use the BOMView.Sort method to sort the BOM Rows by the ItemNumber values, to put them in proper order. If your ItemNumber column's Title is not "Item" (capitalization is important), you might need to edit that text in the rule before you run it. When I first ran this, it gave me an 'parameter is not correct' type error, which was simply because I first had the column title as "ITEM". After I changed that to "Item", that fixed it, and everything worked as expected.
Here is the BOM version iLogic rule code:
Sub Main
If ThisApplication.ActiveDocumentType <> DocumentTypeEnum.kAssemblyDocumentObject Then
MsgBox("An Assembly Document must be active for this rule to work. Exiting.", vbCritical, "iLogic")
Exit Sub
End If
Dim oADoc As AssemblyDocument = ThisApplication.ActiveDocument
oBOM = oADoc.ComponentDefinition.BOM
oBOM.StructuredViewEnabled = True
oBOM.StructuredViewFirstLevelOnly = True
oView = oBOM.BOMViews.Item("Structured")
'now get order needed
Dim oFileNames As List(Of String) = GetFileNamesInOrder(oADoc)
' MsgBox("oDocs.Count = " & oFileNames.Count, , "")
' For Each oFileName In oFileNames
' MsgBox("oFileName = " & oFileName,,"")
' Next
'now reposition rows to match needed order
For Each oRow As BOMRow In oView.BOMRows
Try
oCD = oRow.ComponentDefinitions.Item(1)
Dim oRowDoc As Document = oCD.Document
'check what 'Index' this one is in our list
'this retuns a 'zero' based Integer, so first item is at position zero
oIndex = oFileNames.IndexOf(oRowDoc.FullFileName)
'we don't want to use zero as an ItemNumber, so add 1 to each Index
oRow.ItemNumber = (oIndex + 1)
Catch oEx As Exception
MsgBox("Encoutered Error trying to set new ItemNumber value to BOMRow." & vbCrLf & _
oEx.Message & vbCrLf & oEx.StackTrace,,"")
End Try
Next
'sort the BOM rows by their ItemNumber column values now
'so that they will all be in proper order afterwards
'<<< If your ItemNumber column has a different Title, then change this >>>
oView.Sort("Item", True)
'oView.Renumber(1, 1)
End Sub
Function GetFileNamesInOrder(oAsmDoc As AssemblyDocument) As List(Of String)
'oAsmDoc.Activate
Dim oList As New List(Of String)
oTopNode = oAsmDoc.BrowserPanes.Item("Model").TopNode
For Each oNode As BrowserNode In oTopNode.BrowserNodes
Try
If TypeOf oNode.NativeObject Is ComponentOccurrence Then
Dim oOcc As ComponentOccurrence = oNode.NativeObject
Dim oDoc As Document = oOcc.ReferencedDocumentDescriptor.ReferencedDocument
If oList.Contains(oDoc.FullFileName) Then
Continue For 'don't dig into any possible sub-components
Else
oList.Add(oDoc.FullFileName) 'add to the end
End If
ElseIf TypeOf oNode.NativeObject Is OccurrencePattern Then
Dim oOccPatt As OccurrencePattern = oNode.NativeObject
'process 'input' items only - others are just extra quantity items, not originals
For Each oObj In oOccPatt.ParentComponents 'ObjectCollection
If Not TypeOf oObj Is ComponentOccurrence Then Continue For
Dim oPOcc As ComponentOccurrence = oObj
Dim oODoc As Document = oPOcc.ReferencedDocumentDescriptor.ReferencedDocument
If oList.Contains(oODoc.FullFileName) Then
Continue For 'don't dig into any possible sub-components
Else
oList.Add(oODoc.FullFileName) 'add to the end
End If
Next
End If
Catch
End Try
Next
Return oList
End FunctionIf this solved your problem, or answered your question, please click ACCEPT SOLUTION.
Or, if this helped you, please click (LIKE or KUDOS) 👍.
If you want and have time, I would appreciate your Vote(s) for My IDEAS 💡 or you can Explore My CONTRIBUTIONS
Wesley Crihfield
(Not an Autodesk Employee)
Hi @jjstr8. You are right about that. Since I did not use LOD's that much, and still have not used the new ModelStates that heavily, I often forget to account for others possibly using them more heavily. So, right near the top of the code, right after I set the initial value of the 'oADoc' variable, I injected a little bit of code I've used before to get around that possible issue.
Dim oADoc As AssemblyDocument = ThisApplication.ActiveDocument
If oADoc.ModelStateName <> "Master" Or _
oADoc.ComponentDefinition.IsModelStateMember Or _
oADoc.ComponentDefinition.IsModelStateFactory = False Then
oADoc = oADoc.ComponentDefinition.FactoryDocument
End IfAs you can see, I have obviously including more lines of code in there than are needed, but I wanted to show them here anyways, just to show the various things that can be checked (under the new 2022 ModelStates system). Any one of these 3 checks would probably be good enough. In earlier version of Inventor, using the LODs (LevelOfDetailRepresentations), there were some similar things we could check. Instead of checking "ModelStateName", we could check AssemblyDocument.LevelOfDetailName. The other two checks shown above for ModelStates did not exist for LOD's, but were more for the iAssembly system, which ModelStates partially took on the functionality of. The two similar (but not the same) checks were AssemblyComponentDefinition.IsiAssemblyMember, and AssemblyComponentDefinition.IsiAssemblyFactory, then the two corresponding properties to get either the factory or member were AssemblyComponentDefinition.iAssemblyFactory, and AssemblyComponentDefinition.iAssemblyMember.
Also note, you probably want to define your variable for the AssemblyComponentDefinition (if you will be using it) after this point in the code, so that it is pointing to the right AssemblyDocument.
Wesley Crihfield
(Not an Autodesk Employee)
I'm not sure what 'type' of enumeration you created, or what you mean by 'link a numbering to it', but I'm guessing you are thinking about a list, in which each element/position in the list can contain multiple pieces of data. Something like a Dictionary, where each entry has a 'Key' and a 'Value', and the whole dictionary can be sorted. Unfortunately most of those similar types of objects are just meant to hold 2 pieces of data in each entry, which can often be a little too limiting for more complex needs. The next two most obvious alternative objects to use would be either a List of Lists, or an Array of arrays, but then you can't directly sort the main list or array by something that is within the secondary list or array, without a lot more code. If you really wanted/needed a Dictionary type object that had a custom number of data blocks in each main item, you could create your own type of object using a Class block of code. But then you would have to define all the code behind its Properties and Methods yourself, to suit your needs. If your not familiar with a Class (link1, link2, link3), it is like the template or order form used to create new objects of that specific type, and defines what properties, methods, and events it has. Just some food for thought.
Wesley Crihfield
(Not an Autodesk Employee)
Sorry...I was looking for a simple emoji for mind blown, but came across that image and I just couldn't resist.
Wow. I just opening, then scrolled down through that really long text file full of code, and it just really blew my mind at first. You have obviously got a ton more work into this project that I had imagined. Good for you if you can keep up with all of that in one place. I think I would have separated each of those good size sub routines out into other modules, in an attempt to keep my sanity. 😂😅
Wesley Crihfield
(Not an Autodesk Employee)
