I made a macro, we'll call it "test" defined as
eval new_rate=$val$*$rate$
with the validation expression just checking rate to make sure it's a number
isnum($rate$)
When I call the macro.. I end up with something like test(revenue, .79)
When I do this, Splunk says my rate failed validation because .79 is considered a string. When I pass 0.79, it passes as expected. Is this intentional, or a bug? Additionally, is there a function that would pass .79 as a number?
Like this:
test(revenue, tonumber(.79))
Wonderful, thank you woodcock!
Note that I just retried all this in v6.5.0 and not only is tonumber
not necessary but it generates an error now (the same error that this solution was proposed to solve)!