3,131
I have a report controller class and am trying to prevent the parameters dialog from showing in certain instances.
myController.parmShowDialog(false);
myController.StartOperation();
the parmShowDialog is not preventing the dialog from showing.
*This post is locked for comments
Tried it on 365 and myController.parmLoadFromSysLastValue() still works.
Hi, Sadly no I had not, I've been moved on to 365 now so I have a whole different set of issues!
Well, in case anyone cares, I found out how to work around the formRun abject error message. The controller main method must be defined as running on the client:
public static void main(Args _args)
instead of
public static void main(Args _args)
This could however prevent a report from running in batch.
Hi James,
Howard was the last person who had participated to this thread. We're currently are using R3 cu8. I managed to control the parmshowDialog using a different menu item and checking for the source of the call to the controller like this, in the main method of the controller:
if(_args && _args.menuItemName() == menuitemOutputStr(silentTaxReporting))
{
controller.parmShowDialog(false);
controller.parmLoadFromSysLastValue(false);
}
else
{
controller.parmShowDialog(true);
}
However subsequent run to the interactive session of the report yields a "Object Formrun could not be created". So in the end, I'm not really making any progress! :)
Regards
A workaround is fixing the underlying problem by yourself, as discussed in previous replies in this thread.
.
I'm not sure its by design - how then are you to suppress a dialog without removing all the user data? In my example I just want to print silently to the last location for the report. In addition they use the parmShowDialog in a lot of places.
I may raise it to see what they say. I don't think there is any other practical way to supress the dialog and keep the usage data....
No, I didn't raise it with Microsoft, because it's likely by design. You can raise it by yourself, if you want.
I'm currently looking into R2 and it's there.
No I'd not want to be messing with it too much and changing every single report controller class that I want to supress a dialog on seems like overkill too. Have you raised it with Microsoft? BTW I've also just tested it on 6.2.1000.1437 and it works. My best guess would be its something introduced in R3
#1
Kempeth
4
#1
Andy Adamak
4
#1
Community Member
4
Share
Report
All responses (
Answers (
