We just migrated to WF8 this past weekend. We've found reports executed through HTML Composer are performing differently then they did in WF7 and I can't figure out why. When executing a report via HTML Composer in WF8, if I fail to populate a parameter that is that is marked 'No' under Selection Required, instead of executing the report a new window launches asking me to populate the parameter fields I left blank in the HTML Composer. This did not happen in WF7. If I click 'Run' again in the new window the report will run fine without input in those parameter fields. As a quick test I built a brand new HTML Composer launch page and the same thing happened. I can't find any articles about this in Focal Point, has anyone else run into this?

This message has been edited. Last edited by: <Emily McAllister>,

I think you may have to add in -DEFAULTH for all these variables to stop the prompts.

Thanks for your quick reply, -DEFAULTH will hide the parameter in HTML, correct? I want users to enter values in the parameter if they want to (it's marked as optional in the HTML Composer ... I'm in the GUI if that isn't obvious), I just don't want the follow-up HTML page that asks for the parameters again. I am using HTML Composer as a user-friendly launch page for a fairly complex .fex report, could my problem be in that source .fex code?

Here is a screenshot of my launch page in HTML Composer:



and here is the next page that launches when I hit the 'Run' button if I leave the parameters marked as optional with a * blank:

This message has been edited. Last edited by: Clint Coffey,

Go into Client Administration Console > Application Settings > Parameter Prompting. What is the value there?

I think the default is XMLRUN which I think is causing your issue. If you change it to "OFF" I think this will resolve your issue.

Just becareful as it's a system setting.

We converted to WF 8.1.05 earlier this year.
You have to issue -DEFAULTS for "ALL" parameters, including the ones in the HTML when you want to pass the display value(s).
IBI went way overboard with this, and, your pain will increase when the prompter comes up with no parameters to enter whatsoever; you'll have to figure it out...

Have Fun!

I believe this was a part of code tightening in Version 8. as Tom said, you have to issue defaults for all parameters now. I've always used -DEFAULTH, so I was luck that this one didn't burn me.

Thanks everybody, -DEFAULTH worked. Now it's time for me to dig into the labyrinth that is our dashboard structure to find more. Joy.

quote:

Oyour pain will increase when the prompter comes up with no parameters to enter whatsoever

Hey Eric, I didn't run into this, in WF7 we had focnone in these so maybe that is helping us avoid this issue. Thanks for your help!

Clint,

WF7 worked very different when it came to prompting. I think it has to do with a change to the "Prompt for paramaters" option. I think that was changed. It doesn't seem to work for me like it used to in 7.7.03 and before.

FOCNONE is the ignore character. Its the predecessor to _FOC_NULL. Although you can still define your "_FOC_NULL" value. I believe the administration console has a way to customize this, as well you can define it in the HTML composer.