You’re kidding, right? Custom variables to be used across scenarios can only be whole numbers? I can’t use decimals? How do I store a number that has a decimal so other scenarios can read it when they are run?
Hello @Brian_Smith1 
I can see that my colleague from the Customer Care Team has responded to you regarding the Custom Variable and will leave it here for other Makers:
Where the selected type is a number, it currently supports whole numbers only. I have reached out to our devs regarding this matter. Another option you can try is setting that Custom Variable’s type to text, then use a parseNumber() function as a workaround.
Thank you for your understanding. 
3 Likes
parseNumber(1.5) does not work for you?
@alex.newpath Although that is possible, it’s a little cumbersome for the formula I’m using and defeats the purpose of simplifying it. Also, my other issue was no where in the documentation does it say that the custom variable is whole number only. (I could have missed it). It seems like an oversight.
Feel free to suggest that numbers with decimals be allowed,
You can submit this suggestion to the Idea exchange, under Platform Ideas and Improvements. However, do search for a similar request (and also upvote), just in case it has already been suggested to avoid duplicates.
1 Like
Make is a system that has many data types but due to the nature of how it was designed a number is not one of them. There are interesting posts on this that create a bug like this one I posted:
Bug in average() function when passing in numeric strings
Be very careful when dealing with numbers. It’s not really an oversight — it’s sort of a purposeful implementation because json is totally typeless and as a result everything is a string when data comes out of an api.
1 Like