Don’t know it this help to solve your issue but you can set the office version in the configurator editor

if set to Office2003 the export from Alliance will be done as xsl if you set to office  2007 it will be done as xlsx

Unfortunately, I do not have these options under Configuration Editor, maybe that’s because we are hosted?

Hi Leann,

That is correct… the web employee portal does not give you access to this section of the global.xml settings which are not in the profile.  The Web Employee portal configuration editor provides you access to the profile settings, not the General setting.

However, there is no reason you cannot ask Support to set your configuration to Office 2003 as suggested by Christophe.  They can ask the hosting group to make this change for you at a time which is convenient as I don’t recall if this requires a restart or not.

My suggestion is ask Alliance Support to do this to your UAT system first and see if this achieves the results you are looking to have and if so, modify the setting on Production.

Hope this helps.

To follow up, we asked hosting to update the configuration to Office 2003, but this did not change the issue when running reports through the batch manager. Short of reconfiguring our current reports that are run this way, do you have any other suggestions? We have also confirmed with IT department that the reports cannot be converted, we receive corruption errors when opening as xlsx docs. 

Hi Leann,

I think the file type is determined by the office version that is configured when the batch is created.  For example, if OfficeVersion is set to Office2007, batches will be created with the file type parameter set to XLSX.  I think you will either need to recreate the batches after changing the office version, or we will need to update the parameters via SQL.

Thanks,
Andrew