Value not a plain number

A column mapped to a number holds a value that is not a plain number, such as 1,200 or 12 kg. The product does not guess what it means, since 1,200 is a thousand two hundred in one convention and one point two in another, and it does not drop it either. The run stops at the Map Data node.

What to do

Correct the value on the named row to a plain number in the source data, or map the field to the right column if the wrong one is mapped. The workflow runs once every value in the column reads as a number.

Where it comes from

Shown by Map Bill of Materials, Map Demand History, Map Demand Policy, Map Demand State, Map Handling Policy, Map Handling State, Map Inventory Policy, Map Inventory State, Map Lanes, Map Location Policy, Map Location State, Map Locations, Map Production Policy, Map Production State, Map Products, Map Supply Policy, Map Supply State, Map Transport, Map Units & Conversions. It is one of the messages about a node.