Ad Hoc Reporting

This feature allows the automatic addition of User Defined Fields to the Ad Hoc views.

In each view, each object's User Defined Fields are added under their own placeholder, which is called <Object Name> UDFs.

The User Defined Fields are available in the following categories:

• The same User Defined Fields are also available in the Filtering section.
• The functions available on the fields are based on the UDF type (text, numeric ...).
• Multi-value user defined fields are not included in the views.
• The Field Name to display for the UDF in the Field Name combo-box in the report designer is set to the Display Name of the UDF, as defined on the UDF Edit page.
• Upon selecting a UDF in the report, the Display name is set to the Display Name of the UDF, as defined on the UDF Edit page.

• Upon deleting a User Defined Field or upon deleting a User Defined Field Association, the validation, which ensures that the UDF is not added as a field or filter in an Ad Hoc report, is bypassed.
• Upon previewing an Ad Hoc report through the application or through the View tab of the Report Edit page, when the report contains a UDF as a field or filter and the UDF no longer exists (UDF deleted or UDF association to the object deleted), the missing fields are removed from the report.
  • If the removal of the fields does not cause an error with the report design, the report displays.
  • If the removal of the fields causes an error with the report design, a message displays directly on the page that reads,
    "The following fields have been removed from the report because they no longer exist:
    Field Name 1
    Field Name 2
    The report must be redesigned to account for these changes."
• Upon editing a report or saving a report, when the report contains a UDF as a field or filter and the UDF no longer exists (UDF deleted or UDF association to the object deleted), the fields are automatically removed from the report.
  • If the removal of the fields does not cause an error with the report design, a dialog box displays with a message that reads,
    "The following fields have been removed from the report because they no longer exist:
    Field Name 1
    Field Name 2
    <…>"
  • If the removal of these fields causes an error with the report design, a dialog box displays with a message that reads,
    "The following fields have been removed from the report because they no longer exist:
    Field Name 1
    Field Name 2
    The report must be redesigned to account for these changes."

This feature allows the date filter to be blank on an Ad Hoc report if it is to be displayed on the report. Otherwise, a date parameter is required.

1. When a date filter is set to display on the report, the value can be set to blank.
   • The value in column ‘Parameter 1' behaves in the following manner in relation to the Display checkbox:
     1. When there is no value in the parameter field (blank):
        1. With Display option checked, the field remains blank.
        2. With the Display option unchecked, the field populates with the ‘YYYY-MM-DD'.
     2. When there is a value in the parameter field, the checking or un-checking of the Display option has no effect on the value.
   • The ‘YYYY-MM-DD'value should only appears when the Display option is not selected.
2. When the date filter is set to display on the report and the field is set to blank, the date filter on the resulting report is blank, forcing the User to select a date.
3. When the date filter is blank on the report and the report is previewed, a message displays, indicating that a date parameter is required, "Some of the required fields are missing."
   • The cursor is automatically placed in the date parameter.
4. To continue, click OK.

Facilitates the use of the IN operator when any of the multiple Filter Parameters contain either single or double quotes, thereby allowing the filtering of AdHoc Reports with such special characters.

When using the IN operator, the following formats can be used to ensure that the system reads Filters Parameters, with the following special characters, correctly and returns the expected values: