Account Schedule Export to Excel > Update Existing Document will no longer save to .xlxm file

(0) Share

Report

Posted on by tww

Account Schedule > Navigate > Overview > Actions > Excel > Export Excel > Update Existing Document

Up until this past update, we were able to export an Account Schedule to an existing Macro-Enabled Excel file. The reason for this was, so we could run the macro to format the exported report the way management would like to see it. This has not been a problem since we set up these .xlxm "template" files, until a couple days ago it was reported that this was no longer working.

I did some trouble shooting, and we can still run this same process if we "Update Existing Document" and that document is a .xlxs file, but not a .xlxm. The only thing that struck me was that I received an email notifying me of the new BC update pushed a couple days ago and thought, could this be the reason?

When you run this process using our .xlxm file, it seems to work, until you try to open the file at which point your get an error message:"Excel cannot open the file 'name.xlxs' because the file format or file extension is not valid.Verify that the file has not been corrupted and that the file extension matches the format of the file."

I have the same question (0)

All responses (9)

Answers (1)

Suggested answer

Marco Mels on at

Like (0)

Report

Hello,

This does look like customization, is this also happening in standard CRONUS company?

Thanks.

Was this reply helpful? Yes No
tww 90 on at

Like (0)

Report

The capability of downloading and updating an existing document is not custom. So I guess the question is, after the update are they now blocking downloads to a .xlxm file, as it used to allow us to do this with no issue.

Was this reply helpful? Yes No
Heather Roggeveen 9,146 on at

Like (0)

Report

It doesn't work for me or my client just trying to update an existing .xlxs either - it creates a new random document that we then need to "save as" which then means anything like pivot tables etc linked to the raw data have to be recreated or copy and paste over the raw data. Very frustrating.

Was this reply helpful? Yes No
Suggested answer

Marco Mels on at

Like (0)

Report

Hello,

In W1, I do see the following:

There is no Navigate here:

There are others that confirm the behavior, so I guess I simply cannot find it in standard. It may it does exist in a specific localized release or I am completely off track here.

Thanks.

Was this reply helpful? Yes No
Suggested answer

CM-23071823-0 on at

Like (1)

Report

Hi Terri, what happen if you try the same but before opening the "corrupted file" you changed the extension to xlxm file? Does it open correctly?

Was this reply helpful? Yes No
tww 90 on at

Like (1)

Report

Carlos....that seemed to have done it! Thanks. Side note, you had a typo on the macro extension "xlxm"...should be "xlsm", but once I change that it worked. Still a little bit annoying as you still have another step, but it is not as convoluted and what we were having to do before.

Was this reply helpful? Yes No
CM-23071823-0 on at

Like (1)

Report

I'm glad it worked. I believe this issue has already been reported to Microsoft in order to review this behavior.

Was this reply helpful? Yes No
Verified answer

CM-23071823-0 on at

Like (1)

Report

It seems a fix was deployed recently for this issue, so hopefully the scenario should be working properly now, without the need of a workaround.

Was this reply helpful? Yes No
tww 90 on at

Like (0)

Report

I was told it seems to be working....Thanks for the heads up on this.

Was this reply helpful? Yes No