« Return to TrackVia.com
TrackVia
Home » Knowledge Base » Formulas » Working with formulas » Troubleshooting formula errors

Troubleshooting formula errors

Submitted by admin on Fri, 01/07/2011 - 13:15
Errors when working with formulas Likely cause ("C:") and possible solution ("S:")
Error msg given ...Syntax error C: Most likely you didn't properly open/close the parentheses used in your functions.  There must be the same number of open and close parentheses.


S: Count the open and close parentheses to make sure there's the same number. If you're using a series of "nested" functions it can be a challenge to get this right. One option is to sequentially build your formula by adding one function at a time (which might require temporarily adding calculated fields of different types, which you'll subsequently delete after you get the final filter built). Add a function, click save, ensure you're seeing the expected result in fields, then add the next function.
...Unrecognized words or symbols C: Most likely you forgot to use quotes, or forgot a single open quote or close quote.


S: For each parameter that's entered (such as these constant values: "High Priority", "2010-12-08", "31") make sure it has an open quote and close quote.
...Wrong number of inputs

C: Too many or too few parameters were entered for a function(s) in the formula.


S: Refer to the structure of the function(s) used in your formula (click here for all functions) and correct any errors.
"Oops..." (Internal Server Error) C: One of the other errors listed here has occurred, but for some reason you're seeing a server error page instead of a standard error message.


S: Hit back in the browser and correct the error in your formula (unfortunately you'll just have to figure it out without the benefit of a specific error message).
...Not a field in this/that table

C: This error occurs in lookup functions (child or parent).  The good news is you've used quotes around your field name, which is required in lookup functions.  The bad news is you've used a word or phrase that doesn't match any of the fields in the parent or child table.


S: Open a new window and navigate to the Schema page of the parent or child table.  Confirm the proper field name and correct your formula.
Note: Remember that child lookup functions need the name of the link to parent field name in the child table, not that field's name in the parent table.  Using copy & paste to input field and table names is always a good idea!
...[Function] must have [x] number of field names in quotation marks as inputs C: This error occurs in lookup functions (child or parent). Most likely, you didn't use quotes around field name(s) in your lookup function(s). Second most likely, you didn't include all of the field names required in a function (some require 2, others require 3).


S: First, check that you've put open and close quotes around each field name in each lookup function. Next, check that you've included the correct number of field names in each function (not too few, not too many).
...[Function] must have a table name... C:  This error occurs in child lookup functions that require a table name as a parameter.  Like field names in lookup functions, the table names in functions must be inside quotes.


S: Ensure that you've put quotes around the table name in any child lookup function(s).  Next, ensure that you've used the correct table name.
No error msg Value is blank when you'd expect to see a value C: Assuming you're correct that there should be a value displayed, then the most likely cause is that you've chosen the wrong type of calculated field. I.E, a fully correct formula will display a blank value if it's a value that can't be displayed by that field type.  A calculated number field can't display a word, so it'll display a blank.


S: Check your type of calculated field against the type of value the formula will return.  It can be very helpful to open a single record and look in the change notes (at the bottom of the record detail page).  There will be a change note related to the formula you've applied and it may help you deduce the problem.
Unexpected result C: Parameters included inside functions and formulas are CASE SENSITIVE!  (Field names aren't, though.)   For example, an "isselected" function that references a drop-down field won't match "high priority" to "High Priority" and it won't return an error message.


S: Double-check that you've used the appropriate capitalization to match the values you want to match in your records. Unexpected result
Unexpected result C: You may not have correctly implemented the logic in your formula. (This can be tricky to do in "nested" IF, OR, AND functions, for example.) Your open/close parentheses may be off, meaning you have the correct number but they're not in the correct places. Another way of saying this is that your formula may not properly reflect the way mathematical operations are prioritized in equations (i.e. formulas). For example, multiplication occurs before addition.



S: This is one of the trickier errors to correct in a complex formula.  The best solution is to build your formula sequentially, making sure that each new function or operation added is correct before adding the next one.