In R3 2016 release there was a major change in how each definition item property values are read and cached (that was an optimization change). For more details please check Changes on items in report events are not applied
Based on how you access them, there are two available approaches:
1. If you change the item definitions inside events
those changes will no longer be applied. The correct approach is to get the processing item
- examples are provided the above mentioned article and Report Events
Instead, you need to access the processing report parameters as demonstrated in this example
There is an option to revert back to the old behavior (with the cost of the optimizations in rendering that were introduced) by adding a cacheDefinitionProperties
setting in the application configuration file - an example is provided in mentioned in the beginning KB article.
2. In case you are not accessing the parameter values in events.
The recommended approach of assigning data source and parameters in the report definition are shown in our Invoice example report
, which contains a sub-report named SalesOrderDetails, passing the Sales order ID as a parameter.
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items