In Submissions, you can run a report for one space or for every space in your account. What the report includes depends on how you open the Query Center and, in one case, where you were working just before you opened it.
Prerequisites
- Access to the Submissions Query Center.
- Permission to run the report type you want, which may be Reviews, Spaces, or Submissions; see Run, Download, or Schedule a Submissions Report.
Run a Report Limited to One Space
- Open the space whose records you want to include in the report.
- From that space's menu, go to Queries. You can also use one of the space's count tiles: the "Submissions in Progress" and "Approved Submissions" tiles on a space's submissions page both open the Query Center with a ready-made report for that space already queued.
Result
A tip at the top of the page names the space you are working in. The tip explains that queries you run and save from this view return records for that space only and belong to that space. Use the Global Query Center link in the tip when you want to leave that space-limited view. Submissions reports return only that space's records, and the default results leave out the space name column because every row belongs to the same space.
Run a Report Across Every Space
- From the top-level Submissions menu, go to Queries.
Result
If this is a fresh visit and you were not just working inside a space, the Query Center opens without a space tip. In that view, Submissions reports return records from every space.
Warning
If you recently worked inside a space and then use in-app navigation to open Queries from the top-level menu, the page can stay limited to that space without telling you. You may be on the global address but still see results for one space. Check the top of the page for the space tip. If you see it, you are not viewing every space. Choose the Global Query Center link in the tip to be certain. That link reloads the page fresh, which reliably clears the remembered space.
Opening the Submissions overview or the spaces list also clears the remembered space. If you want to guarantee a global view, return to either of those pages before you open Queries from the top-level menu.
Where a Saved Query Ends Up
When you save a query while you are working in one space, Rhythm saves it in that space's folders. It appears again only when you return to that same space. When you save a query from the global Query Center, Rhythm saves it in your account's organization-wide folders, and it appears no matter which space, if any, you are in when you look for it.
Keep this in mind if a saved query seems to have disappeared. If you saved it while the page was still silently limited to a space, as described above, Rhythm saved it in that space's folders instead of the organization-wide folders. Check that space's Query Center rather than the global one.
Limitations
- The Spaces report type is never limited to one space, no matter how you open it. Even from inside a space's Query Center, a Spaces report lists every space in your account.
- It has not been confirmed whether the Reviews report type is limited to your current space in the same way the Submissions type is. If you expect a Reviews report to be space-limited, review its results carefully against what you expect.
- A custom field set up as a multi-select picklist shows its selected values correctly on the form and on the record itself. When you include that field as an output field in a query, a value that resembles a date can be reformatted as a date instead of shown as the original picklist text. If a picklist column in your results looks wrong, check the form or record view for the value it actually holds.
- Abstract query output for co-author information includes only the first five co-authors. Additional co-authors on the same abstract are not available in the standard query output.
- For event abstract submission queries, use the Sys Created At output field rather than the Submission Date field when you need an accurate submission date and time. Some records can show a Submission Date value that is inconsistent with what the Details view and the audit log's creation timestamp show.