I know this has been reported before, but I feel it worth rehashing. I also know that it ain't easy, so apologies if this irritates people. I have a relatively small spreadsheet created by Office 365. The owner says it's beyond the capabilities of LO, and has as a result gone to Office 365. They say that the pivot tables are beyond LO, but I can see no issues when loaded in. However, I am no expert in pivot tables! The other major issue they report is LO is simply too slow, and just too slow to load the documents. MS Office loads these files almost instantaneously, while LO takes 35 seconds. It is not my intention to cause anger, please don't shoot the messenger, I've been an advocate for LO ever since it was Star Office! But why is what is so easy for MS Office is laborious for LO? I will have to seek permission to upload the file I have, and I suspect the answer will be no, unfortunately, as it probably contains commercially sensitive data.
First, one tracker per bug. So this one would be for slowliness since it's the title, for the other bugs, you should submit other bugtrackers. About the file, you can sanitize it (see https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission) before attaching it.
Many thanks for your reply. The only issue in this ticket should indeed be read as slowness. The sanitize instructions are for files in OD format, shouldn't the data only be handled by Office 365? If I load into LO, as save as xlsx format hasn't the file already been changed? I will go back to the file's author and see if the process can be handled in 365, but I fear it may be met with indifference.
(In reply to Owen Savill from comment #2) > Many thanks for your reply. The only issue in this ticket should indeed be > read as slowness. > > The sanitize instructions are for files in OD format, shouldn't the data > only be handled by Office 365? If I load into LO, as save as xlsx format > hasn't the file already been changed? > > I will go back to the file's author and see if the process can be handled in > 365, but I fear it may be met with indifference. IHMO if people of your company don't care, you should just give up. They paid to have MsOffice 365 so I don't think they would spend some time and money to migrate towards LibreOffice.
Thank you for your comment, I think. We, as a company, have not gone with Office 365 and we, as a company, do care, which is why I, as an individual, raise tickets where I believe it may help with the adoption of LO. We cannot control what other entities decide to use for their office application. Whatever the ins and outs of how we got to where we are now, it seems perfectly valid to raise a ticket with LO to raise the issue that some files are desperately slow to import.
Indeed it's perfectly valid to raise a ticket with LO" but don't expect much if you can't provide a file since, without it, this ticket may fall, like your colleagues, into indifference. Now, there are already similar bugs so wait and see.
I have asked for an anonymized version, I haven't heard back yet
[Automated Action] NeedInfo-To-Unconfirmed
I have repeated my request for an all zeroed or anonymised spreadsheet
Thank you for submitting the bug. I'm going to mark this as 'NEEDINFO'. Once a sanitized file is attached, please change the status back to 'UNCONFIRMED'.
I got a spreadsheet from accounts, but rather than setting all the numeric fields to something like 12.34 they had simply deleted the content. This document loads quite acceptably into LO, with all the pivot calculations just showing #REF. Which may give an indication why the original was so slow to load. All the pivot calculations. I have no idea how this is done, but is it single threaded? Does it all need to be done as the document loads. How does MS Office do it so fast?! I have gone back to accounts and asked for one to be prep'd with 12.34 for all data fields. I could do this myself in LO, but this would alter the .docx data. If you feel it's a worthwhile exercise for me to do I'm happy to do it and post the file here.
Tomaž: thought you might be interested in this one since the slowliness may concern pivot part. The pb is the level of sanitizing here since it seems that sanitizing too much the file almost makes the pb disappear (see last comment of the reporter). Any thoughts here?