{"id":23763,"date":"2024-02-15T14:53:34","date_gmt":"2024-02-15T22:53:34","guid":{"rendered":"https:\/\/docs.extraview.com\/v25\/book\/query-filters-1\/"},"modified":"2025-03-06T11:49:27","modified_gmt":"2025-03-06T19:49:27","slug":"query-filters-1","status":"publish","type":"page","link":"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/querying-1\/query-filters-1\/","title":{"rendered":"Query Filters"},"content":{"rendered":"

Selecting query filters will impose restrictions upon the report being produced and return a set of results that matches the filters you set. For example, if you select the Status<\/strong> Open<\/em>, then only open issues will be displayed. Filters can be combined together, for example to show Open<\/em> issues for the product named XXX<\/em> that have been updated in the last 7 days.<\/p>\n

Filter Options<\/h3>\n

There are potentially four options that you can apply when creating filters.\u00a0 They do not all appear all the time according to how your administrator has configured the site and according to other options chosen.<\/p>\n

    \n
  • Filter Repeating Row Values<\/strong> – If present, this setting controls the results returned by the query when the query filters contain one or more repeating row fields.\u00a0 If checked, only the rows that match the filter criteria will be returned.\u00a0 If not checked, all repeating rows are returned by the query, where at least one row matches the filter criteria<\/li>\n
  • Filter Multi-Valued Field Values<\/strong> – When this option is checked, only the selected values in multi-valued list fields will be returned and displayed by the query, with all other values being suppressed<\/li>\n
  • Use Allowed Values in Filters<\/strong> – When this is checked, and you select a filter of a parent field in an allowed valued relationship and then subsequently select a filter of the child field in the allowed value relationship, only the valid child values will be displayed.\u00a0 This does not apply if you choose the child value before you choose the parent value.\u00a0 Also note this is not operable for the Business Area and Project fields, where all values will always be displayed<\/li>\n
  • Allow Additional Keyword Filters<\/strong> – If you check this option, then a keyword search box is displayed on the query output.\u00a0 You may enter additional search keywords within the search box on the output and these will be applied to the query and the query rerun with this keyword in addition to other filters.<\/li>\n<\/ul>\n

    Saving Filters for Future Use<\/h3>\n

    After setting up filters, you may want to save them for future recall.\u00a0 To achieve this, simply use the Save \/ Update Filters<\/strong> button.\u00a0 After saving the filters, you can recall them by selecting the name you used in the select list.\u00a0 Saved filters may be personal, and with permission you can save them to be shared by all users.\u00a0 These saved filters are independent of the reports saved within ExtraView, although you can include any saved filters within a report that you create.<\/p>\n


    \nSaving filter sets<\/cite><\/p>\n


    \nDialog for saving filters<\/cite><\/p>\n

    Using the popup dialog, you can also delete an existing filter set.<\/p>\n

    There are a few caveats on the use of saved filter sets:<\/p>\n

      \n
    • You may save either Standard or Advanced query filters, and on the Query screen, they will be recalled in the same manner they were saved<\/li>\n
    • Saved filters may only be recalled within a report editor, when you are in Advanced query mode.\u00a0 However, if you recall a set of Standard filters when you are in the Advanced mode, they are converted to Advanced filters<\/li>\n
    • When in a report editor, and you are in Advanced query mode, you may save your filters.\u00a0 If you are using a report hierarchy, the filters will be saved and can be used in any report editor, but will not be visible on the Query screen where reporting hierarchies are not supported<\/li>\n
    • Within a report editor, you can either recall a set of saved filters to replace all the current filters or can recall a set of saved filters to be inserted at any point within the filters currently chosen.\u00a0 To replace all the filters, simple choose from the * Saved Filter List *<\/strong>, to insert a filter choose the option within the field list titled * Insert Saved Filters *<\/strong>:\n


      \nSaved Filters within a Hierarchical Report Editor screen<\/cite><\/li>\n

    • You are warned if you are about to overwrite current filters with saved filters and given the opportunity to cancel.<\/li>\n<\/ul>\n

      Note<\/strong>: With Advanced Filters only, you can create saved filters where the fields have the value of * Any *<\/strong>.\u00a0 Whereas filters with the value of * Any *<\/strong> are typically ignored, and discarded when saved, there is a purpose to this feature.\u00a0 Consider that you might have a set of many filters that you want to use frequently as you create reports.\u00a0 These reports may or may not require all the filters, but you want them to be easily available when creating these reports.\u00a0 This provides a rapid way to construct the filters for these reports.<\/p>\n

      Standard Query Mode<\/h3>\n

      This allows you to choose the values for fields, upon which records are selected for the report. There is a set of filters available directly on the Query \/ Report screen, as well as from the screens where you prepare or edit reports that you save for future use. Typically, the Query \/ Report screen will show the most common filters you use, while the remaining screens show a more complete set of filters to which you have access. The fields available for your use are set up by your administrator.<\/p>\n


      \nStandard query filters<\/cite><\/p>\n

      If a query filter you select is the parent in a relationship, for example, the Module<\/em> field may be dependent on the Product<\/em> field, then the screen will refresh, and the child field will be populated with the valid entries for the parent you selected. If your administrator has enabled the feature that allows you to search for inactive users, an additional prompt appears on the screen alongside the Query Filters heading. This is a checkbox with the label Show Inactive Users<\/strong>. When you check this, all the selection lists of users, will be refreshed, and will show inactive as well as active users, allowing you to perform searches for users who were at one time, but are not currently, licensed users of ExtraView. Note that this feature only works in Standard Query mode and is not operable in Advanced Query mode.<\/p>\n

      Advanced Query Mode<\/h3>\n

      If your administrator has given you access to advanced query mode, you first will select an individual field<\/em> as the first filter to use in selecting individual records for the report. Then you select an operator<\/em> such as \u201cequals\u201d or \u201cgreater than\u201d, and then you select the value<\/em>. For example, a filter may be Status not equal to Closed.<\/strong> You may add as many filters as you like, with each one beginning with a conjunction such as \u201cand<\/strong><\/em>\u201d or \u201cor<\/strong><\/em>\u201d. Advanced filters take a little longer to set up than standard mode filters, but they allow much more flexibility to create a complex set of query filters.<\/p>\n


      \nAdvanced filter selection<\/cite><\/p>\n

      To add a new filter, use the button to the left of the filter. Note that you can add filters following any existing filter. If you want to delete an individual filter from a query, use the button. This will eliminate the filter. In advanced mode, you can set the same filter field multiple times and use the \u201cor<\/strong>\u201d value. For example, you may set two filters as follows:<\/p>\n

      \u00a0 Priority equals P1 or Priority equals P2<\/span><\/p>\n

      Alternatively, you can use the Expanded search mode described below and select multiple values from the Priority list.<\/p>\n

      Composing Complex Queries<\/h3>\n

      There is no limit to the number of filters that you may use to compose a query.\u00a0 One construct that is often useful is to be able to determine several filters grouped together.\u00a0 This is equivalent to using parentheses around parts of your query to separate these parts of the query from other parts of the query.\u00a0 The grouping of filters is achieved with the arrows \u00a0 beneath the and buttons.\u00a0 When you click on the right arrow to indent the filter, you are effectively adding parentheses around the indentation.\u00a0 As an example, consider:<\/p>\n

      <\/p>\n

      This query is equivalent to:<\/p>\n

      Area = Helpdesk
      \nAND (Last Modified during Last 4 weeks AND Assigned To = Bill Smith)
      \nAND
      \nArea = Customer Issues
      \nAND (Last Modified during Last 4 weeks and Assigned To = Bill Smith)<\/span><\/p>\n

      Advanced Query Filter Operators<\/h3>\n

      The operators that appear in the select list are sensitive to the display type of the field you select. This allows you to select operators that only make sense and are eligible for each field display type. This table shows how this operates:<\/p>\n\n\n\n\n\n\n\n\n
      Field display type<\/td>\nOperator values in Condensed Filter Mode<\/td>\nOperator values in Expanded Filter Mode<\/td>\n<\/tr>\n
      Currency, Decimal, Number<\/td>\nEquals
      \nGreater than
      \nLess than
      \nNot equal
      \nLess than or equal to
      \nGreater than or equal to
      \nEmpty
      \nNot empty<\/td>\n      		Equals
      \nGreater than
      \nLess than
      \nNot equal
      \nLess than or equal to
      \nGreater than or equal to
      \nEmpty
      \nNot empty<\/td>\n<\/tr>\n
      Checkbox, List, Pop-up, Tab, User<\/td>\nEquals
      \nNot equal<\/td>\n      		Equals
      \nIn
      \nNot equal
      \nNot In<\/td>\n<\/tr>\n
      Date, Day<\/td>\nEquals
      \nGreater than
      \nLess than
      \nNot equal
      \nLess than or equal to
      \nGreater than or equal to
      \nBetween
      \nEmpty
      \nNot empty
      \nDuring
      \nAfter
      \nBefore
      \nAfter or during
      \nBefore or during<\/td>\n      		Equals
      \nGreater than
      \nLess than
      \nNot equal
      \nLess than or equal to
      \nGreater than or equal to
      \nBetween
      \nEmpty
      \nNot empty
      \nDuring
      \nAfter
      \nBefore
      \nAfter or during
      \nBefore or during<\/td>\n<\/tr>\n
      Keyword<\/td>\nContains<\/td>\nContains<\/td>\n<\/tr>\n
      Text Field<\/td>\nEquals
      \nContains
      \nNot Equal
      \nEmpty
      \nNot Empty<\/td>\n      		Equals
      \nContains
      \nNot Equal
      \nEmpty
      \nNot Empty<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      The operator values are largely self-explanatory, but a word of explanation is needed about the Empty and Not Empty values. When a numeric field (currency, decimal or number display types) is stored in ExtraView, and you do not enter a value, zero is not the value stored. A null, or empty value is stored and these are treated differently. Therefore, searching for a value of empty will retrieve a different set of results that searching for a value of zero. Also, note that for Checkbox, List, Pop-up, Tab and User fields when in Expanded Query mode, there are two additional operators, In and Not In. These allow you to define a list of values to search for that must be present or must not be present. If you want to search for both empty and zero values, you may combine two filter conditions together, as exemplified by the following: Amount<\/strong> Equals<\/em> 0 or Amount<\/strong> is Empty.<\/em><\/p>\n

      Fields with a display type of Date and Day present different options for their values, according to whether an arithmetic operator such as equals<\/em> or greater than<\/em> is chosen, or a duration such as during <\/em>or after <\/em>is chosen.\u00a0 When an arithmetic operaor is chosen, you may enter dates into one or both date value fields.\u00a0 When you choose a duration, you are presented with a list of durations such as last month, this fiscal quarter <\/em>and this month to date.<\/em>\u00a0 ExtraView understands the meaning of these durations and will filter your query or report using the duration you select.<\/p>\n

      Advanced Query Filter Conjunctions<\/h3>\n

      The following conjunctions can be used between the different filters of a report:<\/p>\n\n\n\n\n\n\n\n\n
      Conjunction<\/td>\nMeaning<\/td>\n<\/tr>\n
      and<\/td>\nThis filter will ensure that both filter conditions on each side of the and<\/strong> are true, before including the results<\/td>\n<\/tr>\n
      or<\/td>\nThis filter will include results from the search, if either of the conditions on each side of the or<\/strong> is true<\/td>\n<\/tr>\n
      union<\/td>\nThis will take the results of all the filters together preceding the conjunction union<\/strong>, together with the results of the filters in the query following the conjunction and merge the results of both queries. For example, if you union<\/strong> two queries together, then you will see the results of both queries being returned on the report. The area within the red outline shows the results returned by two queries using the union<\/strong> conjunction.<\/td>\n<\/tr>\n
      minus<\/td>\nThis will take the results of the query filter(s) before the conjunction minus<\/strong>\u00a0and remove all results in common with the results of the query filter(s) following the conjunction. For example, if the query before the minus<\/strong> returns 100 rows, and the query following the minus returns 60 rows, 30 of which are to be found in the first part of the query, you will see 70 rows on the report that is generated. The area within the red outline shows the results returned by two queries using the minus<\/strong> conjunction.<\/td>\n<\/tr>\n
      intersect<\/td>\nThis will take the results of the query filter(s) before the conjunction intersect<\/strong>\u00a0and only display the results that are in common with the results of the query filter(s) following the conjunction. For example, if the first part of your query before the intersect<\/strong> returns 100 rows, and the second part of the query after the intersect<\/strong> returns another 100 rows, and 30 of the results are in both parts of the query, you will see these 30 rows returned on the report. The area within the red outline shows the results returned by two queries using the iintersect<\/strong> conjunction.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      If your ExtraView installation is running on a Microsoft SQL Server database prior to the 2005 version or on the MySQL database0 not all the conjunctions are functional due to database limitations. Only conjunctions that are known to work are operable. Check with your administrator if you are not certain which database is used by your company. If you have more than one union, minus<\/strong> or intersect<\/strong> conjunction in a query, then the filters up to the first one that contains the conjunction are grouped together. The order in which you choose filters is significant if you choose to use the \u201cor<\/strong>\u201d conjunction in your query. The rules for parsing the queries are as follows, with the parentheses showing the precedence.<\/p>\n\n\n\n\n\n\n
      Order of conjunctions<\/td>\nSignificance<\/td>\n<\/tr>\n
      One \u201cor<\/strong>\u201d as the last filter<\/td>\nThe condition in the filter with the \u201cor<\/strong>\u201d is used over the whole query. For example: Product equals XYZ and Priority equals P 1 and Status equals Open or Severity equals Severe This query is parsed as follows: (Product equals XYZ and Priority equals P 1 and Status equals Open) (or Severity equals Severe)<\/td>\n<\/tr>\n
      One \u201cor<\/strong>\u201d that is not the last filter<\/td>\nThe \u201cand\u201d operators take precedence over the \u201cor\u201d operator. For example: Product equals XYZ and Priority equals P 1 or Priority equals P 2 and Severity not equal Severe This query is parsed as follows: (Product equals XYZ and Priority equals P 1) (or Priority equals P 2 and Severity not equal Severe)<\/td>\n<\/tr>\n
      There are multiple \u201cand\u201d and \u201cor\u201d filters<\/td>\nOnce again, the \u201cand\u201d operators take precedence over the \u201cor\u201d operators. For example: Product equals XYZ and Priority equals P 1 or Priority equals P 2 and Severity not equal Severe or Severity not equal Major This query is parsed as follows: (Product equals XYZ and Priority equals P 1) (or Priority equals P 2 and Severity not equal Severe) (or Severity not equal Major)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      Note<\/strong>: You can toggle between standard search mode filters and advanced search mode filters at any time, but the filters currently on the screen are reset. Filters are not lost when you change between condensed and expanded filters.<\/p>\n

      Allowed Values and Advanced Queries<\/h3>\n

      Allowed values do not operate within filters selected for advanced queries. You will see all the parent and all the child values in the filter lists for these queries.<\/p>\n

      Querying for Inactive Values<\/h3>\n

      Within Advanced Search lists, an entry * Show disabled values<\/strong> * will appear in any list that contains values that have been disabled by the administrator. For example, you may wish to search for issues where the originator<\/em> of the issue has left your company, and their account has been disabled. If the field contains any values that are disabled, then you can select * Show disabled values <\/strong>* and the screen will refresh, showing all the disabled values. You can revert to only displaying enabled values with the prompt * Do not show disabled values<\/strong> * that will now be in the list.<\/p>\n

      Querying with Date Ranges and the Changed Operator<\/h3>\n

      This applies when applying conditional formatting to multiple conditions within the filters of date fields.\u00a0 From the following screenshot, the example shows that we want to apply a conditional format of a red dot to a date field named Contract Date<\/strong>.\u00a0 First, we only want to look at dates that are not empty<\/em> and then we want, for the same field, to look for values that changed <\/em>between two specific dates.\u00a0 The filter is only applied to issues where the date range includes field values where the latest change is within the two date values specified in the filter.<\/p>\n

      <\/p>\n

      Querying with Date \/ Time Functions<\/h3>\n

      Day and Date display type fields have two basic ways in which they are used as query filters, depending on the operator you select.<\/p>\n\n\n\n\n\n
      Operator<\/td>\nFunctionality<\/td>\n<\/tr>\n
      Equals
      \nGreater than
      \nLess than
      \nNot equal
      \nLess than or equal to
      \nGreater than or equal to
      \nBetween
      \nEmpty
      \nNot empty<\/em><\/td>\n      		When you choose one of these operators, two date input fields appear, each with a popup calendar.\u00a0 Depending on the operator you select, you will enter a date (and potentially time) into none, one or the two fields.\u00a0 When you select Equals<\/em>, Greater than<\/em>, Less than<\/em>, Not equal<\/em>, Less than or equal to<\/em>, or Greater than or equal to<\/em> then you only enter a date into the first field.\u00a0 When you select Between<\/em>, you enter two dates.\u00a0 If you select Empty<\/em> or Not empty<\/em>, then you do not enter any date values. When using a date field as a filter, the time of day is adjusted as follows when the time component is not entered as part of the filter:<\/p>\n
        \n
      • For all filters, the user’s time zone is utilized<\/li>\n
      • For the equals, greater than, greater than <\/em>or equals <\/em>operators, the end of the day is used as the precise point in time<\/li>\n
      • For the less than, less than <\/em>or equals <\/em>operators, the beginning of the day is used as the precise point in time.<\/li>\n
      • The between<\/em> operator is inclusive of the 2 dates provided in the filter.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
      During
      \nAfter
      \nBefore
      \nAfter or during
      \nBefore or during<\/em><\/td>\n      		When you choose one of these operators, you are presented with a number of date \/ time expressions which complete the filter.\u00a0 The list of valid expressions and their meanings is as follows.\u00a0 This table assumes that today’s date is Friday, November 3rd, 2017 and the fiscal year setting of your installation starts on January 1.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
      Title<\/span><\/strong><\/td>\nData dictionary field name<\/span><\/strong><\/td>\nExpression resolves to<\/span><\/strong><\/td>\n<\/tr>\n
      Last 4 weeks<\/td>\nEVDTF_LAST_4_WEEKS<\/td>\nOctober 1st 2017 – October 28th 2017<\/td>\n<\/tr>\n
      Last 7 days<\/td>\nEVDTF_LAST_7_DAYS<\/td>\nOctober 27th 2017- November 2nd 2017<\/td>\n<\/tr>\n
      Last fiscal quarter<\/td>\nEVDTF_LAST_FISCAL_QUARTER<\/td>\nJuly 1st 2017 – September 30th 2017<\/td>\n<\/tr>\n
      Last fiscal year<\/td>\nEVDTF_LAST_FISCAL_YEAR<\/td>\nJanuary 1st 2016 – December 31st 2016<\/td>\n<\/tr>\n
      Last fiscal quarter to date *<\/td>\nEVDTF_LAST_FQ_TO_DATE<\/td>\nJuly 1st 2017 –\u00a0 November 3rd 2017<\/td>\n<\/tr>\n
      Last fiscal year to date *<\/td>\nEVDTF_LAST_FY_TO_DATE<\/td>\nJanuary 1st 2017 –\u00a0 November 3rd 2017<\/td>\n<\/tr>\n
      Last month<\/td>\nEVDTF_LAST_MONTH<\/td>\nOctober 1st 2017 – October 31st 2017<\/td>\n<\/tr>\n
      Last month to date<\/td>\nEVDTF_LAST_MONTH_TO_DATE<\/td>\nOctober 1st 2017 – November 3rd 2017<\/td>\n<\/tr>\n
      Last quarter<\/td>\nEVDTF_LAST_QUARTER<\/td>\nJuly 1st 2017 – September 30th 2017<\/td>\n<\/tr>\n
      Last quarter to date<\/td>\nEVDTF_LAST_QUARTER_TO_DATE<\/td>\nJuly 1st 2017 – November 3rd 2017<\/td>\n<\/tr>\n
      Last week<\/td>\nEVDTF_LAST_WEEK<\/td>\nOctober 22nd 2017 – October 28th 2017<\/td>\n<\/tr>\n
      Last week to date *<\/td>\nEVDTF_LAST_WEEK_TO_DATE<\/td>\nOctober 22nd 2017 – November 3rd 2017<\/td>\n<\/tr>\n
      Last year<\/td>\nEVDTF_LAST_YEAR<\/td>\nJanuary 1st 2016 – December 31st 2016<\/td>\n<\/tr>\n
      Last year to date<\/td>\nEVDTF_LAST_YEAR_TO_DATE<\/td>\nJanuary 1st 2016 – November 3rd 2017<\/td>\n<\/tr>\n
      Next 4 weeks<\/td>\nEVDTF_NEXT_4_WEEKS<\/td>\nNovember 5th 2017 – December 2nd 2017<\/td>\n<\/tr>\n
      Next 7 days<\/td>\nEVDTF_NEXT_7_DAYS<\/td>\nNovember 4th 2017 – November 10th 2017<\/td>\n<\/tr>\n
      Next fiscal quarter<\/td>\nEVDTF_NEXT_FISCAL_QUARTER<\/td>\nJanuary 1st 2018 – March 31st 2018<\/td>\n<\/tr>\n
      Next fiscal year<\/td>\nEVDTF_NEXT_FISCAL_YEAR<\/td>\nJanuary 1st 2018 – December 31st 2018<\/td>\n<\/tr>\n
      Next month<\/td>\nEVDTF_NEXT_MONTH<\/td>\nDecember 1st 2017 – December 31st 2017<\/td>\n<\/tr>\n
      Next quarter<\/td>\nEVDTF_NEXT_QUARTER<\/td>\nJanuary 1st 2018 – March 31st 2018<\/td>\n<\/tr>\n
      Next week<\/td>\nEVDTF_NEXT_WEEK<\/td>\nNovember 5th 2017 – November 11th 2017<\/td>\n<\/tr>\n
      Next year<\/td>\nEVDTF_NEXT_YEAR<\/td>\nJanuary 1st 2018 – December 31st 2018<\/td>\n<\/tr>\n
      This week to date<\/td>\nEVDTF_THIS_WEEK_TO_DATE<\/td>\nOctober 29th 2017 – November 3rd 2017<\/td>\n<\/tr>\n
      This fiscal quarter<\/td>\nEVDTF_THIS_FISCAL_QUARTER<\/td>\nOctober 1st 2017 – December 31st 2017<\/td>\n<\/tr>\n
      This fiscal year<\/td>\nEVDTF_THIS_FISCAL_YEAR<\/td>\nJanuary 1st 2017 – December 31st 2017<\/td>\n<\/tr>\n
      This fiscal quarter to date *<\/td>\nEVDTF_THIS_FQ_TO_DATE<\/td>\nOctober 1st 2017 – November 3rd 2017<\/td>\n<\/tr>\n
      This fiscal year to date *<\/td>\nEVDTF_THIS_FY_TO_DATE<\/td>\nJanuary 1st 2017 – November 3rd 2017<\/td>\n<\/tr>\n
      This month<\/td>\nEVDTF_THIS_MONTH<\/td>\nNovember 1st 2017 – November 30th 2017<\/td>\n<\/tr>\n
      This month to date *<\/td>\nEVDTF_THIS_MONTH_TO_DATE<\/td>\nNovember 1st 2017 – November 3rd 2017<\/td>\n<\/tr>\n
      This quarter<\/td>\nEVDTF_THIS_QUARTER<\/td>\nOctober 1st 2017 – December 31st 2017<\/td>\n<\/tr>\n
      This quarter to date<\/td>\nEVDTF_THIS_QUARTER_TO_DATE<\/td>\nOctober 1st 2017 – November 3rd 2017<\/td>\n<\/tr>\n
      This week<\/td>\nEVDTF_THIS_WEEK<\/td>\nOctober 29th 2017 – November 4th 2017<\/td>\n<\/tr>\n
      This week to date *<\/td>\nEVDTF_THIS_WEEK_TO_DATE<\/td>\nOctober 29th 2017 – November 3rd 2017<\/td>\n<\/tr>\n
      This year<\/td>\nEVDTF_THIS_YEAR<\/td>\nJanuary 1st 2017 – December 31st 2017<\/td>\n<\/tr>\n
      This year to date<\/td>\nEVDTF_THIS_YEAR_TO_DATE<\/td>\nJanuary 1st 2017 – November 3rd 2017<\/td>\n<\/tr>\n
      Today<\/td>\nEVDTF_TODAY<\/td>\nNovember 3rd 2017<\/td>\n<\/tr>\n
      Yesterday<\/td>\nEVDTF_YESTERDAY<\/td>\nNovember 2nd 2017<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      * These expressions are not commonly used.\u00a0 If you require to use these, ask your administrator to turn them on within the data dicationary by setting the Filter Criteria<\/strong> of the expression fields to Yes.<\/em><\/p>\n

      Querying for Multiple Issue Numbers (IDs)<\/h3>\n

      On the Search\/Report screen, you can type multiple issue IDs into the Issue ID field. Separate these by a semicolon \u2018;\u2019.<\/p>\n

      Querying for Null or No Values<\/h3>\n

      There are occasions when it is useful to be able to search for a null value, or the absence of a value. For example, you may want a report where the filter is to be \u201cshow me all the records that have an empty customer field\u201d. If the field is a list field, you can select the entry * None<\/strong> *. If the field is a text field, however, you can enter the character string {null}<\/strong>, to signify that you are looking for a null.<\/p>\n

      Querying with User Name Fields<\/h3>\n

      User fields have two options related to their ability to search, using the selected value or values as filters. First, there is an entry within the search list, * Current User<\/strong> *. When this entry is selected, the name of the user currently signed in is used as the filter value. If your administrator has enabled the option, there may also be an entry in the list, * Include Inactive Users<\/strong> *. By default, each list of users only includes activated users. When you select this option, the screen refreshes and the user list will include both active and inactive user names. If your installation uses pop-up selection for users, a checkbox will allow any search you make, to include inactive user names.<\/p>\n

      Querying with Checkbox Fields<\/h3>\n

      Checkboxes are odd in their behavior.\u00a0 This is because you, the user sees them as unchecked <\/em>and checked<\/em>.\u00a0 However, the underlying databases upon which ExtraView relies also sees them as not being set at all.\u00a0 To the databases, this is different value, termed a “null<\/em>” value.\u00a0 Therefore checkboxes have three potential values, null<\/em>, unchecked <\/em>and checked<\/em>.\u00a0 As far as possible, ExtraView treats the null <\/em>value as being the same as\u00a0unchecked<\/em>.\u00a0 However, once a checkbox is checked<\/em>, and then subsequently\u00a0unchecked<\/em>, its value remains as unchecked <\/em>and never goes back to null<\/em>.\u00a0 Querying for a value of\u00a0unchecked<\/em> within a checkbox, will also include looking for the null<\/em> value.<\/p>\n

      Querying with Popup Field Lists<\/h3>\n

      Popup field lists are typically large lists.\u00a0 There is a button beside each popup field on the screens that present popup fields to the user.\u00a0 When this is clicked, there is a window that allows you to search in a variety of ways to select the value you are interested in using as a filter:<\/p>\n

        \n
      • You can type part of the value and use an asterisk as a wildcard to search for all values that match.\u00a0 You can then select the value from those returned<\/li>\n
      • There is an option to show disabled entries in the list and to then allow you to search for disabled values that exist in your issues<\/li>\n
      • A string of letters and numbers are presented that represent the first character of the possible values you can select.\u00a0 Click on any letter or number to see all the values that begin with that character<\/li>\n
      • You can select the value * Any *<\/strong><\/li>\n
      • You can select the value * None *<\/strong><\/li>\n<\/ul>\n

        Within the entry field on the screen with the filters, you can directly enter the value you want to use as a filter.\u00a0 You may also use the asterisk wildcard within this entry field.\u00a0 However, note that if the field is a child within an allowed value relationship, you cannot use the Use Allowed Values in Filters<\/strong> checkbox option at the same time.<\/p>\n

        Queries that Use Values of Different Fields within Filters<\/h3>\n

        This feature is especially valuable for reports that are embedded within\u00a0add<\/em> and\u00a0edit<\/em> layouts.\u00a0 This allows you to set up a filter on a field which uses the value of a different field as the input.\u00a0 For example, a report that you embed may want to retrieve an issue where the ID of the current issue is equal to the value of the field named PARENT_ID within the current issue:<\/p>\n

        <\/p>\n

        $$PARENT_ID$$ refers to the field name which contains the issue ID of the parent issue you want to retrieve.<\/p>\n

        Note that this only works with fields with a display type of text or number.\u00a0 However, if you would like this feature to operate with other field types such as list field display types, you can create a hidden text field on the layout in question and use a business rule to assign the value to that hidden field.<\/p>\n

        Runtime Replacement Filters<\/h3>\n

        Both Container Reports and Dashboard Reports provide the opportunity to run multiple reports that give a single, combined output.\u00a0 Each individual report within Container Reports and Dashboards may, and probably will, have their own filters.\u00a0 However, there are times where it can be useful to apply a single set of runtime filters to all the reports.\u00a0 Container Reports and Dashboard Reports give the opportunity to provide runtime replacement filters that are applied to all the reports on their output.<\/p>\n

        For example, you might want to apply a runtime replacement filter that applies the same date range to all the output or apply a filter that provides only results from a specific product within the output.<\/p>\n

        When you specify runtime replacement filters within a Dashboard Report or Container Report, they will replace filters for the same field within the individual reports that they contain.\u00a0 If a runtime replacement filter at the Dashboard or Container report level does not appear within the contained report, it will have no effect.\u00a0 Further, it is not possible to specify conjunctions for the runtime replacement filters – they simply replace filters for the same field within the contained reports.\u00a0 The runtime replacement filters are always displayed in expanded mode, allowing you to make multiple selections within a field.<\/p>\n

        Tip: A typical use case might be to create a dashboard that contains several reports about all your products, but you want to filter on the report output by a single product.\u00a0 You cannot select a runtime replacement filter with a value similar to Product = Any<\/em>, but you can select all the product values in the list and store that as your filter.\u00a0 Then, after viewing the dashboard, you can select a new filter value that is either just one, or a selection of products.<\/p>\n","protected":false},"excerpt":{"rendered":"

        Selecting query filters will impose restrictions upon the report being produced and return a set of results that matches the filters you set. For example, if you select the Status Open, then only open issues will be displayed. Filters can be combined together, for example to show Open issues for the product named XXX that…<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":23762,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_lmt_disableupdate":"no","_lmt_disable":"","_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"class_list":["post-23763","page","type-page","status-publish","hentry"],"acf":[],"yoast_head":"\nQuery Filters - Product Documentation<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/querying-1\/query-filters-1\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Query Filters - Product Documentation\" \/>\n<meta property=\"og:description\" content=\"Selecting query filters will impose restrictions upon the report being produced and return a set of results that matches the filters you set. For example, if you select the Status Open, then only open issues will be displayed. Filters can be combined together, for example to show Open issues for the product named XXX that...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/querying-1\/query-filters-1\/\" \/>\n<meta property=\"og:site_name\" content=\"Product Documentation\" \/>\n<meta property=\"article:modified_time\" content=\"2025-03-06T19:49:27+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"23 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/querying-1\/query-filters-1\/\",\"url\":\"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/querying-1\/query-filters-1\/\",\"name\":\"Query Filters - Product Documentation\",\"isPartOf\":{\"@id\":\"https:\/\/docs.extraview.com\/v25\/#website\"},\"datePublished\":\"2024-02-15T22:53:34+00:00\",\"dateModified\":\"2025-03-06T19:49:27+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/querying-1\/query-filters-1\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/querying-1\/query-filters-1\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/querying-1\/query-filters-1\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/docs.extraview.com\/v25\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"ExtraView 25\",\"item\":\"https:\/\/docs.extraview.com\/v25\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"End User Guide\",\"item\":\"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Querying\",\"item\":\"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/querying-1\/\"},{\"@type\":\"ListItem\",\"position\":5,\"name\":\"Query Filters\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/docs.extraview.com\/v25\/#website\",\"url\":\"https:\/\/docs.extraview.com\/v25\/\",\"name\":\"ExtraView Product Documentation\",\"description\":\"ExtraView Documentation\",\"publisher\":{\"@id\":\"https:\/\/docs.extraview.com\/v25\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/docs.extraview.com\/v25\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/docs.extraview.com\/v25\/#organization\",\"name\":\"ExtraView Corporation\",\"url\":\"https:\/\/docs.extraview.com\/v25\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/docs.extraview.com\/v25\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/docs-stg.extraview.com\/wp-content\/uploads\/2024\/03\/favicon.png\",\"contentUrl\":\"https:\/\/docs-stg.extraview.com\/wp-content\/uploads\/2024\/03\/favicon.png\",\"width\":512,\"height\":512,\"caption\":\"ExtraView Corporation\"},\"image\":{\"@id\":\"https:\/\/docs.extraview.com\/v25\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Query Filters - Product Documentation","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/querying-1\/query-filters-1\/","og_locale":"en_US","og_type":"article","og_title":"Query Filters - Product Documentation","og_description":"Selecting query filters will impose restrictions upon the report being produced and return a set of results that matches the filters you set. For example, if you select the Status Open, then only open issues will be displayed. Filters can be combined together, for example to show Open issues for the product named XXX that...","og_url":"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/querying-1\/query-filters-1\/","og_site_name":"Product Documentation","article_modified_time":"2025-03-06T19:49:27+00:00","twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"23 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/querying-1\/query-filters-1\/","url":"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/querying-1\/query-filters-1\/","name":"Query Filters - Product Documentation","isPartOf":{"@id":"https:\/\/docs.extraview.com\/v25\/#website"},"datePublished":"2024-02-15T22:53:34+00:00","dateModified":"2025-03-06T19:49:27+00:00","breadcrumb":{"@id":"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/querying-1\/query-filters-1\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/querying-1\/query-filters-1\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/querying-1\/query-filters-1\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/docs.extraview.com\/v25\/"},{"@type":"ListItem","position":2,"name":"ExtraView 25","item":"https:\/\/docs.extraview.com\/v25\/"},{"@type":"ListItem","position":3,"name":"End User Guide","item":"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/"},{"@type":"ListItem","position":4,"name":"Querying","item":"https:\/\/docs.extraview.com\/v25\/extraview-25\/end-user-guide-1\/querying-1\/"},{"@type":"ListItem","position":5,"name":"Query Filters"}]},{"@type":"WebSite","@id":"https:\/\/docs.extraview.com\/v25\/#website","url":"https:\/\/docs.extraview.com\/v25\/","name":"ExtraView Product Documentation","description":"ExtraView Documentation","publisher":{"@id":"https:\/\/docs.extraview.com\/v25\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/docs.extraview.com\/v25\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/docs.extraview.com\/v25\/#organization","name":"ExtraView Corporation","url":"https:\/\/docs.extraview.com\/v25\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/docs.extraview.com\/v25\/#\/schema\/logo\/image\/","url":"https:\/\/docs-stg.extraview.com\/wp-content\/uploads\/2024\/03\/favicon.png","contentUrl":"https:\/\/docs-stg.extraview.com\/wp-content\/uploads\/2024\/03\/favicon.png","width":512,"height":512,"caption":"ExtraView Corporation"},"image":{"@id":"https:\/\/docs.extraview.com\/v25\/#\/schema\/logo\/image\/"}}]}},"taxonomy_info":[],"featured_image_src_large":false,"author_info":{"display_name":"carl.koppel","author_link":"https:\/\/docs.extraview.com\/v25\/author\/carl-koppel\/"},"comment_info":0,"_links":{"self":[{"href":"https:\/\/docs.extraview.com\/v25\/wp-json\/wp\/v2\/pages\/23763","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.extraview.com\/v25\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/docs.extraview.com\/v25\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/docs.extraview.com\/v25\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.extraview.com\/v25\/wp-json\/wp\/v2\/comments?post=23763"}],"version-history":[{"count":0,"href":"https:\/\/docs.extraview.com\/v25\/wp-json\/wp\/v2\/pages\/23763\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/docs.extraview.com\/v25\/wp-json\/wp\/v2\/pages\/23762"}],"wp:attachment":[{"href":"https:\/\/docs.extraview.com\/v25\/wp-json\/wp\/v2\/media?parent=23763"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}