In reports you can add as many filters as you wish, and you can get quite complex with the filter logic using multiple fields with AND and OR conditional logic. To add a filter, select a field that you wish to filter on, after which you will need to set both an operator and a value. If the field is multiple choice, it will auto load all of that field's choices in a drop-down so that you may choose one of the choices. Otherwise, if it is not a multiple choice field, it will instead provide a text box for entering the filter value.

There is no limit to how many times you may use a field as a filter in a single report. TIP: If you want to find instances in your data where a field's value is blank/null, then just leave the value text box blank. Conversely, to find instances where the field has a value (i.e., is non-blank), set the operator as 'not =' with a blank text box.

Using ANDs and ORs with multiple fields allow you to do more complex filtering. If you have two filters with an AND between them, for example, that means that it will apply both of them together when filtering, but if you use OR, it will return results that apply to just one or the other. In general, using AND will often constrict the results further by returning less data in the report than when using OR.

If you have filtering that uses both OR and AND, it is very important to know the order in which REDCap evaluates the ORs and ANDs to ensure that your logic behaves how you expect. Essentially, all the ORs are evaluated for consecutive filter fields as a group, and all the groups are then evaluated as ANDs with each other. For example, it looks like (this OR this OR this) AND (this OR this OR this), in which all the ORs inside the parentheses are evaluated first and then those groups of ORs are then evaluated together using ANDs.

If you wish to do even more complex filtering, you may choose to switch the filtering format over to the 'Advanced Logic', which allows you to hand-type the filtering logic in a big text box. The filter logic is essentially the same kind of syntax as Branching Logic and Calculated field equations, in which you may use all the special functions, such as if(), datediff(), and various mathematical functions, in your filtering logic. REDCap will double check your hand-typed logic for any syntax errors, and it will not allow you to save the report until all errors have been resolved. When using the Advanced Logic, just make sure that your logic ultimately evaluates to either TRUE or FALSE and that it does *not* evaluate to a value, such as a number. For example, datediff([dob], 'today', 'y') is not valid because it will evaluate to a number, but datediff([dob], 'today', 'y') > 30 is valid because it will evaluate as either TRUE or FALSE. If the project is longitudinal, in certain contexts you may need to additionally provide the unique event name, which must also be in brackets and prepended to the variable name, in order to target that field on a particular event - e.g., [event_2_arm_1][variable_name].

The value you entered does not exist as a valid variable name in this project. Please re-enter it and try again.

What does this setting do?
When building a report using Step 3 (filtering) for a project that is longitudinal and/or has repeating instruments or repeating events, any filters defined in the report will be applied to each record as a whole, which is the default behavior when the 'Show data for all events and repeating instruments/events for each record returned' checkbox is CHECKED. But if it is UNCHECKED, it will additionally apply the filters to each event and/or each repeating instance within each record returned, in which some (or all) of the events or repeating instances in the records returned could get removed from the results. So if CHECKED, then *all* events or repeating instances will be returned for each record, but if UNCHECKED, then some events or repeating instances in each record *may* get removed (depending on the filter that is specified).

For example, if the project contains one event to capture demographics information and also contains subsequent visits (events) to capture measurements for vitals, one could set a filter of [sex] = '1' (Female). So if the checkbox setting was left CHECKED (the default setting), it would only return records where the person was female, and the results would contain *all* events (demography and all visits) for each of those records. However, if the checkbox was UNCHECKED in that situation, then not only would it remove the records where the person was male, but it would additionally remove the visit events for the female records, thus returning only the demography event for the female records. In this way, having the checkbox UNCHECKED not only filters out some of the records, but it may also remove some of the events in the records that are returned.

SUMMARY: In most cases, this checkbox setting will be left CHECKED unless you have very specific intentions for unchecking it. If you are still not quite sure how you might use this setting, then it is recommended that you leave it CHECKED.

 

Export Entire Project (metadata & data) REDCap Project (XML) The entire project (all records, instruments, fields, and project attributes) can be downloaded as a single XML file (CDISC ODM format). This XML file can be used to create a clone of the project (including its data, optionally) on this REDCap server or on another REDCap server (it can be uploaded on the Create New Project page). Because it is in CDISC ODM format, it can also be used to import the project into another ODM-compatible system. Choose export format CSV / Microsoft Excel (raw data) CSV / Microsoft Excel (labels) SPSS Statistical Software SAS Statistical Software R Statistical Software Stata Statistical Software CDISC ODM (XML) STEP 2: Archive the export files in File Repository? Yes, store a back-up copy No, do not store a back-up copy

De-identification options(optional) The options below allow you to limit the amount of sensitive information that you are exporting out of the project. Check all that apply. Known Identifiers: Remove All Identifier Fields (tagged in Data Dictionary) Hash the Record ID field (converts record name to an unrecognizable value) Free-form text: Remove unvalidated Text fields (i.e. Text fields other than dates, numbers, etc.) Remove Notes/Essay box fields Date and datetime fields: Remove all date and datetime fields — OR — Shift all dates by value between 0 and 364 days (shifted amount determined by algorithm for each record) What is date shifting? Deselect all options

Apply live filters? One or more live filters have been selected on this report. Do you wish to apply the live filters to the data export, thus producing the same data set that you currently see displayed on the report? Apply live filters selected on this report Advanced data formatting options Export blank values for gray Form Status? All Form Status fields with a gray status icon can be exported either as a blank value or as "0" (Incomplete). Hint: Blank values are recommended if the data will be imported back into REDCap, in which this preserves the gray status icons for all the imported records. Export gray Form Status fields with value of "0" Export gray Form Status fields with blank value Set CSV delimiter character Set the delimiter used to separate values in the CSV data file (only valid for CSV Raw Data and CSV Labels export formats): , (comma) - default tab ; (semi-colon) | (pipe) ^ (caret) Force all numbers into a specified decimal format? You may choose to force all data values containing a decimal to have a specified decimal character (comma or period/full stop). This will be applied to all calculations and number-validated text values in the export file. Use fields' native decimal format (default) Use period/full stop ( . ) as decimal for all numbers Use comma ( , ) as decimal for all numbers NOTE: Your data formatting selections above will be remembered in the future and will be pre-selected upon your next export.