Who would benefit? |
All data entry users / all user of inriver |
What impact would it make? |
Better UI/UX and better data management. Currently only option is to write UOM in the fieldtype name or use specifications which has many limitations compared to ‘normal’ attributes. |
How should it work? |
Idea / wish: ‘Unit of Measure’ can be set as a property on the fieldtype – ideally selected from a CVL to ensure consistency. Furthermore, the unit of measure property needs to be language specific so the unit of measure will show correctly in the languages applied in the data model and shown in the Webportal. I found a post in this in the inriver community idea archive. However, I cannot find it in the aha idea portal, it provides many good inputs so please also look at this: https://community.inriver.com/hc/en-us/community/posts/360007749460-One-attribute-with-3-data-points-Name-Value-UOM. |
Why is it needed? |
Better UI/UX and better data management. Currently only option is to write UOM in the fieldtype name or use specifications which has many limitations compared to ‘normal’ attributes. |
Additional feedback, background or context:
Hi! This is a functionality that Volvo Buses is also interested in, or other efficient ways to work with UOM in the data model. Writing the UOM in the fieldtype name or use specifications creates different types of data management issues for us, why we would suggest that you explore this idea further. You are welcome to contact us if you want to discuss more in details on our use cases and requirements on this topic.