This function is not reserved to assembly files and will work on any document class-based object. Only one instance per file is returned, regardless of how many times a part is used in an assembly. This function does a jam-up job of returning all FILE instances within any document object. This function is basically a document dump. We will look briefly at raw document references, and then take a bit of time stepping into the assembly document container hierarchy.įor the scope of this discussion, I will limit that object hierarchy as follows:ĭocument -> AssemblyDocument -> Assembl圜omponentDefinition -> ComponentOccurances -> ComponentOccuranceĬomponentOccurancesEnumerator Just Give Me Everythingįirst, we can get all file references by calling for ‘AllReferencedDocuments’. Inventor has class objects that have intelligence built in to deal with how an assembly document, for example, will behave. In our case, documents represent parts, assemblies, spreadsheets, drawings, etc. However, documents can be interpreted in numerous ways.

Each document is simply a reference to a file that is, or will be upon saving, stored on a file server or local drive. Each component in an assembly is a document. It is very important to understand the Autodesk Inventor® assembly document structure and hierarchy. What follows is a collection of my notes and references relating to the iLogic Assembly document functions that I used to automate drawing creation. I have been on a project that demanded a lot of drawings, and after I got through revising about 20 drawings, I decided that digging into iLogic would be a sound investment.

It appears as though there is only enough time to either research engineering software or research software API.

My background was C++ and I was moving to C# when, well, I started writing. It has been some time since I was regularly programming. Back December 15th, 2014 Inventor iLogic Notes for Assembly Drawings

Inventor drawings