Reports that span abstracts and sessions

An abstract is a record in the same Sessions list as a session. Whether a submission form collects Abstracts or Sessions, what arrives is a session record, flagged as an abstract. That is why one report can cover both, and why you filter, rather than choose a different report, to separate them. See Collect and review abstracts for how abstracts become sessions.

Build one report for both

1. Open Reports and start a Sessions report in the Report Builder.
2. Add the columns you want from the Fields panel. Session fields use the same names as the columns in the Sessions grid.
3. Add Source to see which submission form each record came through.
4. On an event that uses Sessions 2.0, add Type, which reads Abstract or Session. It sits next to Source in the field list.
5. To split them, filter Type. To see both side by side, leave it unfiltered and group by Type.

Note

If you don’t find Type in the Fields panel, search for Source instead and filter on the form: a form that collects abstracts only produces abstract records.

What converts when an abstract becomes a session

When an admin converts an abstract into a session in place, from then on the record counts as a session, not an abstract. A report filtered on Type moves it with the conversion. Records built into a separate session by a different route stay separate rows. See Collect and review abstracts.

Related reports

• Reviews on the same report. Add scorecard questions from the Reviews group to keep one row per record, with answers summarised. See Review answers, one row per session.
• Subsessions. Subsessions are their own rows. Filter Is Subsession and add the Parent session fields to show the parent next to each. See Sessions and subsessions on one row.
• A view instead of a report. To work in a table, the Abstracts list and the Sessions list both accept saved views. See Dashboard views.