I am having a bit of a problem with Preview and Drilldown.
The situation that we are in is that we have a solution that uses Crystal Report for reporting. We do want to phase that out and have been rebuilding few reports with LL. We however would like to continue to build and produce the report data on our server and send streamed preview files to the client. We do not want to store report “projects” on each client and we also like to minimize the footprint on each client.
The first attempt was to display reports on the client using the built in WPF control. That was OK until we found that Drilldown is not possible. Having searched for a solution for that I ended up noticing that this was not possible at the moment (have lost the link to the forum answer).
Then we looked into viewing the report in the Standalone viewer and got help in making the preview “drillable” - as suggested I have marked the report main property as “Embed Drilldown Report” and preview generated on the client makes the drilldown possible.
BUT when generating the preview file in our server we get an Exception. See below. Is it possible to generate the preview file in the server without any user interaction?
As far as I can see we have not set any property to invoke user actions, see code snippets below.
(combit Support - Christian Rauchfuß)
We tried to reproduce the mentioned behavior with the MVC Web Reporting Sample - without success. The sample is part of your List & Label installation:
..\combit\LL28\Samples\Microsoft .NET\.NET 6\ASP.NET\MVC Web Reporting Sample ..\combit\LL28\Samples\Microsoft .NET\.NET Framework 4\ASP.NET\C#\MVC Web Reporting Sample
Is it reproducible on your side using the samples? Analyzing the log file (thanks for uploading) a possible reason could be that “IncrementalPreview” is disabled. Please make sure that IncrementalPreview is set to true LL.IncrementalPreview = true; (which is the default). It should not be disabled. In that case LlPreviewDisplay() needs to be executed to open the *.LL file, but that makes no sense in a server environment.
@Arni_Reginsson Good news to this case: with the upcoming Service Pack Release 28.004 (estimated for the next two weeks) the described behavior is no longer reproducible and solved.
Let us know if the issue is also solved on your end after you have tested it with the Service Pack 28.004. If you need a new version earlier, please create a new support case at the Support Center we can provide the modules.
Thank you that’s good news indeed. I will then wait on our side to publish the newly added report until our “December patch” that is published before December 10th. That should give us enough time to double-check your solution in the upcoming Service Pack.