cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Ability to set the mesurement system at the attribute and object level

Ability to set the mesurement system at the attribute and object level

When a company deals with both imperial and metric components, there is no choice to have 2 reusable attributes for the same dimension: one in metric and the other in imperial to get the value "user-readable".

E.g: the length of a screw in millimeters or inches.

 

Having 2 IBAs makes searches, classification browsing, or table displays less efficient.

The ability to set the measurement system for an object or even for an attribute of an object would be much better.

2 Comments
Level 15

In this instance I would have to disagree. When it comes to purchased items like hardware, they should be modeled and dimensioned in their natural units. Metric lengths in mm and imperial lengths in inches.

 

There are other instances where the units of the value are important and NX added units to their attributes years ago because of this.

 

Level 8

I believe we agree. Having 2 IBAs for the same dimension is a workaround and not a reliable solution.

That's why I posted this idea to be able to specify the measurement unit on each object. I guess I wasn't clear enough.

 

If my screw matches to the metric standard (ISO), I want to specify the length in mm and the attribute to be display in mm (or at least in meters).

If my screw matches to the imperial standard (ANSI), I want to specify the same attribute in inches and obviously the value displayed in inches.

 

Florent