Browser Node Name

Browser Node Name

Anonymous
Not applicable
1,448 Views
8 Replies
Message 1 of 9

Browser Node Name

Anonymous
Not applicable

Can browser node names be used/synced as iProperties? Or be used in drawing partlists?

0 Likes
1,449 Views
8 Replies
Replies (8)
Message 2 of 9

clutsa
Collaborator
Collaborator

Can you give a more specific example?

If I've helped you, please help me by supporting this idea.
Mass Override for Each Model State

Custom Glyph Icon for iMates

0 Likes
Message 3 of 9

Anonymous
Not applicable

We have problems TAGGING (P&ID numbers) valves. Valves are ipt's, but the same size/type of valve use the same ipt. so no iproperty for TAGGING. It would be nice if we could just rename the "node name" into the TAG of the valve and use that in our drawing partlists. So more valves of the same type use the same ipt, but have different node names, and so different TAGs.

 

Would that be handy?

0 Likes
Message 4 of 9

k14348
Advocate
Advocate

Public Sub CreateCustomProperties()
' Get the active document.
Dim invDoc As Document
Set invDoc = ThisApplication.ActiveDocument
' Get the user defined (custom) property set.
Dim invCustomPropertySet As PropertySet
Set invCustomPropertySet = invDoc.PropertySets.Item("Inventor User Defined Properties")
' Declare some variables that will contain the various values.
Dim strText As String

' Set values for the variables.
strText = invDoc.DisplayName

' Create the properties.
Dim invProperty As Property
Set invProperty = invCustomPropertySet.Add(strText, "BrowserName")

End Sub

0 Likes
Message 5 of 9

clutsa
Collaborator
Collaborator

I'm sorry I'm still lost. When I have two of the same parts in an assembly you can interchange where they go when you build it because they are the same part. Way back at my last job I did have one part that was for electric terminal strips that was the same part over and over and then each terminal section had a tag that slid into it... is that sort of what you have going on?

 In your first post your model tree had two "11081". You want to add more details to those node names and have them show up as two different parts in your material list. Does that sound right?

If I've helped you, please help me by supporting this idea.
Mass Override for Each Model State

Custom Glyph Icon for iMates

0 Likes
Message 6 of 9

Anonymous
Not applicable

yes that's what i want. It is not doable with custom properties as they are shared on same parts. Maybe node manes are a solution to this?

 

- that was the same part over and over and then each terminal section had a tag that slid into it... is that sort of what you have going on?

 

- In your first post your model tree had two "11081". You want to add more details to those node names and have them show up as two different parts in your material list. Does that sound right?

0 Likes
Message 7 of 9

clutsa
Collaborator
Collaborator

Can you tell me how you get the parts to separate in the parts list? I can't get parts that have the same part number that are in the same assembly to not group... I think you would have to make a custom table that you use as a parts list... it's doable but may be a lot of coding.

If I've helped you, please help me by supporting this idea.
Mass Override for Each Model State

Custom Glyph Icon for iMates

0 Likes
Message 8 of 9

Anonymous
Not applicable
0 Likes
Message 9 of 9

clutsa
Collaborator
Collaborator

So that seems to work if the model numbers are different but the part numbers in the models are the same... if I put two of the same model into the same assembly that does nothing. If you have different models you can make your descriptions (or other iProperty) different... 

Is there anyway you can create a dummy file of one of your assemblies and load that so we can work with an actual file? It's difficult to come up with ideas when you're not exactly sure how your part are made and being used.



 

 

If I've helped you, please help me by supporting this idea.
Mass Override for Each Model State

Custom Glyph Icon for iMates

0 Likes