Greetings, this is my first post here, though I’ve been following the list for the last couple of months or so. I have been impressed with the quality of the dialog.
I’ve created several master-detail reports and have been saving these to an HTML file. I like how the sections are listed in the left browser frame, and the user can click on one to display the detail in the main frame.
The problem I have is that the detail for the first section always gets loaded in the main frame when the report is accessed. For our remote users this means they always have to wait for this data to load and display before they can choose the section that they are really interested in. I’d like for the detail to be loaded ONLY when a user selects a section.
So far I haven’t been able to come up with an elegant solution, though I can think of some messy ways that I’d rather avoid. Any ideas?
I’ve created several master-detail reports and have been saving these to an HTML file. The problem I have is that the detail for the first section always gets loaded in the main frame when the report is accessed. For our remote users this means they always have to wait for this data to load and display before they can choose the section that they are really interested in.
Paul,
Not sure how to program the loading of the HTML, but I had a similar scenario as you.
A “fix” would be to send different HTML reports out for the different users. For example, you have a BO doc with 10 report tabs. You have tabs 1-5 for user group 1, tabs 6-10 for user group 2. You can accomplish the creation of the HTML to a the server with a script using ExportSheetsAsHTML. You would call one ExportSheetsAsHTML function per report/user group that you wish to create.
or, have a seperate BO doc per user group with just the information they need then you wouldn’t necessarily need a script.
Hope this helps.
Shawn Leven
Southwestern Bell
Information Services SL7699@SBC.COM
Having separate tabs per user group wouldn’t really have worked, as the data is pretty dynamic and I’d have to regularly update the report. I took your idea of using ExportSheetAsHtml and created a generic script that I’ve attached to 3 different reports (so far) submitted to the DAS. It does the following:
Refreshes the document and creates the HTML files on our web server.
Renames the link “DocLinks.htm” to “doclinks.htm” (the file was being created on the server in lowercase, but the reference to it was in mixed case)
Adds a “Back” link to the bottom frame to return to the calling page (using the browser “back” button brings you back to every section you have viewed).
My original goal, replaces the link to “0.htm” in the main section to a simple instruction page (It only does this for detail reports within the document).
Thanks for the impetus to get me started with scripting. I’d be willing to share the script with anyone who is interested.
Paul T. Webb
Applied Microsystems Corp.
A “fix” would be to send different HTML reports out for the different users. For example, you have a BO doc with 10 report tabs. You have tabs 1-5 for user group 1, tabs 6-10 for user group 2. You can accomplish the creation of the HTML to a the server with a script using ExportSheetsAsHTML. You would call one ExportSheetsAsHTML function per report/user group that you wish to create.