This page lists issues that you may experience with reports that were imported from Dynamic Reports to Dynamic Reports 2, and suggestions on how to fix them. (Last updated January 27, 2020)
Issue: Viewing or previewing the report displays the message “DataSet xx referenced in the report could not be found.”
This can happen if a Retrieval’s Statistics Location setting is changed after statistics are added to the report, because the Statistics Location setting affects the names of the Datasets that are provided to the report.
Resolution: To resolve this issue, you must either change the Statistics Location back to its original setting (indicated by the name of the Dataset), or else update all references to the original dataset so that they now point to the current dataset that includes the desired statistic.
Issue: An Expression that worked in Legacy Dynamic Reports does not work in Dynamic Reports 2.
In the Legacy Dynamic Reports module, when an Expression referenced a field that did not always return a string value, that Expression may have automatically cast that field’s value as a string. However, this automatic cast to string does not happen in Dynamic Reports 2.
Resolution: Modify the Expression so that it calls ToString(field_value) instead of just field_value.
For example, the Expression iif(Fields.Item("my_field").Value = "Uni", ... worked in Legacy Dynamic Reports, but in Dynamic Reports 2 it should be changed to iif(ToString(Fields.Item("my_field").Value) = "Uni", ... to work correctly.
Issue: An Expression that worked in Legacy Dynamic Reports does not work in Dynamic Reports 2.
In the Legacy Dynamic Reports module, date/time functions such as DateAdd() allowed you to use an interval argument such as DAY – for example, DateAdd(DAY, 1, [@HighDate]) – perhaps automatically completing the interval to its full enumeration as DateInterval.Day .
Resolution: Modify the Expression to use a valid interval argument, such as “d” for day.
For example, the Expression DateAdd(DAY, 1, [@HighDate]) worked in Legacy Dynamic Reports, but in Dynamic Reports 2 it should be changed to DateAdd("d", 1, [@HighDate]) to work correctly.
Issue: Object spacing looks correct on the layout area when designing the report but gets cut off when viewing or previewing the report.
Resolution: To resolve this issue, find the Report property for ConsumeWhiteSpace and change it to False.
