I made a web-based report showing two interface custom properties, the interface speed, tx%, rcv%, tx bps, and rx bps. There are only seven interfaces. The report looks fine when viewed natively via reports management in web interface. I made note of the URL and added custom HTML resource to an existing page. The HTML is i-frame code with the URL of the web report. I even added &&PRINTABLE=TRUE to the URL and ensured that my report had no logos. When I add that i-frame plus custom HTML with report URL to my previously working page, the web report loads while nothing else does. The other resources are mix of Top XX UDP resources, AJAX trees, and ReportWriter resources. There are no limitations on my page or the account.
The report I am replacing was done via ReportWriter. My dilemma is that making reports in Win32 application ReportWriter and then copying that same report to my other installations seems a little inefficient and not in keeping with the direction the product is going. I thought of using the SWQL hammer on this nail, but figured that was overcomplicating given that I only need to show seven interfaces, native interface metrics, and two custom properties for each interface. From a time management point of view, I would like to use the web reporting more (this may even be my first web report, having done ReportWriter stuff over the past eight years with more SWQL over the last six months).
Is there a better way to show a web report via the web? It seemed that natively one can only show ReportWriter resources with no option to show web reports (the irony does not escape me). I've opened a support case in hopes that I've missed something, but I figure I'd stick my finger in the wind to see everyone else's experience with web reports on summary pages.