[CLOSED] Active report excel export feature not working in chrome
Hey everyone, We have a report being used at the moment that in order for the users to export to excel they use the built in export feature in the active report menu.
When we tested that feature, it worked fine in IE but recently we have been allowing more and more people to use google chrome. We noticed that in doing so, that particular feature doesn't work. When you click export excel from the menu it just puts the comma delimited data into the browser window and nothing else happens.
Anyone else see this behavior or have a solution for it?This message has been edited. Last edited by: <Kathryn Henning>,
WebFOCUS App Studio 8.2.02 Windows 7, All Outputs
January 29, 2014, 07:26 PM
<Kathryn Henning>
Hi Tim P.,
Per your profile, you're using WebFOCUS release 7.7.03. For that release of WebFOCUS, the versions of Chrome that are supported are V12 and V10. Please see our support statement at:
I am having this same problem currently and I am on WEBFOCUS 8.1.05. Was this ever resolved? I have an AHTML that I am trying to export to excel using Chrome browser and it just puts the information in a new browser window. This works in IE. Solutions?
WebFOCUS 8.1.05 Windows, All Outputs
February 25, 2016, 12:19 PM
BabakNYC
I don't think Chrome likes the ActiveX necessary for this. Have you tried this code in your request:
ON TABLE SET WEBVIEWER ON ON TABLE SET CACHELINES ON
I was thinking it had to do with the Active X. I tried your two lines of code and it didn't work. It doesn't like the BYDISPLAY ON line when I add those two lines and it errors. But if I commented that out it still doesn't work.
WebFOCUS 8.1.05 Windows, All Outputs
February 26, 2016, 11:27 AM
CoolGuy
It should work in .xls after adding
ON TABLE SET WEBVIEWER ON
It will only work in .xlsx if you add
ON TABLE SET AREXPEXCEL XLSX
as well.
Also, make sure your redirection settings are permitting saving to the Excel format you want.
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
February 29, 2016, 09:46 AM
Francis Mariani
This thread prompted me to take a look at my Active HTML reports. We recently upgraded to IE11 and I guess I haven't checked everything yet because Export to Excel does not work when IE11 is NOT set to Enterprise Mode.
Unfortunately, AREXPEXCEL doesn't appear to be available in v8.0.08, or, it doesn't seem to be documented...
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
February 29, 2016, 01:12 PM
Francis Mariani
BabakNYC,
From the WF v8.0.08 documentation, it seems WEBVIEWER and CACHELINES are mutually exclusive:
quote:
Syntax: How to Control the Active Technologies Cache Option Because all post-retrieval processing is performed in the memory of the web browser, an active report has a processing limit of approximately 5,000 records or 100 pages of output. The active cache option enables you to send only the first page of active report output to the browser and retrieve subsequent pages from a temporary cache on the WebFOCUS Reporting Server. The server also becomes the resource for performing all calculations, sorting, and filtering when active cache is enabled. Since active cache uses on-demand paging functionality, WebFOCUS Viewer is not supported.
To enable active cache for active reports, use
ON TABLE SET WEBVIEWER {ON|OFF} ON TABLE SET CACHELINES {n|100} where:
ON - Runs the active report with active cache enabled. OFF - Will not enable active cache when the active report is run. OFF is the default value.
n|100 - Specifies the number of rows from cache. The default is 100.
Things don't make too much sense, e.g. "approximately 5,000 records or 100 pages of output" - does this mean five records per page?
Why is WEBVIEWER even involved here? Active Reports has its own paging mechanism, controlled by style-sheet option LINES-PER-PAGE.
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
February 29, 2016, 01:50 PM
BabakNYC
Francis: I think this might just be the work around to the issue of using a browser other than IE. I remember running into this and the WEBVIEWER and CACHELINES settings were what support provided as the solution. Note that the permissible options for CACHELINES is a number but the switch used is ON instead.
Tech support might have a better explanation of why these two settings fix the issue though.
