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     Help needed with this error

Read-Only Read-Only Topic
Go
Search
Notify
Tools
Help needed with this error
 Login/Join
 
<Kalyan>
posted
Hi,
I am getting a error message like
" All sort keys are not in a single top to bottom segment path"

Let me explain more..
I am preparing a dynamic report wherein a person can slelect columns at random from a given list and generate a report based on some where criteria.When I select one of these columns and try to generate the report I get this error. Also This is the only column that can be selected from that paricular table..

Any idea why this is happening?

Thanks.
 
Report This Post
Noreen Redden
Gold member
posted Hide Post
The reason is because of the relationships that have been developed previously, particularly the Sort Criteria. (BY fields). Let's say that you have a host (root) record that contains an employee id, last name, first name, and some other 1-1 information . Now either through JOIN TO ALL, you have connected that employee with his/her education information. Another JOIN TO ALL connects the employee up with JOB HISTORY. Now, the way you have built those JOINS implies that education and job history have nothing to do with each other. Therefore, you cannot PRINT JOBINFO BY EMPLOYEE BY EDUCATION as you have said they are unrelated. That is the meaning of the error message. The alternatives are only to use BY fields that are common to all of the paths, in my example, fields from the root segment, or fields that are in a 1-1 relationship with that root (where you did a JOIN TO, not JOIN TO ALL.
 
Posts: 60 | Location: 2 penn | Registered: May 22, 2003Report This Post
Leah
Virtuoso
posted Hide Post
If the files are of such a relationship that you can create a vertical join structure as I call it, you can avoid the message.

I call a horizontal join something like as follows:

JOIN KEY IN A TO KEY (OR ALL KEY) IN B AS J1
JOIN KEY IN A TO KEY (OR ALL KEY) IN C AS J2

A vertical join:

JOIN KEY IN IN A TO KEY IN B AS J1
JOIN B.KEY IN A TO KEY IN C AS J2

This only works if B has a key for every key in A. C could be missing which is 'short path' and I use SET ALL ON for those if you want data to show whether C info is present or not.
 
Posts: 1317 | Location: Council Bluffs, IA | Registered: May 24, 2004Report 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     Help needed with this error

Copyright © 1996-2020 Information Builders