Issue 124504 - Base Report Wizard Sort
Summary: Base Report Wizard Sort
Status: CONFIRMED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: 3.4.1
Hardware: All All
: P3 Normal with 1 vote (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-25 00:21 UTC by John Meyers
Modified: 2014-04-02 18:31 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: 4.1.0-dev
Developer Difficulty: ---

Attachments
Fake Amateur Radio club member database (39.37 KB, application/vnd.sun.xml.base)
2014-03-25 00:21 UTC, John Meyers 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description John Meyers 2014-03-25 00:21:19 UTC 
Created attachment 82964 [details]
Fake Amateur Radio club member database

1. In Base, create a Query ending with --- ORDER BY "name" ASC [attached Query = "RosterName"]
2. Use the Base Report Wizard to create a report using the Query
3. Expected results: Report containing fields specified in Query and sorted as specified by ORDER BY in the Query
4. Actual results: Report containing the fields specified by the Query in the order specified by the Query but SORTED by the Primary Key of the Table.
In this case, in "Step 4, Sort Options" of the Report Wizard, the sort option was left as "undefined". [attached Report = "RosterName1"]
5. If you create a new report using the Report Wizard and the same Query but, in this case, in "Step 4, Sort Options" enter the name of the field you want the Report sorted by and absolutely nothing will be extracted from the table. [attached Report = "RosterName2"]
Comment 1 mroe 2014-03-25 09:44:30 UTC 
I can confirm this behaviour.

But I noticed a other problem: If I edit a query in the sample odb in SQL view I see the ORDER statement. If I change to design mode or edit the query directly in design mode the ORDER statement is lost. Bt I don't know if this is the underlying reason for the reported issue.

-- 
AOO410m14(Build:9760) - Rev. 1573601
214-02-28 10:30 - Linux i686
Comment 2 j.nitschke 2014-04-02 12:09:33 UTC 
bug already visible in AOO 3.4.1
Comment 3 Stefan 2014-04-02 18:31:53 UTC 
bug already visible in AOO 4.0.1