This is still needed!!!

This is still needed.  In order for Confluence to compete with SharePoint, we need to be able to use the same files.  I'm not going to have some files in Confluence and some files in SharePoint - I'll just put everything in SharePoint and Confluence will wither and die.

Hello,
I would like to vote for this issue but it seems closed.
I checked, it is just the name of the file that causes a problem, if you rename it in .xls for exemple (not save as but rename in explorer) it is embeddable, still works in Excel.
The only problem is that you get warnings in Excel about security because the file name is not correct.
So maybe you just add .xlsm to the list of "acceptable" files for the office macro ?

I am hoping I can plead to have this request revisited and re-opened and added to the planned backlog for a fix. I have several projects that use MS Excel macro-enabled workbooks to track data and am trying to avoid having the data hosted elsewhere which will cause people to cease feeling the burning need to visit the Confluence site and then it will wither and die. Dont let my project site die... please... please.... fix this little bug.

Hello guys,

As suggested in the Atlassian OnDemand Support in the Request JST-160327 I'm adding here a few points why xlsview macro is very useful and should not be decommitted or deprecated

1. Preview does not render spreadsheets correctly (please look at attached xlsx_preview.jpg that displays how preview renders the file, and at xlsx_preview_src.jpg that displays the exact content of what must be rendered)
2. Preview does not allow to select a sheet number to be rendered, it always renders the very first spreadsheet; xlsview - does.
3. Preview is not capable to render spreadsheets in-place (i.e. embedded into the page), which is very useful as user does not have to download the file to view it, user cannot search content directly within the page, etc.; xlsview - does.
4. Preview does not allow to search (сtrl/cmd+f) content of the rendered file (please look at the previous point); xlsview - does.
5. Preview does work from time to time (please look at xlsx_preview_dontwork.jpg); xlsview - always does (according to my experience).

I just would like to understand why such a simple feature like allowing xlsview macro to render xlsm files cannot be implemented, although this feature already works if you just change an extension from xlsm to xlsx, and instead forcing users to use preview functionality (which is not user-friendly). Why not use both to make your customers happy?

Kind Regards,
Sergey

Hi Natasha,

>> Going forward, we will not be investing in the viewfile macros

Could you please clarify, why so? ... especially when Wayne mentioned that it's as trivial as changing file extension, that means it's only necessary to allow xlsview to allow to select xlsm files.

Kind Regards,
Sergey

Hi @natasha,
I've tried to view attached .xlsm files with reference to your latest post that it is possible with the new file previewer - but what is the trick? We are running 5.8.6 and there is no preview of these .xlsm files.
Please advice,
Arne

Thanks everyone for your feedback on this issue. As part of Confluence 5.7, we've launched a new file previewer which is able to handle xlsm files. Going forward, we will not be investing in the viewfile macros; improvements will be made to the new previewer instead. Please try it out and raise an issue against it if the problem persists.

Best,
Natasha Prasad
Confluence Product Manager

Bill Arconati [Atlassian], thanks for looking at this again, much appreciated.

Thanks for calling this to our attention. We'll have a look into this and see if it's a matter of changing a filter.