I am trying to find mismatches when comparing two fields. The [TO_iM_StaticPressureCFM] is numeric field while the [TO_CalculatedCFM] field is a formula  numeric field. The below script is not working correctly. I guess I am not using the "<>" correctly.
If([Customer  Related Client]=3 and [AirFlowMethodID]=2 and [TO_iM_StaticPressureCFM]<>[TO_CalculatedCFM],"Does not match"&"\n")&
Thanks
If([Customer  Related Client]=3 and [AirFlowMethodID]=2 and [TO_iM_StaticPressureCFM]<>[TO_CalculatedCFM],"Does not match"&"\n")&
Thanks
 394 Points
Posted 9 months ago
Chris, Champion
 4,390 Points
Evan Martinez, Community Manager
 9,690 Points
HI Stephen,
When that formula is not working correctly are you getting a specific error message back when trying to save or are you getting a wrong output?
When that formula is not working correctly are you getting a specific error message back when trying to save or are you getting a wrong output?
Evan Martinez, Community Manager
 9,690 Points
What type of fields are [TO_iM_StaticPressureCFM] and [TO_CalculatedCFM]
 394 Points
[TO_iM_StaticPressureCFM] is a numeric field and [TO_CalculatedCFM] is a formula  numeric field.
Evan Martinez, Community Manager
 9,690 Points
Hi Stephen,
Does that formula numeric use any rounding? If you go into that field and set the decimal place to 14 do you see any trailing decimal points for that calculation? Sometimes due to rounding numbers can appear the same but are stored as different, essentially one might be 2.5 and the other might be 2.50000134 and that 134 is still logged by the formula but not displayed due to the field settings. Expanding the decimal place manually can help to assure that isn't happening and causing inconsistent results.
Does that formula numeric use any rounding? If you go into that field and set the decimal place to 14 do you see any trailing decimal points for that calculation? Sometimes due to rounding numbers can appear the same but are stored as different, essentially one might be 2.5 and the other might be 2.50000134 and that 134 is still logged by the formula but not displayed due to the field settings. Expanding the decimal place manually can help to assure that isn't happening and causing inconsistent results.
 394 Points
Evan,
Thanks for the information and I was able to prove your theory. I did not see everything after the decimal point because of the field settings.
Thanks.
Thanks for the information and I was able to prove your theory. I did not see everything after the decimal point because of the field settings.
Thanks.
Evan Martinez, Community Manager
 9,690 Points
Hi Stephen,
I am glad I was able to help. I have ran into that myself a number of times with numeric formulas, Quick Base at times will hide those small decimal places and it can be confusing to figure out where the mismatch is. If you are looking to still use the comparison for your formula you can apply a rounding to your formula field via the Round function to force it to round the results to the decimal place you would like. Thank you and have a great day!
I am glad I was able to help. I have ran into that myself a number of times with numeric formulas, Quick Base at times will hide those small decimal places and it can be confusing to figure out where the mismatch is. If you are looking to still use the comparison for your formula you can apply a rounding to your formula field via the Round function to force it to round the results to the decimal place you would like. Thank you and have a great day!
(Edited)
Related Categories

Formulas & functions
 2788 Conversations
 64 Followers