| Info |
|---|
This feature requires a CommCare Software Plan This feature will only be available to CommCare users with Pro Plan or higher. For more details, see the CommCare Software Plan page. |
https://www.youtube.com/watch?v=dStNRojjno0
...
| Excerpt |
|---|
The Case List Explorer is a powerful feature for CommCare HQ which enables users to inspect their case data by building custom-filtered views of their cases. The Case List Explorer allows you to find and validate test data, identify cases that fit a very specific criteria, and find data anomalies and outliers. |
...
Watch this short video to learn more about the Case List Explorer and how to use it!
| Multiexcerpt include macro | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Table of Contents
| Table of Contents | ||||
|---|---|---|---|---|
|
Case List Explorer Overview
Seeing Your Case List
To begin, go to your CommCareHQ project space, select the Reports tab at the top of page, and locate the "Inspect Data" header on the left-hand side.
...
XPath Date/Timezone Conversion
Previously, project-specific properties were stored as standalone time or dates, meaning that no conversion to UTC was required while generating a query for this, after an update was deployed to address a longstanding issue on the Case List Explorer page, that which disallowed a user's input into the query search box from being translated back to UTC from the domains timezone, which had caused cases outside the specified date range to be returned, or cases inside the range to be hidden.
To rectify this, a new update has introduced a new feature that that allows exact matches of special case properties to now work. For example, "last_modified = '2023-06-03'" will return cases that were modified on project timezone's date "2023-06-03". Originally, exact matches of special case properties do not work because in Elastic Search, special case properties are stored as timestamps, meaning "'2023-06-03" won't be an exact match.
Additionally, this change adds a check to apply the timezone conversion to only datetime special case properties, since they are stored in Elastic Search as UTC timestamps.
These expressions can be used in conjunction with the Case Query Language, as a Search Expression, as outlined above.