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     [SOLVED] Trouble with NULLs in drilldowns

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] Trouble with NULLs in drilldowns
 Login/Join
 
Virtuoso
posted
We have a bit of pass-thru SQL that can contain NULLs for a field that is used in a drilldown. In the drilldown the field value is converted to a space ('%20'). We don't want that happening.

Is there a setting or something that changes that behaviour such that the field is either left out or contains FOC_NONE?

I can duplicate the issue with this simple bit of code:
SQL ORA PREPARE SQLOUT FOR
SELECT NULL AS value FROM dual;
END

TABLE FILE SQLOUT
PRINT VALUE
ON TABLE SET STYLE *
$
TYPE=DATA, COLUMN=VALUE, FOCEXEC=DRILLDOWN(VALUE=VALUE),$
ENDSTYLE
END


I realise there are several ways to work around the problem, but I'd rather have WebFOCUS do the right thing. After all, a single space might be a valid value different from NULL in the database. I consider what WF does here to be incorrect behaviour.

This message has been edited. Last edited by: <Kathryn Henning>,


WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010
: Member of User Group Benelux :
 
Posts: 1669 | Location: Enschede, Netherlands | Registered: August 12, 2010Report This Post
Guru
posted Hide Post
Try this code

SQL ORA PREPARE SQLOUT FOR
SELECT NULL AS value FROM dual;
END

TABLE FILE SQLOUT
PRINT VALUE
ON TABLE SET STYLE *
$
TYPE=DATA,
WHEN=VALUE NE '',
COLUMN=VALUE, FOCEXEC=DRILLDOWN(VALUE=VALUE),$
ENDSTYLE
END
/>


WF 7.6.11
Oracle
WebSphere
Windows NT-5.2 x86 32bit
 
Posts: 398 | Registered: February 04, 2008Report This Post
Virtuoso
posted Hide Post
I could do that, but that doubles the number of drilldown definitions I have to write; I would need a FOCEXEC+WHEN for both NULL and NOT NULL.

That may seem odd, as drilling down on an empty value is not normally useful. However, in this repro the value drilled down from is only empty because I intentionally kept it simple.

Perhaps a better example would be:
SQL ORA PREPARE SQLOUT FOR
SELECT 'foo' AS foo, NULL AS value FROM dual;
END

TABLE FILE SQLOUT
PRINT FOO VALUE NOPRINT
ON TABLE SET STYLE *
$
TYPE=DATA, COLUMN=FOO, FOCEXEC=DRILLDOWN(FOO=FOO VALUE=VALUE),$
ENDSTYLE
END


In my actual report, I have nearly 30 drilldowns that suffer from this issue. I'd rather not have to double that number.


WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010
: Member of User Group Benelux :
 
Posts: 1669 | Location: Enschede, Netherlands | Registered: August 12, 2010Report This Post
Expert
posted Hide Post
A shot in the dark but might be a possibility, use COALESCE?

select coalesce(FIELD,'FOC_NONE') ....

I've not got access to Oracle at the moment so can't check it out.

T



In FOCUS
since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2  
WebFOCUS App Studio 8.2.06 standalone on Windows 10 
 
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004Report This Post
Virtuoso
posted Hide Post
Yeah, I thought of that too, but somehow that FOC_NONE value didn't seem to make it through to the drilldown - it was still passed as an empty string.

Perhaps I should try that again, I couldn't explain that behaviour so perhaps something else was going wrong there. If I substitute the NULL in my above example with 'FOC_NONE' it does get passed on as the correct drilldown parameter value... That's something to look into tomorrow - we're near the end of the working day here.


WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010
: Member of User Group Benelux :
 
Posts: 1669 | Location: Enschede, Netherlands | Registered: August 12, 2010Report This Post
Expert
posted Hide Post
Try using _FOC_NULL instead?

T



In FOCUS
since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2  
WebFOCUS App Studio 8.2.06 standalone on Windows 10 
 
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004Report This Post
Virtuoso
posted Hide Post
I found why FOC_NONE (or _FOC_NULL for that matter) didn't get passed along - if you add MAX.FIELD into the internal matrix, make sure you also pass MAX.FIELD to the drilldown parameter list instead of just FIELD.

So COALESCE saved the day once again. Thanks.


WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010
: Member of User Group Benelux :
 
Posts: 1669 | Location: Enschede, Netherlands | Registered: August 12, 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     [SOLVED] Trouble with NULLs in drilldowns

Copyright © 1996-2020 Information Builders