27

You define an attribute of type decimal and sets up limit for this attribute. You then use the attribute type in a product model because you want this value in the configuration dialogue to be delimited by the limits. But these limits are not used, so the user can type any value in the field. So my suggestion is to enable these limits either by looking up in the model or secondary give posiibility to define some limits on the attribute in the model.

STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for your feedback. Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.

 

Sincerely,

Johan Hoffmann

PM, Microsoft

Comments

F

Although the work around works, it's difficult to push the configurator to customers that need the precision.
Hopeful others will vote this one up as it should be a simple setting on the attribute, or even respect the UOM precision on the attribute.

Category: Product Information Management

F

My patented workaround for now is a shadow integer field converted forth and back from the real input:
Size 1,23 m = 123 [cm]
Then I feed the Solver with integers and let it deliver an integer solution, then use a "calculation" to write it back into the BOM etc.

Category: Product Information Management