2018.1.2: DataBands inconsistent behaviour (Bug)
Re: 2018.1.2: DataBands inconsistent behaviour (Bug)
Hello,
In this case, you should set the following option:
StiOptions.Engine.PrintIfDetailEmptyNesting = true;
By default, the PrintIfEmpty property checks only first elements for each level and if one of them empty - all level will hide.
With this option, all levels will check.
Thank you.
In this case, you should set the following option:
StiOptions.Engine.PrintIfDetailEmptyNesting = true;
By default, the PrintIfEmpty property checks only first elements for each level and if one of them empty - all level will hide.
With this option, all levels will check.
Thank you.
Re: 2018.1.2: DataBands inconsistent behaviour (Bug)
Thanks Alex, that seems to be working. Seems like it should be default on. I can't think of a scenario where you would need it false by default.
Although it works now, any headers are still shown if the data band is empty. Why is it so? Header.PrintIfEmpty property is not working.
Header --> "Class" is shown (correct behaviour) Header --> "Class" is shown (incorrect behaviour - should be hidden)
Although it works now, any headers are still shown if the data band is empty. Why is it so? Header.PrintIfEmpty property is not working.
Header --> "Class" is shown (correct behaviour) Header --> "Class" is shown (incorrect behaviour - should be hidden)
- Attachments
-
- Report1.mrt
- (12.07 KiB) Downloaded 331 times
Re: 2018.1.2: DataBands inconsistent behaviour (Bug)
Hello,
We need some additional time to check the issue.
Thank you.
Ticket Reference: #5561
We need some additional time to check the issue.
Thank you.
Ticket Reference: #5561
Re: 2018.1.2: DataBands inconsistent behaviour (Bug)
Hi there, any updates on this one?
Re: 2018.1.2: DataBands inconsistent behaviour (Bug)
Hi Vineet,
Thank you for investigating the problem further and we managed to reproduce it. We will update you once we have more information on how this could be solved.
Thank you,
Edward
Thank you for investigating the problem further and we managed to reproduce it. We will update you once we have more information on how this could be solved.
Thank you,
Edward
Re: 2018.1.2: DataBands inconsistent behaviour (Bug)
Hi Edward, was this fixed in the latest release? Can you give me a time frame on when this could be released?
Re: 2018.1.2: DataBands inconsistent behaviour (Bug)
Hi Vineet,
Sorry for the delay, the ticket to fix the problem is still with our dev team, and actually, the change requires some significant efforts to tweak the report engine, so it was not prioritized for this reason yet.
And also we are considering to set the option
to equal true by defalut.
I think we need at least couple of months to get this sorted. We will update this ticket once the problem is solved.
Thank you,
Edward
Sorry for the delay, the ticket to fix the problem is still with our dev team, and actually, the change requires some significant efforts to tweak the report engine, so it was not prioritized for this reason yet.
And also we are considering to set the option
Code: Select all
StiOptions.Engine.PrintIfDetailEmptyNesting = true;
I think we need at least couple of months to get this sorted. We will update this ticket once the problem is solved.
Thank you,
Edward
Re: 2018.1.2: DataBands inconsistent behaviour (Bug)
Just checking if there was any progress on this.
Re: 2018.1.2: DataBands inconsistent behaviour (Bug)
Hi Vineet,
Unfortunately, that issue has not been fixed yet. We will let you know in this topic, once it is fixed.
Thank you,
Edward
Unfortunately, that issue has not been fixed yet. We will let you know in this topic, once it is fixed.
Thank you,
Edward