Decimal Precision issue for 2 decimal points

Stimulsoft Reports.WEB discussion
anishravindran
Posts: 22
Joined: Fri Mar 23, 2018 5:53 am

Decimal Precision issue for 2 decimal points

Post by anishravindran »

Team,

When a report is designed for 2 decimal precision for any format like Number or Percentage the report rendering is inconsistent in different environments. For example I get exactly two decimals points in local environment but I may get three decimal points once the same template is deployed in cloud platform.

This is happening only when we put 2 decimal points in formatting. If I put any other value other than two it is working fine.

So to find what is happening I just tried different options in decimal precision and I happen to notice that when 2 decimal points are given the tag is not written to the MRT file. Please refer below for 2 decimal and 3 three decimal options for the same field.

I am using Stimulsoft 2018.2.1 version

For 3 decimal points:-

<TextFormat Ref="22" type="NumberFormat" isKey="true">
<DecimalDigits>3</DecimalDigits>
<GroupSeparator>,</GroupSeparator>
<NegativePattern>1</NegativePattern>
<UseLocalSetting>False</UseLocalSetting>
</TextFormat>

For 2 decimal points:-
<TextFormat Ref="22" type="NumberFormat" isKey="true">
<GroupSeparator>,</GroupSeparator>
<NegativePattern>1</NegativePattern>
<UseLocalSetting>False</UseLocalSetting>
</TextFormat>

Looks like because of this the report rendering is inconsistent. I manually added this tag to the report fields and deployed to cloud environment and then it worked for me.

Let me know if you need more information.

Please can you help to fix this? Thanks in advance.
Attachments
Stimulsoft_DecimalIssue_2.png
Stimulsoft_DecimalIssue_2.png (38.17 KiB) Viewed 3833 times
Stimulsoft_DecimalIssue_1.png
Stimulsoft_DecimalIssue_1.png (36.97 KiB) Viewed 3833 times
anishravindran
Posts: 22
Joined: Fri Mar 23, 2018 5:53 am

Re: Decimal Precision issue for 2 decimal points

Post by anishravindran »

Team,

Did you get a chance to look into this? Thanks in advance.

Anish
Lech Kulikowski
Posts: 6197
Joined: Tue Mar 20, 2018 5:34 am

Re: Decimal Precision issue for 2 decimal points

Post by Lech Kulikowski »

Hello,

We have reproduces the issue. We are working on this issue.
We need some time to fix that issue.

Thank you.
anishravindran
Posts: 22
Joined: Fri Mar 23, 2018 5:53 am

Re: Decimal Precision issue for 2 decimal points

Post by anishravindran »

Team,

Please can you let me know if this fix was released? Thanks in advance.
Lech Kulikowski
Posts: 6197
Joined: Tue Mar 20, 2018 5:34 am

Re: Decimal Precision issue for 2 decimal points

Post by Lech Kulikowski »

Hello,

That issue was fixed in last release. Please check release 2018.2.3

Thank you.
simader
Posts: 5
Joined: Mon Jun 21, 2021 12:22 pm

Re: Decimal Precision issue for 2 decimal points

Post by simader »

Hello,
I have again the same problem with the newest Stimulsoft nuget version.

I just leave the default option on Numeric.

Please fix this bug.

Best,
Attachments
stimulsoft problem.png
stimulsoft problem.png (55.35 KiB) Viewed 2237 times
Lech Kulikowski
Posts: 6197
Joined: Tue Mar 20, 2018 5:34 am

Re: Decimal Precision issue for 2 decimal points

Post by Lech Kulikowski »

Hello,

Please clarify which product and version are you use?

Thank you.
simader
Posts: 5
Joined: Mon Jun 21, 2021 12:22 pm

Re: Decimal Precision issue for 2 decimal points

Post by simader »

We use Stimulsoft.Reports.Engine.NetCore in version 2021.3.3

If we render the same report under .netFullFramework it appears with two digits precision
Lech Kulikowski
Posts: 6197
Joined: Tue Mar 20, 2018 5:34 am

Re: Decimal Precision issue for 2 decimal points

Post by Lech Kulikowski »

Hello,

We couldn't reproduce the issue on our samples.
Please send us a sample project that reproduces the issue for analysis.

Thank you.
simader
Posts: 5
Joined: Mon Jun 21, 2021 12:22 pm

Re: Decimal Precision issue for 2 decimal points

Post by simader »

Hello,

It seems that the default behaviour in Microsoft .Net 5 changed.
https://github.com/dotnet/runtime/issues/45695

Thats why, we get now 3 digits and before 2 digits.

Best,
Andreas
Post Reply