topic Re: Displaying Part Description in Feature Tree in Inventor Forum

Displaying Part Description in Feature Tree

ToddPig — Thu, 26 May 2016 15:47:36 GMT

Is there a way to display the part description next to the file name in the feature tree?

Re: Displaying Part Description in Feature Tree

mdavis22569 — Thu, 26 May 2016 15:59:38 GMT

Like this

yes ...but not out of the box ...

also check out

https://knowledge.autodesk.com/support/inventor-products/troubleshooting/caas/sfdcarticles/sfdcarticles/Resetting-browser-name-to-file-name.html

Re: Displaying Part Description in Feature Tree

mcgyvr — Thu, 26 May 2016 16:35:33 GMT

Set this ilogic rule to trigger "on save" or whatever other trigger works for you..

'create reference to part
openDoc = ThisApplication.ActiveDocument
 
'format display name
openDoc.DisplayName = iProperties.Value("Project", "Part Number") & " (" & iProperties.Value("Project", "Description") & ")"
openDoc.Rebuild
 
'update
iLogicVb.UpdateWhenDone = True

Re: Displaying Part Description in Feature Tree

mdavis22569 — Thu, 26 May 2016 16:42:00 GMT

we do it via iproperties too

Re: Displaying Part Description in Feature Tree

cmyersSNP6E — Fri, 16 Dec 2022 23:40:33 GMT

I've tried this code but it keeps failing on openDoc.Rebuild, and gives the following error message:

Error on line 6 in rule: DescInModelTree, in document: 11000012.iam

Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))

When I comment out that line, the description is shown in parentheses after the parent part number, but none of the components or subassemblies within the parent, they still only show the part number. What am I missing?

More details in the "more info" tab:

System.Runtime.InteropServices.COMException (0x80004005): Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))
at Microsoft.VisualBasic.CompilerServices.LateBinding.InternalLateCall(Object o, Type objType, String name, Object[] args, String[] paramnames, Boolean[] CopyBack, Boolean IgnoreReturn)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateCall(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack, Boolean IgnoreReturn)
at ThisRule.Main() in rule: DescInModelTree, in document 11000012.iam:line 6
at Autodesk.iLogic.Exec.AppDomExec.ExecRuleInAssembly(Assembly assem)
at iLogic.RuleEvalContainer.ExecRuleEval(String execRule)

Re: Displaying Part Description in Feature Tree

johnsonshiue — Tue, 03 Jan 2023 21:10:13 GMT

Hi! The original rule only works for an ipt file, not an iam file. To extend it, change "Rebuild" to "Rebuild2" and it will work for iot and iam files.

Many thanks!

Re: Displaying Part Description in Feature Tree

swalton — Thu, 05 Jan 2023 16:38:41 GMT

I am experimenting with this rule using Inventor 2022. I've found an issue that I'd like to better understand.

I've modified the sample code with the Rebild2 command and it works well if I make a change to the description property in each document. I've set the rule to run on both "iProperty Changes" and "Before Save" in the Event Trigger window. Both work ok at the individual document level.

However, if I open an assembly that has sub-components with this iLogic code, and edit their descriptions in the BOM Editor, I can't get the display names in the assembly to update. In fact, I find that the parent assembly display name updates each time I change a sub-component description.

Is there a different Event Trigger I should use, or does the code need to be modified so that changes in the BOM editor are pushed to the individual sub-components and the display name of each component is updated in the parent assembly when the BOM Editor is closed/assembly saved?

Re: Displaying Part Description in Feature Tree

A.Acheson — Fri, 06 Jan 2023 06:55:52 GMT

Hi @swalton

So what is happening here is the documents you want the rule to run on are not being targeted.

With This External Rule ran before save event trigger the document object is the top most document indicated by ActiveDocument. So the Parent Assembly. See Picture(1)

'create reference to part Dim openDoc As Document = ThisApplication.ActiveDocument'ThisDoc.Document 'format display name openDoc.DisplayName = iProperties.Value("Project", "Part Number") & " (" & iProperties.Value("Project", "Description") & ")"

With this External Rule the document ran before save event trigger the object is driven by ThisDoc.Document which works to update the iproperties of any document the event trigger is targeting. So the rule runs on save on any document that has been dirtied. See Picture(2). The document can be dirtied by adjusting the iProperty in the BOM editor or deleting the occurrence Name.

Dim openDoc As Document = ThisDoc.Document 'format display name openDoc.DisplayName = iProperties.Value("Project", "Part Number") & " (" & iProperties.Value("Project", "Description") & ")"

Assembly7 Document Dirtied

In my testing I couldn't get any update snippets to provide any meaningful contribution so those have been omitted to avoid unnecessary updates.

Not sure if Method 2 is robust enough for your use. If not the only other solution I can think of is an external rule run manually to loop through the reference documents Of the Parent Assembly and force a change to the display name.

Dim Asm As AssemblyDocument = ThisDoc.Document Dim Trans As Transaction = ThisApplication.TransactionManager.StartTransaction(Asm, "Change Display Name In all files") 'Make this a single transaction For Each Doc As Document In Asm.AllReferencedDocuments 'Traverse all referenced documents If Doc.IsModifiable = True Then Try Dim PartNo As String = Doc.PropertySets.Item("Design Tracking Properties").Item("Part Number").Value Dim Description As String = Doc.PropertySets.Item("Design Tracking Properties").Item("Description").Value 'Format display name. Doc.DisplayName = PartNo & " (" & Description & ")" Catch End Try End If Next Trans.End 'End the transaction

Re: Displaying Part Description in Feature Tree

swalton — Fri, 06 Jan 2023 14:45:23 GMT

@A.Acheson

Thanks for the comments and the code snippet.

Preliminary testing looks good. Now to try editing iprops in Vault and Vault Data Standard...