# RapidIdentity Administrators' and Users' Guide

##### Studio Data Explorer

Once a job is run, the resulting data can be viewed and filtered in the Data Explorer.

To view records, click the dropdown to Select data type. There are three categories listed: Consumer, Metaverse, and Provider. The options in each category directly correlate to the Record Definitions set up in the Consumer or Provider applications and further defined in Metaverse,

Choose the Record Definition for which you would like to see the details from the dropdown list.

This will result in a view of the records associated with that Record Definition, as well as the values expected to show based on the set Field Definitions for those Records.

Here, you can validate that the field values are mapped correctly to the fields. If any changes need to be made to these configurations, those can be done in the Field Definitions for the application, and the job would need to be run again to view updated results.

### Note

The Data Explorer is a read-only validation screen.

To narrow the search results, enter a filter before clicking Search.

###### Filtering Syntax

The basic unit for a filter is a comparison of the form <fieldName><operator><value>.

• fieldName starts with a letter and may contain letters, digits, underscores, and hyphens.

• operator can be one of the following:

• equals: =

• does not equal: !=

• like: ~ or like

• greater than: >

• greater than or equal to: >=

• less than: <

• less than or equal to: <=

• value is either null or a quoted JSON string.

• The unquoted form of the JSON string may be used if it does not contain white space, backslash, double quotes, or any symbol used as an operator.

• Comparisons may be joined with a boolean logical operator where and has higher precedence.

• and: & or and

• or: | or or

• Keyword forms of operators are not case-sensitive.

• A comparison or set of comparisons joined by logical operators may be enclosed in a pair of parentheses.

• The not operator (! or not) may precede the opening parenthesis to negate the boolean value of the expression.

• Insignificant white space may appear anywhere except within a fieldName, operator, or value, but is only required before and after keyword forms of and, or, not, and like operators.