gregg.dale_1

We have a field in a report where the text can be potentially very large. We would like to truncate the text to a reasonably displayable amount in our html version of the report, but would like the entire field value to display when export to .csv, .xls, or .xlsx Any suggestions on how we might achieve this?

Actually, the issue is larger in scope than just patterns. The report, when displayed, shows the column heading names and labels as defined in the appropriate locale property file, but when exported to xlsx and csv, it intermittently shows the default property values instead.

We have locale property bundles for our reports. When a report is run for a specific locale, date patterns, currency patterns and column headings and labels are determined by these property bundles. When we display the reports, this works great. It also works when we export to .PDF, .PPT, and .XML, but not when we export to .XLSX, .XLS or .CSV. Does anyone know why this would be?

To clarify, we use a data source expresion like ((OurCustomDataSource) ${REPORT_DATA_SOURCE}).getSomeSubsetDataSource()

We use a custom data source multiple times throughout our report. In order to get the subsets of data from the main datasource that we need for each area of the report, we add methods to our data source that return a custom datasource with the required data. We then define a datasource expression for each section that gets report data source, casts it as our custom data source class, and then calls the appropriate method to return get the necessary datasource for that section. this works great to initially fill and render our report, but when we sort any records, we get an error that says "SortedDataSource can not be cast to [our custom data source]". Does anyone know a way to guarantee retrieving the original data source? Here are some additional general details about our custom data source, to help understand why we are trying to do what we are doing. The data source calls rest enpoints to retrieve data for which we do not have direct db access. The data is returned as Json which we deserialize into POJOs. For a single report, we would prefer not to make multiple rest calls to retrieve the data. Some of the records contain subordinate records, so we add methods to return the subordinate records as a separate data source for the areas of the report where they are needed.