Page 1 of 1
Two new errors upgrading to 2019.3.6 from 2019.3.5
Posted: Tue Oct 01, 2019 5:36 pm
by terje.pedersen
We are forced to upgrade to 2019.3.6 because of the "print to pdf" bug with the newest release of Chrome on Windows. The new 2019.3.6 solves two bugs we currently have, but the new release gives us two new bugs so I can't publish this version in production in our systems. I have also tested 2019.3.5 and these two new bugs below isn't present in 2019.3.5 but in 2019.3.6
a) Error message in the viewer. Only place I can find "pageNumbers" is the PageNumbers in the localization file nb-NO.xml we use.
- stimulsoft-error1-pagenumbers.png (9.51 KiB) Viewed 3473 times
b) Can't download anything more with Stimulsoft.Report.Export.StiPdfExportService / Stimulsoft.Report.Export.StiHtmlExportService etc. The html is empty and the PDF file generated is not able to open and is a lot smaller than the version generated with 2019.3.5 (7kB vs 70kB).
- stimulsoft-error2-empty-html.png (10.52 KiB) Viewed 3473 times
Re: Two new errors upgrading to 2019.3.6 from 2019.3.5
Posted: Wed Oct 02, 2019 6:40 am
by Lech Kulikowski
Hello,
Please try to use the renderAsync() method instead of the render().
Thank you.
Re: Two new errors upgrading to 2019.3.6 from 2019.3.5
Posted: Wed Oct 02, 2019 10:28 am
by terje.pedersen
Thanks. The renderAsync solved both those two issues.
But it didn't take long before another one appeard in one of our reports which is now with 2019.3.6 just showing this and no content
- stimulsoft-sti-of-null.png (5.15 KiB) Viewed 3454 times
Re: Two new errors upgrading to 2019.3.6 from 2019.3.5
Posted: Wed Oct 02, 2019 12:30 pm
by terje.pedersen
Another one, its now a difference in rendering of dates. In the JS version its now wrong, but the .NET version its working ok. The time has also been different.
2019.3.6 .NET
- stimulsoft-date-format-dotnet-2019.3.6.png (39.26 KiB) Viewed 3452 times
2019.3.6 JS
- stimulsoft-date-format-js-2019.3.6.png (21.07 KiB) Viewed 3452 times
Re: Two new errors upgrading to 2019.3.6 from 2019.3.5
Posted: Thu Oct 03, 2019 12:21 am
by terje.pedersen
Have found what is causing the date to be formatted as 18/01/2019 in JS version.
If you in the designer have chosen format "03.10.2019" it becomes "03/10/2019" with JS version.
If you choose "*03.10.2019" it becomes "03.10.2019".
In the mrt file choosing "03.10.2019" its saved as:
<TextFormat Ref="53" type="DateFormat" isKey="true">
<StringFormat>dd/MM/yyyy</StringFormat>
</TextFormat>
In the designer preview its shown correctly.
- stimulsoft-date-format-not-working.png (18.92 KiB) Viewed 3438 times
Re: Two new errors upgrading to 2019.3.6 from 2019.3.5
Posted: Fri Oct 04, 2019 2:34 pm
by Lech Kulikowski
Hello,
We have made some fixes with DateTime formats. Please check the 2019.3.7 build
Thank you.