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,

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.

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 ?

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

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...

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

Craig's and jack's suggestion ([SOLVED] How to Handle Too Many Parameters) seem like the best solution, I have yet to try them.

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,

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.

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.

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