Description: After exporting a sheet to .CSV file by StoreToURL(), last rows from the sheet are missing in the .CSV file. After repeating export with changed number of rows to be exported, exported number rows in target .CSV file is not changing, it is constant. Macro used for export follows: sub export_to_CSV() Dim AAS( 1 ) as New com.sun.star.beans.PropertyValue AAS( 0 ).Name = "FilterName" AAS( 0 ).Value = "Text - txt - csv (StarCalc)" AAS( 1 ).Name = "FilterOptions" AAS( 1 ).Value = "44,34,0,1,1" ThisComponent.getCurrentController.setActiveSheet( ThisComponent.Sheets( 0 ) ) S_file = ConvertToURL( "D:\exported.csv" ) ThisComponent.StoreToURL( S_file, AAS ) end sub Steps to Reproduce: 1.write a macro for exporting a sheet to a .CSV file 2.write more than 10 rows of some data to the 1st sheet 3.call macro for exporting sheet to .CSV file 4.open .csv file and check some last rows are missing 5.change number of rows in the sheet 6.call macro for exporting sheet to .CSV file 7.open .csv file and number of exported lines in the .CSV file is always the same Actual Results: When using StoreToUrl(), number of lines to be exported from the source sheet and number of exported lines in the .CSV file is not the same. Expected Results: When using StoreToUrl(), number of lines to be exported from the source sheet and number of exported lines in the .CSV file shold be the same. Reproducible: Always User Profile Reset: No Additional Info: none
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Dear lubomir.kovac, 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
It is not possible to create a new file for this bug to appear.
Works fine for me. Do you still see this with version 24.2? Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 07468c71ad47e027bdadbf2cdf35e903734a8078 CPU threads: 2; OS: Windows 11 X86_64 (10.0 build 22621); UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-GB Calc: threaded Version: 7.5.6.0.0+ (X86_64) / LibreOffice Community Build ID: f0e825382a76d685998be702ed551a00b73476a5 CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Jumbo
Lubomir: you set this to unconfirmed, but did not answer my question from comment 4, so I'm setting it back to needinfo.
Dear lubomir.kovac, 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