1
Discussion | Обсуждение / Re: Nestled grouping
« on: September 27, 2016, 11:20:29 pm »
Ok, I'll be waiting.
Thank you
Thank you
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
3
Discussion | Обсуждение / Nestled grouping
« on: September 24, 2016, 07:17:46 pm »
Hi, how are you doing?
First, I need to say LimeReport is very good tool. I've tested other 4 or 5, and LR is the best one.
However, for my application, I need some help. Is it possible to nestle grouping headers?
My query returns 3 levels of grouping (e. g.: trip section > trip > bus > driver).
How could I do it?
LR Designer band menu enables "GroupHeader" option when I select a previous group header.
However, this second group header is shown between the first one (attachment 1) and data band,
instead of above both -- since the first one is actually related to data band;
When I render this report, only one group works, while the other one remains lost below data band lines (attachment 2).
Well, it would be awesome if nestled group headers could work properly. Is it a bug? Or am I doing something wrong?
Obs.: I'm using external datasource implementing QAbstractDataModel interface approach. It would be great if I could keep this way
Thanks in advance, and greetings from Brazil.
Edilson Castro
[вложение удалено администратором]
First, I need to say LimeReport is very good tool. I've tested other 4 or 5, and LR is the best one.
However, for my application, I need some help. Is it possible to nestle grouping headers?
My query returns 3 levels of grouping (e. g.: trip section > trip > bus > driver).
How could I do it?
LR Designer band menu enables "GroupHeader" option when I select a previous group header.
However, this second group header is shown between the first one (attachment 1) and data band,
instead of above both -- since the first one is actually related to data band;
When I render this report, only one group works, while the other one remains lost below data band lines (attachment 2).
Well, it would be awesome if nestled group headers could work properly. Is it a bug? Or am I doing something wrong?
Obs.: I'm using external datasource implementing QAbstractDataModel interface approach. It would be great if I could keep this way
Thanks in advance, and greetings from Brazil.
Edilson Castro
[вложение удалено администратором]
Pages: [1]