Setting Up a DataView Actions Filter

To build a filter to use on a DataView action:

  1. In the DataView Actions Filter Setup form, select the property of the IDO to be evaluated.

    For a Run DataView action type, this is the primary collection of the predefined DataView. For a Run Form action type, this is the primary collection on the target form.

    If this form is launched from the DataView Actions Setup form with a Run Form action type selected, the Property Name drop-down list shows all bound and derived properties in the IDO, not just those that are bound to the form.

  2. Select the operation method.

    If you select Is Null or Is Not Null, do not specify anything in the Comparison field and value.

  3. Select the comparison type:
    • Literal: The property is compared to a specified value.
    • Source DataView Property: Use this IDO property from the source DataView (where the user right-clicked) to filter the form or DataView that is opened by the action. For example, if the user right-clicks on a customer number and selects an Action menu option that opens the Customer Orders form, the additional filter created here could include the Ship To (CustSeq) property as part of the filter, like this: CustSeq=FP(CustSeq).
    • Target DataView Property: Use this IDO property from the target DataView (the DataView that will be opened by the action) to filter the DataView that is opened. For example, if the action opens a Customer Order Lines DataView, this filter could show only unfilled order lines, where QtyOrdered > QtyShipped.
    • Target Form Property: Use this IDO property from the target form (the form that will be opened by the action) to filter the form that is opened. For example, you could add QtyShipped < QtyOrdered to the filter when the action opens the Customer Order Lines form.
  4. If you selected Literal, specify a comparison value.
  5. Click Add to translate the information from the fields into filter syntax and show the filter expression in the editor box.
  6. Click OK to save changes.

Notes:

  • Click Remove to clear the content in the editor box.
  • For complex comparison logic, it may be necessary to manually edit the text in the editor box to add parentheses around or and and statements, to ensure that the filter is evaluated properly.
  • To better understand how filters can be used, look at the vendor level DataViews that are provided as part of the application.