![]() iLogic code gets around this issue, as it seems to completely ignore the currency formatting of that property.Īs far as I am aware, the Estimated Cost property is the only one where the #2 issue exists.Autodesk Inventor Professional is 3D CAD Modelling Software for Mechanical Engineering Design and Simulation.Īutodesk Inventor 3D CAD software offers an easy-to-use set of tools for 3D mechanical design, documentation and product simulation. As a result, there is no way I'm aware of to set up a User Parameter-based solution for the Estimated Cost iProperty that doesn't result in a unit mismatch issue. Currency is not an available unit type for a parameter, but is built in to the Estimated Cost iProperty.In this example, you could solve it by making a User Parameter that does the math, and no iLogic code would be needed. But you can't actually make an iProperty expression multiply those properties to give an area. So you can make a description that includes something like "PLATE- X ", where WIDTH and LENGTH are the properties created from part dimensions or other parameters. iProperty expressions can combine text from other properties, but can't do math.But I believe there are two issues that complicate it and make iLogic necessary: ![]() My setup for this has been established for quite a while (and as I mentioned earlier in the thread, is now used infrequently anyway).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |