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.
Hi there, I am trying to understand the following syntax since it's returning a 'DUPLICATES IN JOIN 'FROM' FIELD : TEK_HOLD_PPL_PROMO_DETAILS_FULL_LIST' error.
Here is the syntax.
quote:
JOIN CLEAR * JOIN LEFT_OUTER TEK_HOLD_PPL_HIRES_AND_PROMOS_OFFICE_LIST.TEK_HOLD.JOIN_KEY IN TEK_HOLD_PPL_HIRES_AND_PROMOS_OFFICE_LIST TO MULTIPLE TEK_HOLD_PPL_PROMO_DETAILS_FULL_LIST.TEK_HOLD.JOIN_KEY IN TEK_HOLD_PPL_PROMO_DETAILS_FULL_LIST TAG J30 AS J30 END
This is an error from a Report Caster job. Thank you.solved]This message has been edited. Last edited by: Tamra,
Thanks for the information. How can I implement a join in a 1 to many relationship?
TEK_HOLD_PPL_HIRES_AND_PROMOS_OFFICE_LIST contains the unique key while TEK_HOLD_PPL_PROMO_DETAILS_FULL_LIST contains multiple records with the same "key".
Judging from the message you encountered, it looks like your two "_LIST" files are flat files, and the TABLE request encountered duplicate JOIN_KEY values in the join-from file.
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
How are you storing your data? is it in a non-focus relational database? If so then just declare it a unique join and make sure that the adapter is translating the sql properly. As long as its an RDBMS managed join and not a FOCUS managed join, your golden. Unique/Multiple only have real meaning when dealing with FOCUS data sources. These are not RDBMS concepts, but for WF will apply the same check logic either or. Unique has less of these issues.
Eric Woerle 8.1.05M Gen 913- Reporting Server Unix 8.1.05 Client Unix Oracle 11.2.0.2
Posts: 750 | Location: Warrenville, IL | Registered: January 08, 2013