You are viewing limited content. For full access, please sign in.



Field lookup with double quotes in input value

asked on December 6, 2017 Show version history

We have a form with multiple lookup rules that accept user input from text fields.  They behave as expected until the input value contains double quotes.  More confusing to us is that the field lookup will return a value if there is only one set of double quotes.

User input of ' The "Th ' will return both ' The "Thing" About That' and ' The "Theory" of Constraints ', but if a user submits ' The "Thing" ', the filed lookup returns no values.

We're using stored procedures as the data source.  The stored procedures execute as expected for all of these example values when executed in SQL Server Management Studio.  It looks like Forms is doing something unanticipated when it hits the second double quote in the string.

Has anyone else encountered this?  Do you have a solution?

0 0


replied on December 6, 2017

I didn't realise this was a thing. I've tested what you described and I have the same issue. Forms doesn't even attempt the lookup if there are 2 double quote characters present.

A bit of research turned up this:

Specifically this line:

  • Forms lookup data will now successfully download locally when data includes quotation marks. (155913)

So basically to fix this you need to update to 10.2.1

Hope that helps.

0 0
replied on December 7, 2017


Thanks for validating that we're not alone in this.

We're on Forms already, so at least for us the problem still exists at that rev.

If you run across anything else that might be helpful, please pass it along.  If we find a solutions, I'll update the thread.

Thanks again.

0 0
replied on December 11, 2017

Hi Brian,

I tried the same input on 10.2.1 but the behavior is like this:

1. when input ' The "Th ' the lookup rule works as expected. In your case it would return two values, is this expected or not? How does your stored procedure work? Is this is not expected, can you try if it behaves the same when lookup uses database table instead of stored procedure?

2. when input The ' The "Thing" ' there is js error and lookup could not work at all. This is a bug and should be fixed in next release. Sorry for the inconvenience.

0 0
replied on December 12, 2017


You are correct.  In the first example, the stored procedure returns two values.  We use that to populate a drop down.  This way the user can do a partial text match of a descriptive field, and we can still force them to select from a matching set of returned values.

We'll wait for the next release.


0 0
replied on April 3 Show version history

This issue that Lookup doesn't work when lookup rule match value contains more than one double quote has been fixed at Forms 10.3.1, and you can download newest package at

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.