In modifying my CSV file by deleting rows, and then saving the changes to the file, LibreOffice "corrupts" the file. This can be viewed either by simply "reloading" via the File->Reload menu, or by closing and then opening the file. The corruption is as follows. Usually, some component of the file data that was deleted is appended as additional columnar data, rows, or both. I use CSV files to load data into my SFDC instance. A current work-around is to save the file using a different file name. That appears to prevent the corruption.
Could you attach any example documents to allow others to check on different system/build?
Created attachment 79031 [details] Simple Catalog CSV file You can use this CSV file.
Hi Chad, I can not reproduce with: Win7x64 Ultimate Versión 4.0.3.3 (ID de compilación: 0eaa50a932c8f2199a615e1eb30f7ac74279539) Have you tried to reset the user profile?, sometimes solve strange issues. https://wiki.documentfoundation.org/UserProfile
I have not tried resetting the user profile. I'm using Windows 8 Pro with Media Center 64 bit. I'll try resetting the profile. The issue only happens when I save the changes (not save as different file) to the open file. If you reload that file, I see the issues.
Please attach the file after corruption and exactly describe what operations on which rows do you apply. Also, try updating LibreOffice and use another user account in Windows.
Hi Chad, something to comment about this issue?
Dear Bug Submitter, 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 INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/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
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID 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 FDO