Pipeline Rule - converted numbers changed to zeros

Ok, I’m stumped then. Here’s the post I referenced when trying to get the fields stored as numbers: Changing a field type from string to numeric and mid-setup and past string values. I must have misunderstood.

When I removed the number conversion from the rule, the rule failed. I’m assuming that was because those three fields had already been created as being numeric (with zero as every value). To test my theory, I renamed the fields, and the rule immediately started working and storing what looks like the correct numbers in the new fields. However, when I try to create a chart using one of the fields, the number of field occurances gets charted instead of the field value. That’s my root problem. To me, this seems to be caused by the field being stored as a string instead of as a number. Just a guess though, because I don’t know how to check the field data type. If I’m correct in my guess, I have no idea why something like 15791.01 would be interpreted as a string.