Posted 2 September 2020, 1:06 am EST
Hi,
We have implemented an Active Reports 14 reporting API (using your dotnet core sample as a base) using “GrapeCity.ActiveReports.Aspnetcore.Viewer” nuget package on version “14.2.2495”.
Then we implemented the new Active Reports 14 JSViewer (also v 14.2.2495) on our front-end with the code being something like this:
```
_scope.viewer = GrapeCity.ActiveReports.JSViewer.create({
element: ‘#viewerContainer’,
reportService: {
url:
${_scope.permissions.reportAPIEndPoint}api/reporting
,securityToken: ‘42A9CD80A4F3445A9BB60A221D042FCC’
},
availableExports: [‘Xml’, ‘Pdf’],
displayMode: ‘Continuous’,
reportLoaded: (reportInfo) => { },
action: (actionType, actionParams) => { },
documentLoaded: () => { },
error: (error) => {
if (error.message) {
console.log(“Internal error! Please ask administrator.”);
console.log(error.message);
}
}
});
And to run the report we just call:
```
_scope.viewer.openReport(_config.reportType, reportParameters);
Everything works great in theory, but I found out that when the displayMode is continuous only the first 4 pages have content, the remaining pages are present but they are all blank. If I use the viewer tools to export as PDF or print the report using the viewer tools, all the pages appear. E.g: If I run a report with 10 pages, after the “documentLoaded” event gets triggered the pages start to appear until I end up with a viewer with 4 rendered pages plus 6 blank ones.
Am I doing something wrong? Can you replicate it?
Thanks in advance.
Best Regards,
Ricardo Pereira