I am attempting to write a basic multiplication formula for a table and I keep getting the error below. Should I be using the "MULT" function instead? Thanks!
Question
Question
Answer
A message about invalid variables means the names do not match up with the actual variable names used in your form.
In your screenshot, I noticed the table variable is actually "variable" so if you want your function to work, you either need to change the variable to be "Costs" or you would need the function to use "variable." instead of "Costs."
As Jared mentioned, changing field types will create new variable names as well, so while your editing the table variable, you should cleanup the old variables and rename the new ones to remove any "_1" that may have been added to the name.
Just be sure to look at the type icon on the left to make sure you're removing or renaming the correct ones.
Replies
Can you try setting costs and quantity to Number type fields (or a currency type field)? You could also try the MULT function.
I just noticed my screenshot of the field was old. I have updated the Quantity and Unit Price fields to be number/currency fields. Still getting the error message of having a invalid variable in the formula.
When you updated the field types, it created new variables. Maybe the variables are now quantity_1 or something like that?
A message about invalid variables means the names do not match up with the actual variable names used in your form.
In your screenshot, I noticed the table variable is actually "variable" so if you want your function to work, you either need to change the variable to be "Costs" or you would need the function to use "variable." instead of "Costs."
As Jared mentioned, changing field types will create new variable names as well, so while your editing the table variable, you should cleanup the old variables and rename the new ones to remove any "_1" that may have been added to the name.
Just be sure to look at the type icon on the left to make sure you're removing or renaming the correct ones.
Thank you Jason. Didn't catch that previously. Fixed the issue