Bug 122026 - BASE - Problems in Report design
Summary: BASE - Problems in Report design
Status: RESOLVED DUPLICATE of bug 120152
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
6.1.3.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-11 16:51 UTC by clemente.s.moreira
Modified: 2018-12-11 19:45 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description clemente.s.moreira 2018-12-11 16:51:56 UTC 
Description:
Hello
With this new version (Versão: 6.1.3.2 (x64)), I can't no longer insert fields from a table or qwery in the report design.
I select the field and do Insert, but nothing happens.
Also the sort buttons do not work.

Steps to Reproduce:
1.open Report design
2.Click teh Insert Field button
3.Select on field an do insert


Actual Results:
Nothing happens

Expected Results:
The field must appear on the report (desheet 


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: pt
Module: ReportDefinition
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no
[My Information]
OS: Windows (Win10)
OS is 64bit: YES: x64-based processor (intel i5)
[From Help - About LibreOffice]
Versão: 6.1.3.2 (x64)
ID da versão: 86daf60bf00efa86ad547e59e09d6bb77c699acb
Processos do CPU: 4; SO: Windows 10.0; Gestão da interface: padrão; 
Configuração regional: pt-PT (pt_PT); Calc: group threaded
Comment 1 Robert Großkopf 2018-12-11 19:45:43 UTC 
This seems to be a duplicate of bug 120152. Have tested with LO 6.1.2.1 and LO 6.1.3.2 - both will fail. But with LO 6.1.4.1 you could add fields to the report again.

I will set this as duplicate of bug 120152. Seems to be fixed for next version.

*** This bug has been marked as a duplicate of bug 120152 ***