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]Bursting with mixed case sort values

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED]Bursting with mixed case sort values
 Login/Join
 
Gold member
posted
We are experiencing some issues with bursting compound PDF reports. If the primary sort field value for which we are bursting contain mixed case letters, we are either getting Adobe errors or data mixup among reports. It doesn't happen for all sort values with mixed case which makes it hard to debug. But, if we convert sort values to uppercase, it seems to fix the problem. Has anyone experienced this problem before? We are trying to avoid converting the sort values to uppercase if possible because we use it for display purpose also and there are 100+ reports that gets affected by this change.
Thanks for the help.

This message has been edited. Last edited by: CT,


7.6.9, XP
 
Posts: 60 | Location: Cary, NC | Registered: February 19, 2008Report This Post
Guru
posted Hide Post
This could be caused by the fact that in the ASCII collating sequence upper case and lower case letters are not in sequence, Therefor Aa dose not follow or precede AA but comes after AZ.


WF 7.6.11
Oracle
WebSphere
Windows NT-5.2 x86 32bit
 
Posts: 398 | Registered: February 04, 2008Report This Post
Gold member
posted Hide Post
Thanks. It makes sense. Is there a setting in WebFocus reporting server or somewhere to ignore the case when sorting?
Thanks for the help.


7.6.9, XP
 
Posts: 60 | Location: Cary, NC | Registered: February 19, 2008Report This Post
Virtuoso
posted Hide Post
Two approaches to try:

#1. use
TABLE ...
BY myUpperCaseValue NOPRINT
BY mixedCaseValue
-- where myUpperCaseValue is either predefined in the data source table, or DEFINEd using UPCASE() function


#2. perhaps you can hold in desired order (using #1), and then
TABLEF ...
BY mixedCaseValue

- TABLEF will break whenever the sort-key value changes, regardless of direction of the change -- but I'm not sure that Reportcaster bursting will work with TABLEF.
 
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005Report This Post
Gold member
posted Hide Post
Thanks j.gross and RSquared.
Your responses gave me some clues on what to look for. We are able to find a setting which solved our problem.

COLLATION = enabling keyword
Internal default: CODEPAGE
Establish Binary or Case-Insensitive Collation Sequence. The keyword values are:

CODEPAGE Bases collation sequence on the code page in effect
BINARY Bases the collation sequence on binary values
SRV_CS Bases collation sequence on the LANGUAGE setting, and is case-sensitive
SRV_CI Bases collation sequence on the LANGUAGE setting, and is case-insensitive

We changed this setting from SRV_CI to SRV_CS which fixed our problem
I think when report castor bursts reports, they are in ASCII collating sequence, so the setting SRV_Cl made them out of order with the BY field values in the report.


7.6.9, XP
 
Posts: 60 | Location: Cary, NC | Registered: February 19, 2008Report 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]Bursting with mixed case sort values

Copyright © 1996-2020 Information Builders