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.
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).
Two new errors upgrading to 2019.3.6 from 2019.3.5
-
- Posts: 80
- Joined: Thu Aug 18, 2016 7:29 am
-
- Posts: 6245
- Joined: Tue Mar 20, 2018 5:34 am
Re: Two new errors upgrading to 2019.3.6 from 2019.3.5
Hello,
Please try to use the renderAsync() method instead of the render().
Thank you.
Please try to use the renderAsync() method instead of the render().
Thank you.
-
- Posts: 80
- Joined: Thu Aug 18, 2016 7:29 am
Re: Two new errors upgrading to 2019.3.6 from 2019.3.5
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
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
-
- Posts: 80
- Joined: Thu Aug 18, 2016 7:29 am
Re: Two new errors upgrading to 2019.3.6 from 2019.3.5
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 2019.3.6 JS
2019.3.6 .NET 2019.3.6 JS
-
- Posts: 80
- Joined: Thu Aug 18, 2016 7:29 am
Re: Two new errors upgrading to 2019.3.6 from 2019.3.5
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.
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.
-
- Posts: 6245
- Joined: Tue Mar 20, 2018 5:34 am
Re: Two new errors upgrading to 2019.3.6 from 2019.3.5
Hello,
We have made some fixes with DateTime formats. Please check the 2019.3.7 build
Thank you.
We have made some fixes with DateTime formats. Please check the 2019.3.7 build
Thank you.