Page summary problem

Stimulsoft Reports.WPF discussion
Post Reply
llysyganicz
Posts: 55
Joined: Thu Mar 12, 2015 10:06 am

Page summary problem

Post by llysyganicz »

We have problem with page summary of report (attachment). Problem occures in version 2016.1 and newer (prereleases). In 2015.2 works fine.
Attachments
Summary.zip
(126.15 KiB) Downloaded 209 times
HighAley
Posts: 8431
Joined: Wed Jun 08, 2011 7:40 am
Location: Stimulsoft Office

Re: Page summary problem

Post by HighAley »

Hello.

We have reproduces the issue.
There was some changes in aggregation methods.

Thank you.
llysyganicz
Posts: 55
Joined: Thu Mar 12, 2015 10:06 am

Re: Page summary problem

Post by llysyganicz »

Hello,

I checked latest version (2016.1.26) and problem still occures.
When this issue will be fixed?
Alex K.
Posts: 6488
Joined: Thu Jul 29, 2010 2:37 am

Re: Page summary problem

Post by Alex K. »

Hello,

We will inform you on this topic when this issue will be fixed.

Thank you.
llysyganicz
Posts: 55
Joined: Thu Mar 12, 2015 10:06 am

Re: Page summary problem

Post by llysyganicz »

Hello,

I see that you will release new version soon.
Is this problem solved in new version?
HighAley
Posts: 8431
Joined: Wed Jun 08, 2011 7:40 am
Location: Stimulsoft Office

Re: Page summary problem

Post by HighAley »

Hello.

Yes, there was made an improvement of your issue.
Please, check our official build when it will be available.

Thank you.
llysyganicz
Posts: 55
Joined: Thu Mar 12, 2015 10:06 am

Re: Page summary problem

Post by llysyganicz »

I checked offical build. Problem still occurs.
llysyganicz
Posts: 55
Joined: Thu Mar 12, 2015 10:06 am

Re: Page summary problem

Post by llysyganicz »

Could you give an approximate date when this problem will be fixed?
Or maybe, is it a solution to modify template and code to calculate sum properly?
HighAley
Posts: 8431
Joined: Wed Jun 08, 2011 7:40 am
Location: Stimulsoft Office

Re: Page summary problem

Post by HighAley »

Hello.

Sorry for this problem.
We have fixed the initial issue, but there was a large refactoring that cause other issue.
We have found and fixed it. You sample works right now.
The fix will be available in our next build 2016.2.1.

Thank you.
Post Reply