Forms Personalization fails when field being validated contains non-ascii character

We have a forms personalization on a standard Oracle form that checks for a combination of values in 2 fields and should throw an error if this scenario exists:

${item.rgw_folder.m_customer_number.value} IS NOT NULL AND ${item.rgw_folder.m_location.value} IS NULL

The location field pulls from the Oracle Customer Location field, which is VARCHAR2 and sometimes we have found non-ascii values in this field.  An example that we just found is that the location field contained an acute accent (´) in place of an apostrophe.

When this FP triggers and evaluates this value in the m_location, it throws an error (The condition <...> could not be evaluated because of error).