Opened a case with support, but wanted to ask if anyone had a similar issue.

We are running 8.206.01 in QA and we have missing on for a particular field in the metadata.

We are using autoprompt to pull in values on a page which we can multiselect. one of the possible values is "MISSING" since we can have nulls in the data.

When i look at the debugger, it looks like the sql is being written like this:

in 8202M:

((T1."MyField" IS NULL) OR (T1."MyField" = 'Value1'))


in 8206.01:

T1."MyField" IN('Value1', 'MISSING'))

It looks like the dropdown is passing the shown value, not the actual value of the missing item which would be NULL.

Anyone run into this?

Do you have your drop down setting "Send Display Value" checked (to true) ?

Hi Martin,

We're using a fex that was dropped onto the Page Designer, not the HTML Canvas.

The dropdown is populated using the page controls through the autoprompt in the fex.

I did find that the SQL statement does process properly if we ONLY used the MISSING choice in the dropdown. If we multiselect MISSING and something else, it processes it as I originally mentioned.

Is MISSING being passed to the fex with quotes ?

Waz,

Nope, it's being passed properly to the fex as '_FOC_MISSING'.

The SQL that it sends off to the database is being passed as 'MISSING' in quotes. So it's like the SQL is being written wrong by WebFOCUS, however the FEX is interpreting it properly.

This is the WHERE condition of the fex:

WHERE MyField EQ 'Value1' OR '_FOC_MISSING';


This is the SQL it writes:

(T1."MyField" IN('Value1', 'MISSING'))


It's like it can't translate _FOC_MISSING to a NULL on the SQL translation side of things. Because it's translating it literally as 'MISSING' it also puts it in an "IN" SQL clause instead of breaking out into an "OR" like it does in 8202M.

Certainly sounds like bug.

Good luck with the case

What if you wrote the webfocus WHERE in 2 whole phrases

WHERE myfield EQ 'value' OR myfield EQ _FOC_NULL;

or perhaps

WHERE myfield EQ 'value' OR myfield IS MISSING;