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     [CLOSED] Settting up Joins in InfoAssist

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED] Settting up Joins in InfoAssist
 Login/Join
 
DWaybright
Platinum Member
posted
I know Joins have been a topic of discussion on the Forum (I've read most of the posts), but I haven't seen anything that addresses how to set up a join in InfoAssist. Specifically, what are the things to consider when choosing between Single or Multiple Instances?
I recently worked on a report that joined two tables to the main table and thought multiple was the way to go because there could be multiple records that matched back to the main table, but that gave incorrect results. I had to use Single on both to get the correct results, but I don't understand why.

Thanks in advance for help in understanding this!
--Deb

This message has been edited. Last edited by: FP Mod Chuck,


WebFOCUS 8.2.03 (production), 8.2.06 (testing)
AppStudio, InfoAssist
Windows, All Outputs
 
Posts: 183 | Location: Indiana | Registered: December 05, 2017Report This Post
BabakNYC
Virtuoso
posted Hide Post
What's the data source of the tables involved? Are they all relational and in the same DBMS or are you joining HOLD files?


WebFOCUS 8206, Unix, Windows
 
Posts: 1853 | Location: New York City | Registered: December 30, 2015Report This Post
FP Mod Chuck
Virtuoso
posted Hide Post
Deb

This has always made me a little crazy and I heard the explanation once but can't recite it back.. 99 times out of a 100 a single or unique join will do what you want. To prevent users from doing the wrong thing because (and this is the part that makes me crazy) the default is to do the multiple join you can create a Reporting Object that has the join pre-defined or you can create a cluster join in the metadata itself and let them use that..


Thank you for using Focal Point!

Chuck Wolff - Focal Point Moderator
WebFOCUS 7x and 8x, Windows, Linux All output Formats
 
Posts: 2127 | Location: Customer Support | Registered: April 12, 2005Report This Post
DWaybright
Platinum Member
posted Hide Post
The tables are all relational and in the same DBMS.

The issue with creating a Reporting Object is that my BAs keep creating new joins! I'd have to anticipate what they'll come up with next. Plus, I'm holding off on creating Reporting Objects until we upgrade to 8.2 later this year. We're still on 8.1.05M.

Sounds like what I am hearing is, try it until you get what you're looking for. Not exactly what I was hoping for!
Razzer


WebFOCUS 8.2.03 (production), 8.2.06 (testing)
AppStudio, InfoAssist
Windows, All Outputs
 
Posts: 183 | Location: Indiana | Registered: December 05, 2017Report This Post
FP Mod Chuck
Virtuoso
posted Hide Post
Deb

I think the single join will work 99% of the time so steer them in that direction.


Thank you for using Focal Point!

Chuck Wolff - Focal Point Moderator
WebFOCUS 7x and 8x, Windows, Linux All output Formats
 
Posts: 2127 | Location: Customer Support | Registered: April 12, 2005Report This Post
DWaybright
Platinum Member
posted Hide Post
Chuck,
Thanks for all the info. I will indeed steer them in that direction.

--Deb


WebFOCUS 8.2.03 (production), 8.2.06 (testing)
AppStudio, InfoAssist
Windows, All Outputs
 
Posts: 183 | Location: Indiana | Registered: December 05, 2017Report This Post
Tony A
Expert
posted Hide Post
Hi Deb,

A couple of suggestions so that your users do not have this issue would be -
  • Cluster Joins
  • Reporting Objects

Either of these might suit your Company and the way that they wish to work.

One advantage from the end users point of view is that they do not have to worry about the structure and the joins because they would already have been analysed and set within either solution.

If you need assistance with understanding or implementing either or both of these (plus business views of course), check with your local IB team for their Professional Services team.

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
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CLOSED] Settting up Joins in InfoAssist

Copyright © 1996-2020 Information Builders