Inventor’s iProperties system includes some lesser known behaviors, especially when working with date fields and expression‑driven values, that can affect automation and data consistency. In this post, we’ll look at how Inventor treats the date properties as well as how expressions work behind the scenes in both the UI and the API.
In my last post, Accessing iProperties, we explored the basics of reading iProperties in Inventor. Now it’s time to go a level deeper. In this article, we’ll look at how to create, edit, and manage custom iProperties — both with iLogic and with the more powerful Inventor API.
Working with iProperties is a common task when automating Autodesk Inventor: managing metadata, preparing BOM exports, or enforcing naming rules. Developers typically access these properties through one of two interfaces: the Inventor API or the iLogic API. Although both expose the same underlying document data, they do so in noticeably different ways. The object models differ, the available property names are not always identical, and some operations are simpler in one API than the other.
Yesterday, I scrolled down the "Inventor Ideas" board and found this idea: "Virtual Component Library." It has 112 votes, so I guess that people would like this feature in Inventor. However, this idea was posted in 2012 and is still gathering support. Probably it will not be implemented any time soon. But with a small I logic rule you can implement this functionality yourself.
This is just a random post to showcase how to find all the properties of a (face) appearance. I created the rule to help someone on the Autodesk "Inventor Programming Forum". Someone else (or me) might find it useful in the future.
A user on the forum posted the code below. He uses it to clean up his drawing resources. He wrote, "It appears to work nicely but I'd be grateful if someone with actual coding knowledge could cast an eye over it". I pretend to have some knowledge. And I started commenting on his code. In the end, I realised, it could benefit everyone.
In some situations, you might want information from the user but a complete form is too much. In that case, you might want to look at the mini toolbar. Here you will find an example code.
Sinds Inventor 2023 we have the new mark-feature. This is a cool feature with lots of possible use cases. But I expect that many users want to use it for laser etching some number on a sheet metal part. For example to etch the part number. Now if you want to do that on all your parts then you're in for a lot of work. Just this week there was a question on the forum. If it would be possible to automate the process. (Link)
Just a random post about an object-oriented way of exporting flat patterns to dxf. if you want to use the code you only need to change the stuff in the main-sub. All other stuff is just there to help you (and not to be touched).
On my job, I came across a VBa program that consisted of 2 parts. The second part would add dimensions to your drawing. The first part would let you select faces/edges and add properties to it. Pairs of faces/edges are used to create dimensions on a drawing. Those properties included things like the position of the dimension text and to which view the dimension belongs.
Just as the title indicates, there is a way to 'sort of' change the functionality of an InputListBox, so that you can select multiple items at once. No more having to use a regular InputListBox within a loop, and only being able to select a single item each time until you escape the loop.
Autodesk Inventor, Vault, Git, C#, vb, .net, php HTML, css, js
University computer science.
HBO Mechanical engineer.
MBO Fine mechanics.
Programmer and
Mechanical engineer
at Kelvion
(2016 - 20..)
Mechanical engineer
at Strukton
(2009 - 2016)
Mechanical engineer
at RDG-engineering
(2007 - 2009)
CNC Programmer
at VMC
(2005 - 2007)
volunteer
at Taizé
(2007)
Objectgeoriënteerd analyseren en ontwerpen, Objectgeoriënteerd programmeren in Java, Webapplicaties: de clientkant, Databases, Security Aware Programmer, Web Security Specialist