Hi Guys.
I was thinking to isolate the Parts in an assembly and save them as Each representations
for Example, the Below Assy has 17 ipts
so when the automation is run, each parts are to be isolated and 17 view representations are created
for part 1
similary it has to create number of View representations based on number of IPTS
Could anyone help in creating Ilogic/VBA code for Automating this process..
Thanks in Advance !!
hi @dalton98
Thanks for the Code, it works correctly as I expected.
Still as an improvement, design views are created for each and every parts.
Is there a way we can avoid duplicate creation of design view Representations if same IPT/IAM is used more than once,
for eg, in picture below, one desing View representation is sufficient for LO-096581-01(used 7 times)
Thanks in Advance!
Just another little tip...you may also want to ensure that the current component (the one within the loop & selected) is actually 'Visible = True' within the loop somewhere, just to be thorough. I know that manually, when you select a component that has already had its visibility turned off, the Isolate command is not shown, and the Undo Isolate command is greyed out, so I don't know if that would cause an error when you execute the Isolate command on a selected component that was already not visible itself or not.
Wesley Crihfield
(Not an Autodesk Employee)
Hi @get2dpk. That behavior has been a pain for a long time. The DVR (DesignViewRepresentation) does have the Locked property, but that does not exactly seem to fit this need. It just prevents changes to that DVR from being saved in that DVR when you save the document. It would be nice to have an additional property for another type of lock on that DVR, which would prevent any other components from showing up in it. But that may not be feasible for the folks at Autodesk to provide a solution for, and enforce.
Below is another similar iLogic rule example that you should be able to run as many times as you want to keep a DVR for each component, and keep that component the only one visible in that DVR. I chose to go the loop route, instead of the Try...Catch statement for ensuring the needed DVR exists, simply because we can, and it is the proper way (even if I do not follow my own advise all the time 😉). It gets all collections first, then starts iterating the components. If a component is suppressed, we can not do much with it, without it throwing errors, so we check for that status first, and skip over those. (If we need to deal with those too, then we may need to add in some extra code for handling that.) Then we try to find an existing DVR with the same name as the component, by iterating the existing DVR's and checking their name against the name of the current component. If it was not found, it will get created. Then that DVR is activated, all components hidden, and that one component's visibility turned on. Then we activate the originally active DVR, to avoid disruption of what you were doing before. Then update the assembly, if needed. Give this a try, and see if it does what you need it to. And if needed, we may want to use a helper event handler to automate this rule to run when certain events happen.
Sub Main
If ThisDoc.Document.DocumentType <> DocumentTypeEnum.kAssemblyDocumentObject Then Return
Dim oADoc As AssemblyDocument = ThisDoc.Document
Dim oADef As AssemblyComponentDefinition = oADoc.ComponentDefinition
Dim oOccs As ComponentOccurrences = oADef.Occurrences
Dim oRepsMgr As RepresentationsManager = oADef.RepresentationsManager
Dim oDVRs As DesignViewRepresentations = oRepsMgr.DesignViewRepresentations
Dim oOrigDVR As DesignViewRepresentation = oRepsMgr.ActiveDesignViewRepresentation
For Each oOcc As ComponentOccurrence In oOccs
If oOcc.Suppressed Then Continue For
Dim oOccDVR As DesignViewRepresentation = Nothing
For Each oDVR As DesignViewRepresentation In oDVRs
If oDVR.Name = oOcc.Name Then
oOccDVR = oDVR
Exit For
End If
Next 'oDVR
If oOccDVR Is Nothing Then
oOccDVR = oDVRs.Add(oOcc.Name)
End If
oOccDVR.Activate
oOccDVR.HideAll
oOcc.Visible = True
Next 'oOcc
oOrigDVR.Activate 'restore originally active DVR
If oADoc.RequiresUpdate Then oADoc.Update2(True)
'If oADoc.Dirty Then oADoc.Save2(True)
End Sub
If this solved your problem, or answered your question, please click ACCEPT SOLUTION .
Or, if this helped you, please click (LIKE or KUDOS) 👍.
Wesley Crihfield
(Not an Autodesk Employee)
I guess I did not pay good enough attention to the previous responses where it was mentioned that you needed all components referencing the same model file (resulting in same base component name) to be visible in each view rep. I had that similar sounding code on hand, so I posted what I had, without looking into it deep enough. With that added functionality in mind, and with a couple of the tips mentioned by @J-Camper in mind, I modified a copy of my earlier code. I kept my DVR's loop in place, instead of the Try...Catch statement, for finding/creating the needed DVRs, but did the other loops and collections a bit differently, blending some existing and new stuff together. Just as another interesting example to look at for the same basic task. Not that there is anything wrong with the previous versions, just playing around with it a bit.
The code is in the attached text file.
Wesley Crihfield
(Not an Autodesk Employee)
Also just a couple more tips to keep in mind, if performance is an important factor in your code solutions...
Using 'Is Nothing' is generally preferred over using 'IsNothing()', because IsNothing() sends the input object to another vb.net Function, then receives the result back from that other Function, which takes a little more processing than the 'Is Nothing' way, because it just directly evaluates it in place, with no external calls. I used to use IsNothing a lot myself also, until I read multiple discussions about it online, then went back and changed that little detail in a ton of my work related rules.
Also, when you are planning on iterating through a collection, it is best to get the collection to a variable before the start of the loop, then reference that variable. This is because, if you are 'getting' the collection within the definition line of the loop, it is re-obtaining that collection each time it iterates, reducing performance. At leas that is what I have heard, which is why I usually get my collections to a variable before my loops start in all my latest examples, and in my work related code solutions. Another one I picked up not too long ago, and used to do differently myself.
I have also read multiple discussions about, if an Try...Catch statement 'can be avoided' by using a simple loop with If...Then statement, then which is more efficient/proper. Well avoiding the Try...Catch statement, when you can, seems to be the 'proper' way. Whether or not it is more efficient (as far as processing) is more hotly debated and there are several variables involved, but most agree that the regular loop with If...Then statement is more efficient (again in processing). Using a Try...Catch statement is often much faster to type though because it usually requires less code when we are in a hurry. My own codes are still mixed with both, but I am trying to revert most to using loops where possible.
Wesley Crihfield
(Not an Autodesk Employee)
