I have an active document. When I run the document from the WebFocus BI Portal or from AppStudio, the Excel export works perfectly fine after adding in the required code:

 
SET WEBVIEWER = ON
SET AREXPEXCEL = XLSX
 

However, if I schedule the exact same report to be emailed, and open it up from the email attachment, the export option turns to XML (Excel) and exports it as XML.



Is there something that I am missing?

Here is an example of the code I am using:

  
ENGINE INT CACHE SET ON
SET PAGE-NUM = NOLEAD
SET EMPTYREPORT = ON
SET WEBVIEWER = ON
SET AREXPEXCEL = XLSX

COMPOUND LAYOUT PCHOLD FORMAT AHTML
SECTION=Section_1, LAYOUT=ON, PAGESIZE=LETTER, ORIENTATION=PORTRAIT, SHOW_GLOBALFILTER=OFF, ACTIVE_UNITS=PTS, PAGECOLOR=RGB(255 255 255), $
PAGELAYOUT=1, NAME='Page 1', TEXT='Page 1', LEFTMARGIN=0.25, RIGHTMARGIN=0.25, TOPMARGIN=0.25, BOTTOMMARGIN=0.25, $
COMPONENT=Table_1, COMPONENT-TYPE=REPORT, POSITION=(1.041666 1.041666), DIMENSION=(* *), ARREPORTSIZE=DIMENSION, $
PAGELAYOUT=2, NAME='Page 2', TEXT='Page 2', LEFTMARGIN=0.25, RIGHTMARGIN=0.25, TOPMARGIN=0.25, BOTTOMMARGIN=0.25, $
COMPONENT=Table_2, COMPONENT-TYPE=REPORT, POSITION=(1.041666 1.041666), DIMENSION=(* *), ARREPORTSIZE=DIMENSION, $
END

SET COMPONENT=Table_1

TABLE FILE ibisamp/car
SUM CAR.BODY.DEALER_COST
BY CAR.ORIGIN.COUNTRY
BY CAR.COMP.CAR
BY CAR.CARREC.MODEL
BY CAR.BODY.BODYTYPE
END

SET COMPONENT=Table_2

TABLE FILE ibisamp/car
SUM CAR.BODY.RETAIL_COST
BY CAR.ORIGIN.COUNTRY
BY CAR.COMP.CAR
BY CAR.CARREC.MODEL
BY CAR.BODY.BODYTYPE

END

COMPOUND END

This message has been edited. Last edited by: Hallway,

I cannot confirm 100% since it's very technical on how IBI generates the files but my assumption is that :

- when you run directly (from the portal/AS) the "data" is stored in the cache so it's possible to the active technology (AHTML) to download the data into Excel since the data is in memory.

- when you open it from a received email the data as been "sent" (attached in the mail) as in a format that can be managed by the mail service which is as XML format. So once opened, the data can be download to Excel but from the same source as when you open the mail : from XML data.

I end to this conclusion because if you do compare both "view source" of the reports (direct vs mail) the only difference is the following line :

direct execution :

<meta name="ibi-report" content="type=AHTML, records=18, columns=5, iscompound=true, iscache=true, isextjs=false"/>

open from mail :

<meta name="ibi-report" content="type=AHTML, records=18, columns=5, iscompound=true, iscache=false, isextjs=false"/>

Look at the "iscache" option

What browser are you using to open the Active report? Make sure you test both scenarios with IE.

I've tested it Babak and IE react exactly as Hallway said.

Also react the same way with FF or GG.

I don't think that it' a browser "issue".
The more I think about it, the more I think that I've found the reason as explained in my previous post.

I just tested the code. I do get the XML (Excel) on the export drop down as well, however, when I click it, I get a pop-up about an ActiveX opening Excel and the worksheet opens with the data. I remembered something about the pop-up and here's something I found in the tech support site. Maybe it'll be helpful.

Check these settings in IE

1 - Opened an IE browser.
2 - Look in the browser status bar at the bottom of the browser. In this case
    it states "Internet".
3 - Click on Tools --> Internet Options.
4 - Click on the "Security" tab. Make sure the "Internet" zone is selected or
    what was observed in step 2.
5 - Click "Custom level ..." and scroll down to "Downloads".
6 - Change "Automatic prompting for file downloads" to Enable and click on the
    "OK" button.
7 - If you receive a Warning message about changing this setting, click on the
    "Yes" button.

If the Excel report does not open at this time, look at the Status bar as
stated in Step 2. If it states "Local internet" or "Trusted sites", then repeat
Steps 4 thru steps 7 for that zone.

Joking aside... Thanks for your insight. However our end users can't even enter in their credentials correctly in IE. I know that we would not be able to get them to follow all those steps is setting up their browser. We have instructed our end users to use Chrome because of all of the issues related to IE.

It's frustrating that IBI's big selling point on the Active Document is that everything needed is "all self contained within the document." Apparently this is false.

This message has been edited. Last edited by: Hallway,

Maybe you can let IB's tech support know that. My suggestion was intended to help you figure out what the problem was not to dictate what browser to use. BTW, I just Opened the html file in Chrome and Export XML (Excel) worked.

I appreciate your help BabakNYC. Thank you for your insight.

quote:

Originally posted by BabakNYC:
Maybe you can let IB's tech support know that. My suggestion was intended to help you figure out what the problem was not to dictate what browser to use. BTW, I just Opened the html file in Chrome and Export XML (Excel) worked.

I just saw that you are running WF 8201. So I tested it in our 8201 environment (that we haven't gone live with yet) and it worked. Granted it was still in Excel's 17 year old format (EXL2K not XLSX), but it worked in Chrome.