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.
We have some reports that utilize a certain piece of data X, among others.
We also have users that need to see these reports, but we also have another set of users that need to see these reports but without field X (or any DEFINEs or COMPUTEs using field X).
Do I need to re-create a new version of the reports without field X, or is there some kind of way to lock down field X so that only the correct users can see it?
Thanks!This message has been edited. Last edited by: <Emily McAllister>,
There's several ways to slice and dice this one Dusty.
Questions to answer: Where are you running these reports from? A BI portal, dashboard, stand-alone? Are these reports being distributed via ReportCaster? If so, you can build two versions of the report and only distribute the right version to the right distribution lists.
You can dynamically populate your TABLE FILE xxx request with the proper fields utilizing GOTO and labels within your fex based on whoever is running the report (utilizing the &IBIMR_user value to figure that out).
Are these users only allowed to run these reports and not edit them (have access to underlying code?)?
Many ifs to clear up.
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015
if you can identify your user, when s/he logs in, and determine which group s/he belongs to, then use a comment inside your single fex to turn off or on the display of a certain field. lets say you know your user's membership in a group called 'admin'; -SET &cmt_model=IF &USER_GROUP IS 'ADMIN' THEN ' ' ELSE '-*'; TABLE FILE CAR SUM SALES BY COUNTRY BY CAR &cmt_model.EVAL BY MODEL END .. get the idea? If the user is an admin, then the report is SALES BY COUNTRY BY CAR BY MODEL If not , then the report is just SALES BY COUNTRY BY CAR
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
Take a look at DBA security. It allows you to mask out a field for certain users or groups, so any report with that field in it will just show blanks or zeros or nulls, but not the data itself.