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.
in our WF 5.x the drill down feature of a report stops working if the field involved has a full quote (") in it. Also, if there are 2 apostrophes (').
obvious workaround is to remove the bad characters using STRIP function in the master file, however, I have 2 concerns:
(1) can I do STRIP(STRIP(....))? (2) what other symbols might trigger this problem?
I will start my own experimentation on these, but if anyone has additional comments and/or insights, please share.
Furthermore, is there a solution that will work within the fex directly? The field involved is only referenced in the "Report_Hierarchy:" statement, so I am thinking I can only fix it in Master File.
Finally, is this still a problem in 7.x ?
thanks
RichardThis message has been edited. Last edited by: Kerry,
MTO WebFOCUS Dev Studio 5.3.2 (trying to upgrade to 7.x !) Unix with Win XP front ends output usually PDF (and some HTML and XLS at times)
it doesn't go in the master files. it is appended to the variable (&VAR.QUOTEDSTRING) to indicate special handling of the string. From the manual:
The QUOTEDSTRING suffix on a Dialogue Manager variable applies the following two conversions to the contents of the variable:
Any single quotation mark embedded within a string is converted to two single quotation marks.
Single quotation marks are added around the string.
Dialogue Manager commands differ in their ability to handle character strings that are not enclosed in single quotation marks and contain embedded blanks. An explicit or implied -PROMPT command can read such a string. The entire input string is then enclosed in single quotation marks when operated on by .QUOTEDSTRING.
Note: When using the -SET command to reference a character string, ensure the character string is enclosed in single quotes to prevent errors.
Regards,
Darin
In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007
QUOTEDSTRING is not a solution to Richards problem.
The issue he is having is in passing a column via his drilldown, not a variable and it is the parser in the WebFocus server that is breaking on these values.
Quoted string only applies when working with DM variables. Additionally QUOTEDSTRING does not handle double quotes, which are also causing a problem, at all.
Expect to learn a lot of things you may not be able to use, as training is always based on current release.
As a side note 5.3 is due to be functionally stabalized in Q1 2009 and while this does not mean that you will not get support from hottrack it does mean that no patches of fixes will be made available.
I'm not sure if you are still having issues with those special characters or not. However what we have done here is use the CTRAN function to convert those special characters from one decimal representation to another. For example we changes the apostrophe {') to a graves (`) symbol.
Hope this helps
Prod: WebFOCUS 7.6.10 MRE Oracle/Sybase Test: DevStudio 7.6.6 WF Server 7.6.6 Report Caster 7.6.6 Web Server - Tomcat MS Windows XP SP2 Output: HTML, Excel 2000 , PDF, CSV, DOC
I've just run into this problem with a report that I have. I'm running 7702. Ampersands do not seem to be a problem, but when my field contains an apostrophe the drill down will not work. I've tried converting the field using CTRAN, as the previous poster suggested, but I have not yet been able to solve the problem.
Colleen
WebFocus 8104, IBMi (server), Windows 7 (client), iWay 6.1
What's the nature of the failure in the called fex?
Let me guess.
Let's suppose the drilldown is on LNAME, with a value of "O'Hara". The fex issuing the drilldown converts apostrophe to (say) circumflex, so it passes parameter &LNAME with a value of "O^Hara".
The fex receiving this value has to take two measures in order to fish out the O'Hara records --
1. Use CTRAN to convert it back to the original value ("O'Hara").
2. In the report code, use .QUOTEDSTRING, to 'escape' the apostrophe in the value of &LNAME:
WHERE ( LNAME EQ &LNAME.QUOTEDSTRING );
Without #1, no matches Without #2, syntax errorThis message has been edited. Last edited by: j.gross,
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005