Don't use decimal keys when accessing Xano objects; use integers instead
Another thing I wish I knew beforehand.
Do not use a decimal as the key for accessing a value in an a Xano object; convert the key to an integer first. Trying to access a value with a decimal key will return null.
E.g. do this:
Not this:
I couldn’t find an explanation of this behavior in the documentation, so thought I would share it with you here.
This is probably something I should know if I were a trained developer, but I’m not. And you probably aren’t either, so here you go.
Maybe be the "." dot notation in the decimal caused it to find the [0] index of the decimal number so for decimal '1000.1' is converted to 1000.[1] under the hood in xano. I think if you use '..' double dot notation to access the object instead it should work.