Bug 105468 - .uno:DataSort basic command doesn't accept all sort options usable in ui dialog
Summary: .uno:DataSort basic command doesn't accept all sort options usable in ui dialog
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Macro-Recording
  Show dependency treegraph
Reported: 2017-01-21 17:55 UTC by Paolo Benvenuto
Modified: 2024-07-13 03:14 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Paolo Benvenuto 2017-01-21 17:55:25 UTC
I created a macro in order to sort a multicolumn range, and I recorded the sort command setting 6 sort columns.

However when I looked at the recorded macro, I discovered that only 3 sort columns are recorded.

I tried adding more columns, following the convention I saw for the previous columns, but the interpreter didn't accept them.

I think more columns should be allowed in the basic macro. I think it's a simple bug
Comment 1 Paolo Benvenuto 2017-01-21 21:17:49 UTC
surely related to bug #105301
Comment 2 Buovjaga 2017-01-25 11:01:06 UTC
(In reply to Paolo Benvenuto from comment #1)
> surely related to bug #105301

Yeah, it seems this report depends entirely on bug 105301, so do you see any benefit on keeping this open?
Comment 3 Paolo Benvenuto 2017-01-25 13:10:50 UTC
Yes, it must remain open, because it's not obvious that solving the other bug solves this too
Comment 4 raal 2017-07-28 19:37:59 UTC
I can confirm with Version:
Build ID: e0bafa78e3ad0df397d78cd65ad19bd5b07dc5f2
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-07-20_22:42:49
Comment 5 QA Administrators 2018-07-29 02:38:58 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2020-07-29 03:54:12 UTC Comment hidden (obsolete)
Comment 7 Andreas Heinisch 2021-01-11 19:58:38 UTC
Could you explain to me, how you exactly you recorded the macro? I cannot reproduce the error. Thank you!
Comment 8 QA Administrators 2024-07-13 03:14:55 UTC
Dear Paolo Benvenuto,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team