Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [Case opened] MISSING being interpreted literally by SQL

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[Case opened] MISSING being interpreted literally by SQL
 Login/Join
 
RyanIPG13
Silver Member
posted
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?


Production: WebFOCUS 8.202M
QA: WebFOCUS 8.206.01
Windows/SQL
 
Posts: 37 | Registered: May 24, 2017Report This Post
MartinY
Virtuoso
posted Hide Post
Do you have your drop down setting "Send Display Value" checked (to true) ?


WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF
In Focus since 2007
 
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013Report This Post
RyanIPG13
Silver Member
posted Hide Post
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.


Production: WebFOCUS 8.202M
QA: WebFOCUS 8.206.01
Windows/SQL
 
Posts: 37 | Registered: May 24, 2017Report This Post
RyanIPG13
Silver Member
posted Hide Post
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.


Production: WebFOCUS 8.202M
QA: WebFOCUS 8.206.01
Windows/SQL
 
Posts: 37 | Registered: May 24, 2017Report This Post
Waz
Expert
posted Hide Post
Is MISSING being passed to the fex with quotes ?


Waz...

Prod:WebFOCUS 7.6.10/8.1.04Upgrade:WebFOCUS 8.2.07OS:LinuxOutputs:HTML, PDF, Excel, PPT
In Focus since 1984
Pity the lost knowledge of an old programmer!

 
Posts: 6347 | Location: 33°49'23.0"S, 151°11'41.0"E | Registered: October 31, 2006Report This Post
RyanIPG13
Silver Member
posted Hide Post
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.


Production: WebFOCUS 8.202M
QA: WebFOCUS 8.206.01
Windows/SQL
 
Posts: 37 | Registered: May 24, 2017Report This Post
Waz
Expert
posted Hide Post
Certainly sounds like bug.

Good luck with the case


Waz...

Prod:WebFOCUS 7.6.10/8.1.04Upgrade:WebFOCUS 8.2.07OS:LinuxOutputs:HTML, PDF, Excel, PPT
In Focus since 1984
Pity the lost knowledge of an old programmer!

 
Posts: 6347 | Location: 33°49'23.0"S, 151°11'41.0"E | Registered: October 31, 2006Report This Post
Mike in DeLand
Guru
posted Hide Post
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;


Webfocus 8
Windows, Linux
 
Posts: 258 | Location: Palm Coast, FL | Registered: February 05, 2010Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [Case opened] MISSING being interpreted literally by SQL

Copyright © 1996-2020 Information Builders