Has anyone seen in a 2.x script where an object has a property of a "number" that has been parseFloated for instance, but when you go to set a number field, it tells you that it is an invalid value? I have this issue where I have an object with a parseFloat(quantity). It does this just fine and is 1 with a data type of numeric. This object gets passed to the map phase and do the reduce phase where it is JSON.parsed before use. In the reduce phase, im still seeing it as 1 and numeric but when i go to set the quantity, it says 1 is an invalid value. If i parse float the quantity a 2nd time, and it is STILL 1 and numeric and set the quantity, it works just fine.