ObjectSession – the session is used as the storage, the report is stored as an object ObjectCache – the cache is used as the storage, the report is stored as an object (default value) None – caching is disabled, the report will be reloaded each time using the GetReport event It can take one of the following values of the StiServerCacheMode enumeration: Sets the time in minutes that the server will store the report since the last action of the viewer. For big reports, it is recommended to increase this value. Sets the response timeout from the server in seconds, after which an error will be generated. The default value of the property is null. If the property is not set, then the MVC project template will be used instead. Sets the route template that is returned when the report viewer actions are executed. If this property is not specified, then the current controller will be used to process requests. Specifies the name of the report controller for the report viewer. In addition, this action is used to load scripts and styles of the viewer. Specifies the name of the action method of basic viewer events and the processing actions of the viewer, such as printing and exporting a report, working with parameters, and interactivity, if these actions are not specified separately. Specifies the name of the action method to go to the specified view by clicking the Design button on the viewer panel. Specifies the name of the action method for the viewer to work with interactive operations, such as using parameters, dynamic sorting, collapsing, and drill-down. This is not relevant when viewing dashboards. Specifies the name of the action method of sending the report by email. Specifies the name of the action method of the export the report to the specified format. Specifies the name of the action method of report printing. If report caching is enabled, this action will be called only once when the report is requested or if the requested report is not found in the server cache. Specifies the name of the action method for preparing the constructed report. The reason why I don't use the traditional Master-Details approach is because I actually wanted to pass the next parent's Id as the parameter, i.e., Next(Datasource, "pId"), but it didn't work because of the exception "The name 'Next' does not exist in the current context", so I tried the above.Specifies the name of the action method for preparing the rendered report. So I wonder which the correct way to achieve this is, please help. 379e020c-0eea-477c-8f02-f7c6dc2b86b0 => Exception right awayĪnd repeated with the above Filters conditions but the result were the same. I also tried passing pId as a hard-coded value in Sub: I even tried a hard-coded value for the Filters: Expression: pId = new Guid(this.ToString()) => Blank Expression: pId = new Guid(this) => Exception Expression: pId = Guid.Parse(this.ToString()) => Blank Expression: pId = Guid.Parse(this) => Exception, obviously In Sub, I added a parameter named pId, and passed the parent's Id variable, then I've tried the following ways for the Filters of DataBand2: In Details, there is DataBand2 with the child source, and filter by parent's Id, let's call it pId. In Master, we have DataBand1 with the parent data source and a sub-report (let's call it Sub) that points to Details. Let's say there are 2 pages: Master and Details. I'm trying to make a master-details with sub-report by passing a Guid parameter but somehow it doesn't work as expected.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |