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] WF report - too many drilldown values causes error

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED] WF report - too many drilldown values causes error
 Login/Join
 
Francis Mariani
Expert
posted
I get this error:

(FOC3202) BAD VALUE IN STYLESHEET FILE AT LINE 281:
FOCEXEC=app/fex_name( ASSET=FUNDGR ASSET_DESC=FUNDGR_DESC FUND

Though this error does not point to it, I know there are to many selected values being passed in the drilldown. The total number of bytes for the whole drilldown is over 4590. If I reduce the number of values being passed in the drilldown, the report works. These values are successfully being used in the main report, but they're causing the error in the drilldown area of the code:

TYPE=DATA,
     COLUMN=BIFUNDGROUP,
     FOCEXEC=app/fex_name( \
     ASSET=FUNDGROUP \
     ASSET_DESC=FUNDGROUP \
     FUND=&FUND.QUOTEDSTRING \
...


&FUND is about 1936 characters long, and there are two sets of values like this.

Does anyone know what the limit is?

Thanks,

This message has been edited. Last edited by: Francis Mariani,


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Report This Post
Waz
Expert
posted Hide Post
As the drilldown is performed as a method GET, it has a limitation the same as typing the URL into the address bar.

The only way I know to avoid this is to submit a form with METHOD POST.


Waz...

Prod:WebFOCUS 7.6.10/8.1.04Upgrade:WebFOCUS 8.2.07OS:LinuxOutputs:HTML, PDF, Excel, PPT
In Focus since 1984
Pity the lost knowledge of an old programmer!

 
Posts: 6347 | Location: 33°49'23.0"S, 151°11'41.0"E | Registered: October 31, 2006Report This Post
FrankDutch
Virtuoso
posted Hide Post
Francis, IT is a known issue, many years ago on the summit there was a presentation held by Tony and Susannah and the mentioned this.
Keep the drill short.
Better only drill the code and do the decoding in the second report.
And I know that is not always the best solution. Since you may need to go back to the server again.
Maybe it is possible to write the long string to a small txt file like the POST command you have in FML ?




Frank
prod: WF 7.6.10 platform Windows,
databases: msSQL2000, msSQL2005, RMS, Oracle, Sybase,IE7
test: WF 7.6.10 on the same platform and databases,IE7

 
Posts: 2387 | Location: Amsterdam, the Netherlands | Registered: December 03, 2006Report This Post
<FreSte>
posted
You could also change the local ampers to global ampers.
If parameter IBIF_persistentamp is set to Yes the global variables will persist during the browser session.
(see WebFOCUS Admin Console under Configuration/General for setting this parameter)


quote:

IBIF_persistentamp
Turns on the persistent && feature. By default, this is set to YES. To disable, set to NO. The persistent && feature allows you to persist && variables for the duration of the browser session.


... or use the FOCCACHE directory for temp storage

-Fred
 
Report This Post
Francis Mariani
Expert
posted Hide Post
I was hoping I didn't have to make too many coding changes.

I had to modify the drilldown to use names instead of codes because the data is very very dirty and the client has no intention of cleaning it - just throw it into the reporting tables and let the programmer worry about it.

I have two choices - say that I've completed the requested task and let them discover the issue or spend time on a decent workaround, and this for only one of the five drilldown values...


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Report This Post
Craig R.
Gold member
posted Hide Post
I've got a few drilldowns with long parameter strings like that. I ended up writing the string to a file in FOCCACHE, building a unique file name by appending time-of-day, and then passing the file name in the drilldown.

Craig


v8.1.04, 64-bit Windows (Reporting Server), Apache Tomcat (Web/App Server), HTML, PDF, AHTML, Excel outputs
 
Posts: 57 | Location: Des Moines, IA | Registered: April 30, 2009Report This Post
Francis Mariani
Expert
posted Hide Post
Craig's and jack's suggestion ([SOLVED] How to Handle Too Many Parameters) seem like the best solution, I have yet to try them.


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Report This Post
J
Guru
posted Hide Post
Instead of javascript, I usually just test variable lengths to see if they are too large.
IF &var.LENGTH GE [limit (usually 2000 is good)] THEN GOTO ALTERNATIVE/ERROR MESSAGE

Then you can do it the normal way for most cases. Since this is server side only, it shouldn't be too hard to come up with a solution.

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


WebFOCUS 7.7.03/8.0.08
Dev Studio 7.7.03/8.0.08
App Studio 8.0.08
Windows 7
ALL Outputs
 
Posts: 402 | Location: Upland, IN | Registered: June 08, 2012Report This Post
Francis Mariani
Expert
posted Hide Post
This is my situation:

I have a parameter screen designed by HTML Composer GUI, with a double list box where many options can be selected.

Then click submit to run the report, using the selected options in a WHERE statement. This works fine.

Then I have a drill-down where I need to pass the previously selected (and successfully used) values - this is where I get a Dialogue Manager error.


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Report This Post
Waz
Expert
posted Hide Post
quote:
this is where I get a Dialogue Manager error.


Is that because of the length of all the paramters ? They get truncated ?

I really do with that IBI would change there drilldown model to submit a form and not open a URL, all this would be a moot point and there would be better security as well.


Waz...

Prod:WebFOCUS 7.6.10/8.1.04Upgrade:WebFOCUS 8.2.07OS:LinuxOutputs:HTML, PDF, Excel, PPT
In Focus since 1984
Pity the lost knowledge of an old programmer!

 
Posts: 6347 | Location: 33°49'23.0"S, 151°11'41.0"E | Registered: October 31, 2006Report This Post
Francis Mariani
Expert
posted Hide Post
The line number in the error is the first line of the drill-down string, so I assume its the total length that's too long, but nothing else indicates what the error really is...

BAD VALUE IN STYLESHEET FILE AT LINE 281


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Report 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] WF report - too many drilldown values causes error

Copyright © 1996-2020 Information Builders