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.
I have a view that I built in Oracle, from about 6 tables. I then created a WebFocus MFD from that view. Now I'm trying to apply DBA security to certain values of a field, and it's not working. It completely ignores the restrictions. I'm not doing pass-thru or anything like that. I have verified that if I put a similar restriction on a regular table it works ok. Is this because my MFD is based on a database view and not a plain table? The field I want to restrict is a field that gets created when the view runs. Thanks.
Duh... I found the documentation on SET DBASOURCE=ALL. Added that to my edasprof and everything works great.This message has been edited. Last edited by: Mike in DeLand,