Tweet
I have a back end program that is setting an app variable equal to a decimal value from a table, but when i use SetResponse('appVar':'xx':myvar) i have to do a data conversion on myvar to char since the prototype only accepts a character value for field 3. This has been fine in the past since it seems like valence is able to figure out what data type an app variable is.
Currently, after running this back end program, it reloads a form that has a field which is tied to that app variable (This field is also marked as required.) So after running the program the field goes from having the "This field is required" warning to having a value of, say, 100. This is all working perfectly fine on desktop, but on mobile, after running the program, the field goes from "This field is required" to saying "Value is not a valid number" which is leading me to believe that something on mobile is failing to recognize the app variable as numerical.
This would also align with a separate issue I've been having where an app variable that is an expression of other app variables is failing to show any result on my form on mobile, as i assume some of the expression's variable that are being set on the backend are failing to be recognized properly, thus messing up the expression which causes a blank result.
Currently, after running this back end program, it reloads a form that has a field which is tied to that app variable (This field is also marked as required.) So after running the program the field goes from having the "This field is required" warning to having a value of, say, 100. This is all working perfectly fine on desktop, but on mobile, after running the program, the field goes from "This field is required" to saying "Value is not a valid number" which is leading me to believe that something on mobile is failing to recognize the app variable as numerical.
This would also align with a separate issue I've been having where an app variable that is an expression of other app variables is failing to show any result on my form on mobile, as i assume some of the expression's variable that are being set on the backend are failing to be recognized properly, thus messing up the expression which causes a blank result.
Comment