Inventor Custom iProperties name is able to duplicate from default name

[mdinesh]

For better clarity I am comparing my question with f(X) Parameter to i-Properties.

Both we can use to store data about component.

In f(X) parameter we cannot use same parameter name more than once, even though if it is "User Parameter" or "Model Parameter".

But in the same case in "Custom i-Properties" we are able to create property name same as in "Summary" or "Project".(Please find the attached image for reference).

If duplicate is not accepted in f(X) parameter means it should not accept in " i-Properties" also.

I am aware that through api we can create new "Property Set" ,still there should be priority hierarchy that [General, Summary, Project, Status & Physical] as top and those property name should not used in Custom and user defined property set.

This made additional information need to pass from Database to code.

For Eg:

"Part Number" = "XYZ" (this can not be used because same name can be used in Custom tab also)

"Project, Part Number" = "XYZ" or "Custom, Part Number" = "XYZ"

While using API, the way it is accepting of duplicate name in i-Properties leading us to use more specific about the property set which it is belong. we are not doing this to Model or User parameter but why this is for i-Properties?

[johnsonshiue · Accepted solution]

Hi! Indeed, the behaviors are inconsistent in this regard. It can be confusing for sure. I have seen cases that the duplicated iProperties lead to incorrect displayed values.

The general rule of thumb is that you want to keep things unique in Inventor, in terms of naming (files, objects, components, parameters, and properties). Try to avoid duplicates whenever possible.

Regarding the property names, I suspect it could be related to the fact that custom iProperties and the regular iProperties are managed in different places. So, duplicated names are allowed. Also, an Instance Property can have the same name as an iProperty. There is an advantage of duplication in this case. Essentially, you can have a default value (in the iProperty), and an overridden value (in the same named Instance Property) when consumed in an assembly. You can document it in the drawing accordingly.

Many thanks!

[mdinesh]

Thanks for your reply...