Corrected item |
What it means |
Customize Changes Sample Filter Match Behavior |
Filter Match option saved in the Managed Document Sample Load options are ignored when customizing a report. The Sample Load options in the document have a Sample Filter set to “All Filters Specified” that are applied correctly when printing the report directly in Web. However, if you click ‘customize’, even without making any changes to the template, the printed report does not have the correct Sample filters applied. Rather then using the set “All Filters Specified”, the customized Web report uses the filter option “At least one Filter specified” resulting in a report with unwanted Samples. |
Customize Error with Selected Samples Set in Managed Document |
When the Sample Load method saved in the Managed Document is set to Selected Samples, customizing the report before printing results in an error message stating the query could not be executed. Note: See a Known Issue related to this bug on here. |
Customize Ignores Sample Label Filter |
Label Filters saved in the Managed Document Sample Load options are ignored when customizing a report. Submitting the report directly from the Templates page applies the Label filter to the Samples loaded in the report. |
Customize with Query Date Sample Load Options Prints Empty Report |
When Query Date is set in 'Use Query Date' Customize for this template prints empty reports (Submit works fine). Customizing a report that includes documents using Sample Load options with Query Dates results in an empty printed report. The issue is seen when the following Sample Load methods are set in the document:
|
Multiple Sample Filters Not Working for Customized Query |
When multiple sample filters are selected in a customized query, the printed report does not retrieve the correct data. |
Sorting on "Date" Field on Web Reports page is incorrect |
When trying to sort the Web Reports grid on the Date column, it appears to be doing an "alphabetical" sort instead of a Date/Time sort. For Example: The date "05/01/2018 15:00:00" sorts as newer than "04/01/2019 15:00:00" even though it is a year older. |
Can we improve this topic?