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] Error in while creating report from Reporting object

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] Error in while creating report from Reporting object
 Login/Join
 
Rao Casturi
Member
posted
Hi This is the error I get when I create a report via the Reporting object I created.
The reporting object runs fine and gives me no error.
When I create a report with specific fields I get this error. for other fields I can run/create reports via the reporting object without any issue.
Any help?
Thanks,
Rao


(FOC029) ALL SORT KEYS ARE NOT IN A SINGLE TOP-TO-BOTTOM SEGMENT PATH

This message has been edited. Last edited by: Kerry,
 
Posts: 14 | Registered: April 18, 2007Report This Post
N.Selph
Guru
posted Hide Post
WebFocus only uses fields/tables in a query if they are referenced or implied by fields that are referenced. Your Reporting Object can have multiple one-to-many paths in it without a problem, as long as you don't use items from more than one of the paths per report. The query with problems must have BY fields from more than one of these paths.
In my opinion, you should design your Reporting Objects without multiple one-to-many paths in it. This type of issue is one that you can't usually expect your users to understand. Avoiding these issues is a major strength of setting up the joins for the users in Reporting Objects or Embedded joins.


(Prod: WebFOCUS 7.7.03: Win 2008 & AIX hub/Servlet Mode; sub: AS/400 JDE; mostly Self Serve; DBs: Oracle, JDE, SQLServer; various output formats)
 
Posts: 391 | Location: California | Registered: April 14, 2003Report This Post
Rao Casturi
Member
posted Hide Post
Thanks a lot. I will try to redesign the reporting object. The tables are well designed Relational tables.
Thank,
Rao
 
Posts: 14 | Registered: April 18, 2007Report 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] Error in while creating report from Reporting object

Copyright © 1996-2020 Information Builders