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] Anybody Using Business Views?

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED] Anybody Using Business Views?
 Login/Join
 
Guru
posted
Anybody out there using Business Views? I'm having a challenge in that changing the FIELDNAME property causes problems when creating parameters in reports.

When I go to the Variable Editor and select the Values for Field radio button in the Data Context area I can select the field based on the new name I created in the Business View but it does not return any values.

In the Object Inspector the Qualified Name of the field looks correct and the Alias references the original field name in the Synonym that the Business View is baed on.

I do have SET FOCTRANSFORM=ON set in the server profile.

Am I missing something or could this be a bug?

We are running v7.6.2

This message has been edited. Last edited by: Kerry,


7.7.05M/7.7.03 HF6 on Windows Server 2003 SP2 output to whatever is required.
 
Posts: 393 | Location: St. Paul, MN | Registered: November 06, 2007Report This Post
Expert
posted Hide Post
Hi Dan,

Do you have an updated status regarding this issue?

The suggestion for this issue would be similar to the other topic you have regarding DBA: the best channel for assistance would be your local SE's (you may want to contact your local branch) and/or education. The issue will involve a lot more details than providing simple information/directions.

Hope this helps. Smiler

Cheers,

Kerry


Kerry Zhan
Focal Point Moderator
Information Builders, Inc.
 
Posts: 1948 | Location: New York | Registered: November 16, 2004Report This Post
Platinum Member
posted Hide Post
It is a bug ... contact tech support ... there is a workaround.


Brian Suter
VP WebFOCUS Product Development
 
Posts: 200 | Location: NYC | Registered: January 02, 2007Report This Post
Platinum Member
posted Hide Post
But for the rest of the viewers of this thread .. I am interested in if sites are using business views and how are they using them? Change names? Structure? Hide fields? etc.


Brian Suter
VP WebFOCUS Product Development
 
Posts: 200 | Location: NYC | Registered: January 02, 2007Report This Post
Expert
posted Hide Post
"Art Greenhaus" method vs Business Views...
so far the ARt Greenhaus method wins, but it does not appear to work anymore in 764 (we have a case open to validate).
The principal reason we use the "AG" method is to hide KEY fields, they're ugly and useless to an enduser.
so..
USE
FILE1 AS FACTTABLE
FILE2 AS FACTTABLE
FILE3 AS FACTTABLE
END
JOIN KEY IN FACTTABLE TO KEY IN DIMTABLE AS J1
The AG method can hide the KEY easily
...
My read of the BV doc says i have to do this:
USE
FILE1 AS BV_FACTTABLE
FILE2 AS BV_FACTTABLE
FILE3 AS BV_FACTTABLE
END
JOIN KEY IN ... oops there's no KEY because its been taken out of the BV
My read of the BV doc says you can use a join IFF its in the original table's mfd, but i don't want to put a join in the original mfd.
Yes i could have a second master FACTABLE2 that contains JOINS, but then i have to maintain a second mfd everytime the original changes.
The hope of BV was that i would NOT have to change it when the original mfd changed. With AG, i had an alternate master and changed all the fieldnames in it.
The 2nd potential benefit of BV was the ability to rename a segment... which you can't do with just an alternate master
But as it is now, we have nothing.
AG doesn't work anymore and with BV we can't hide ugly keys .
Got any ideas?




In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report This Post
Platinum Member
posted Hide Post
A BV on top of an existing master can hide any field you have in the master.
Another way to hide a field is to use ACCESS=INTERNAL on the field in the original maaster. That will keep the field from showing up in any of the GUI trees. But it is still there and available to the syntax coders.


Brian Suter
VP WebFOCUS Product Development
 
Posts: 200 | Location: NYC | Registered: January 02, 2007Report This Post
Expert
posted Hide Post
ah.
but the question was how to hide a field in 2 masters, the field that is the basis of a join.

so you're saying ACCESS=INTERNAL would be the way to accomplish the ArtGreenhaus technique on a pair of masters, and then still be able to use the KEY fields in a JOIN between two business views? Is that right?

This message has been edited. Last edited by: susannah,




In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report This Post
Expert
posted Hide Post
I just tried adding ACCESS=INTERNAL to a master.
The RO wouldn't open, it bombed.
I searched for ACCESS=INTERNAL on the TEch Doc, and came up empty.
I searched for ACCESS=INTERNAL on the Advanced Search and the search crashed...i got "File cust_queryhit.idq. Unspecified error "

Could you point us to where this feature is documented?

according to the describing data manual, page 354, the possible values of the ACCESS= attribute are R,W,RW, and U only. Searching that manual, and the Developing RA and Creating.. manuals for ACCESS=INTERNAL comes up empty. Brian, can you please point us to the doc for your recommended technique?
thanks.




In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report This Post
Expert
posted Hide Post
update: we can make BV's work beautifully by hiding the KEY fields that we might want to use to JOIN with
not by using access=internal (which doesn't seem to exist)
but by using the now-nicely-documented-and-formalized FocWizard trick
found for me by CSS (thanks Fred!)
This technique lets you perform a multitude of mischief, notably *not* showing certain fields
in the Reporting Object Field List, whether that RO is a BV or just an ordinary master.

It works. so, now that makes BV's wickedly cool and usable. I'll now try to catch up to Dan's original post and see what happens..




In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report This Post
Platinum Member
posted Hide Post
ACCESS_PROPERTY = INTERNAL

Sorry for quoting the wrong keyword ... and sorry for delay, your question back to me got lost in the fog!


Brian Suter
VP WebFOCUS Product Development
 
Posts: 200 | Location: NYC | Registered: January 02, 2007Report This Post
Expert
posted Hide Post
no matter. JOINing 2 bv's doesn't work. which is fine. We built the combo mfd first, then a bv on top of that. worked like a charm, until we tried in RA to generate the list of values for a parm.
Same as Dan's original post.
If there is a w/a, can you please post it here. thanks, B.
We presented our first 'BV via RA' today and it went over huge! HUGE!




In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report This Post
Guru
posted Hide Post
With regard to the initial post, this is fixed in 7.6.5


7.7.05M/7.7.03 HF6 on Windows Server 2003 SP2 output to whatever is required.
 
Posts: 393 | Location: St. Paul, MN | Registered: November 06, 2007Report This Post
Expert
posted Hide Post
Dan, i just upgraded to 765 and tried it and i got 'failed to retrieve values', still.
Did you install the new ibiapplets.txt that was the 'workaround'?




In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report This Post
Platinum Member
posted Hide Post
Any updates on this, I am having the same issue.. Anyone else have a solution?
what is the workaround for this? Is this documented some where?

This message has been edited. Last edited by: getit,


App Studio Version 8202
windows Platform
SQL Server 2008/2012
 
Posts: 183 | Location: TX | Registered: January 22, 2007Report This Post
Expert
posted Hide Post
i remember using the ibiapplets.txt thta was sent to me by CSS, and i remember it working on 765, but we've moved on to Reporting Objects with lots of fex-y bits in them, so Business Views aren't on our list. We use RO's and rename and hide fields using the technique in tech memo 4550
or http://documentation.informati....htm?url=topic74.htm




In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report 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] Anybody Using Business Views?

Copyright © 1996-2020 Information Builders