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     [SOLVED] HTML Drill Down Report

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] HTML Drill Down Report
 Login/Join
 
Dan_Bam
Member
posted
We have an HTML drill_down report that drills into a second report and that part works fine. We used to be able to save that file to our desktop and retain the drill-down functionality, but that no longer works. We recently upgraded to 7.6 and then 7.6.5. What would have changed?

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


Webfocus 7.65
UNIX
 
Posts: 20 | Location: Rochester, New York | Registered: June 03, 2008Report This Post
GinnyJakes
Expert
posted Hide Post
What did you upgrade from?

When you look at the links in the saved html, are they using relative addressing such that they can't find the server?

Look up FOXECURL.


Ginny
---------------------------------
Prod: WF 7.7.01 Dev: WF 7.6.9-11
Admin, MRE,self-service; adapters: Teradata, DB2, Oracle, SQL Server, Essbase, ESRI, FlexEnable, Google
 
Posts: 2723 | Location: Ann Arbor, MI | Registered: April 05, 2006Report This Post
susannah
Expert
posted Hide Post
You may have had, in a pre-upgrade version,
the specific
SET FOCEXURL = 'http: etc'
hardcoded into your edasprof.
that is one possible diagnosis that would account for the symptom that you're seeing.

you might consider [just from a security perspective] putting that specific SET in each fex that actually needs it...
eg, in a caster job, you put it in a pre-processing condition. Then your emailed output will be drillable.



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
Dan_Bam
Member
posted Hide Post
We upgraded from 5.3 (5 point something). The stange thing is the report works fine in Managed Reporting and from the dashboard, but only looses the functionality once it is saved to an HTML file. I never would have thought that it would have ever saved that way, but the users tell me that it used to.


Webfocus 7.65
UNIX
 
Posts: 20 | Location: Rochester, New York | Registered: June 03, 2008Report This Post
susannah
Expert
posted Hide Post
again, Dan
for the very same reasons just stated.
take a look at the html report
do a view source on it
look at the drilldowns
are they full urls? or just relative urls?
if they are relative urls, the drill works in mre or dashboard fine
if they are full urls, the drills will work in a caster'd report, or from an html file saved by the user (although why a user would save an html file, i have no idea, but that's what users are.... challenges to bulletproofing.)
Look up FOCEXURL



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
Dan_Bam
Member
posted Hide Post
We had an IBI consultant here last week (for other reasons) who told me that there would be no way to do this, but the day he left I was able to make it work using suggestions from many of you. In short, it was a matter of setting the FOCEXURL to the specific path, but because of the "&" in that path it needed to be divided into several chunks. Thanks for all of your help.


Webfocus 7.65
UNIX
 
Posts: 20 | Location: Rochester, New York | Registered: June 03, 2008Report 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     [SOLVED] HTML Drill Down Report

Copyright © 1996-2020 Information Builders