Currently, in Queries, you will receive an error when including ‘Custom Field’, like: “Consented Status ”, attached to a participant-level custom field for the mGen collection protocol, and then use this as a sub-query to another query.

It is likely, the users want to run a report, and only get details for participants/visits/specimens that have certain criteria, which is added to a custom field level.

Example: In a single report, get a count of participants who consented to the collection protocol mGen and My Healthy Maryland.

Why?

When no CP is selected, the UI has no knowledge of the custom fields. Therefore the custom fields based filters from subqueries are wiped out in the main query resulting to an error.

Workaround

Add the custom field to your subquery as usual.
Use this subquery in your main query as usual.
Click View Records — ignore any error message. Select the columns you need and save the query.
Go back to the Queries list and schedule it as a Job with Run On Demand.
Go to Jobs, click Run, and you’ll get the results in a CSV file via email.

How to include Custom Fields/Forms in Subqueries?

Why?

Workaround