Description: Opening a 329 kB xlsx file results in the following warning; "The data could not be loaded completely because the maximum number of columns per sheet was exceeded." The number of columns being used in the sheet is 32. I compared the loaded spreadsheet in LibreOffcie Calc 7.2.2 to the same spreadsheet loaded in Softmaker Planmaker. Planmaker does not throw a warning. Both sheets appear identical in either Libre or Planmaker. The warning message is causing mistrust of the product. Office workers, on seeing this message, are afraid to modify the sheet for fear that there has been some portion of the sheet that has not been loaded. This is impeding adoption. Actual Results: Throws a warning that informs the user that the data could not be loaded completely, yet the spreadsheet SEEMS to load OK, there doesn't seem to be any data missing. Expected Results: Expect the spreadsheet to load with no warnings thrown, as it does in Softmaker PlanMaker and Microsoft Excel. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.2.2 / LibreOffice Community Build: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 Environment: CPU threads: 8; OS: Linux 5.4 UserInterface: UI render: default; VCL: gtk3 Locale: en-CA (en_CA.UTF-8); UI: en-US Misc: Calc: threaded
If you need a copy of the sheet that is throwing this error just ask.
(In reply to stephen.bungay42 from comment #0) > If you need a copy of course a sample document will ease to reproduce the problem.
I am not able to reproduce this message using a 32 column sheet that I created in LO Calc, saved as xlsx, closed, and then re-opened. Stephen, If the spreadsheet in question does not contain any proprietary data, please attach it to this report so that we can use it for debugging and testing.
Created attachment 176543 [details] Screenshot with error message More or less REPRODUCIBLE with attachment 176542 [details] from Bug 145922 with Server Installation of Version: 7.4.0.0.alpha0+ (x64) Build ID ae36ee4f3aa544e53e2edad93d6d79160b27bc9d CPU threads: 12; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win | Special devUserProfile | Locale: de-DE (de_DE); UI: de-DE | Calc: CL Maximum number of Coumns in sheet "MP3-CUP-SEN" is 251 (IQ) - if I did not make a mistake. Same with 7.2
Dear stephen.bungay42, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear stephen.bungay42, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp