When creating an HTML Composer designed form in MRE, you can add a Save Selection button. That adds a call to a JavaScript function called SaveSelectedParameters and the parameters are saved to the My Reports area of MRE.

Has anyone made this work? As someone just pointed out, the button appears in HTML Composer, but does not display when launching the form.

Thanks,

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

I think Don did...

Yes, it's working in 7.6.11. Seems like the user has to have 'My Reports' enabled in MRE though. Do you see the elements in text?

i.e.

 // **************************************************************************************************************************************************************************
//Begin function saveButton_onclick
function saveButton_onclick(ctrl) {
// TODO: Add your event handler code here
SaveSelectedParameters()
}
//End function saveButton_onclick
 

This message has been edited. Last edited by: Don Garland,

Don,

Thanks for the info. I found a temporary solution to the missing Save Selections button - I created a simple button that executes the same JS as the Save Selections button.

I just wonder why the Save Selections button does not display.

Regards,

Hi Gang,

That is not how you do this. Save Sekection is only in Managed Reportng, so the page must be in MR in order to add it to the page. The next requirement is that the user at runtime must be allowed to save parameterized reports. That is an MR permission for the user. If the user does not see the button at runtime, it means they do not have the privilege to save parameterized reports.

quote:

Managed

Yep, I thought of that last night. You apply it in DevStudio but it only works when you run the report from MR.

"That is not how you do this". This is how I am doing it. This IS all in MRE. For some reason, which I hope you can explain, the Save Selection button does not appear on the MRE contained, HTML Composer composed page. What is going on? At first I thought the problem was I was running the screen from Dev Studio - you know, for testing purposes - which Dev Studio allows you to do. Then I ran it from the MRE Domain Builder and I have the same result - no Save Selections button.

Oh, and by the way, I think DevStudio is smart enough to determine if the html page is in MRE or not - if it is not in MRE, the Save Selections icon in the Components toolbar is disabled.

Francis,

quote:

I think DevStudio is smart enough to determine if the html page is in MRE or not

Check out the [CLOSED / SHARING] Composer / JavaScript question post

Francis,

I don't understand what you are trying to get at. The product writes specific MR attributes to a page created in MR. So of course it knows the page is an MR page.

If you have created the page using the GUI in MR, and have the Save Selection button on it, and you run the page with a user that has the save parameterized report permission, the button will display and work.

I have the same problem as Francis. It appears I have to have two save selections for one to appear at run time.

David describes how it's supposed to work. I have described how it actually does not work, unless you intervene.

"I don't understand what you are trying to get at. The product writes specific MR attributes to a page created in MR. So of course it knows the page is an MR page." - I wouldn't bring this up if I didn't create the form in HTML Composer and if I didn't abide by all the rules, so, something is wrong. This is one of two FocalPoint threads that mentions the Save Selection button does not display when running the page. In fact, it appears for .25 seconds before disappearing.

Francis --

But has the MR user-ID you use to test the report been granted the "save parameterized report permission"? You sort of implied that, but didn't say so explicitly.

Thanks Jack. I said that too. The MR user needs the permission in order to see it.

I do not know if the user has been granted the "save parameterized report permission". I didn't know one needed to.

Thank you for pointing this out. We use Active Directory and the MRE Administration page does not contain our User ID's.

I really wish that D.G. wouldn't get so prickly. We developers live in the real world with hundreds of programs of many variations, not in some protected universe where four or five example programs work really well.

I have found this Save Parameter functionality does not work when the MRE program is a fex that has an -HTMLFORM app/page_name.htm in it. Is this documented?

I have a simple HTML pageusing the CAR file in a Tree Control and I did make the Save Parameters work.

I have a slightly more complex HTML page - completely created by HTML Composer GUI, with additional JavaScript, which, I believe, is supported. I get a JavaScript error on line 9430 in file ibirls3.js. Now, how do I debug this and why is it happening on a page that was completely built in HTML Composer GUI (with no launch fex)?

Francis,

It is documented that -HTMLFORM and HTML Composer should not be used together. It was also a topic in my "Best Practices" presentation I did for the FocalPoint audience a few weeks ago. Save Selection creates an HTML page with the saved values and calls back to the original HTML page. -HTMLFORM needs to be in a FEX. So they cannot work together.

Fine, but you didn't answer my second question: "how do I debug this and why is it happening on a page that was completely built in HTML Composer GUI (with no launch fex)?".

If you are not using -HTMLFORM, I have no idea and suggest you open a case with Support Services.

Francis, I don't know if this is still an issue for you, but check out my workaround here