Appearance
Reports and loading data
Building reports
Presently includes a custom report type, Offerings with Sessions with Attendance. It gives one row per person per session, marked or not, with:
- the offering, its program and session;
- the person;
- the code, its meaning and its reporting category;
- the reason;
- Enrolled, which is unticked for walk-ins (and stays ticked for someone who has since been unenrolled).
To count marks only, filter out rows whose Attendance Code is blank.
Salesforce also creates report types of its own for programs, offerings, sessions and enrollments, such as Offerings with Enrollments. Attendance is reported only through Presently's report type, which also offers an Attendance Number column: click a row's number to open that attendance record. Users need Run Reports on their profile.
Presently doesn't ship ready-made reports or dashboards: the Home page covers the common views. For an attendee-by-session grid, use Export CSV in the attendance history.
Rules that apply everywhere
The same rules apply in the app, on record pages, through the API and in data loads:
- A closed session's attendance can't be added, changed or deleted, except by users who can reopen sessions (Program Owner and Admin), on record pages, through the API and in data loads. On the attendance sheet, they reopen the session first.
- An attendance row can't be moved to a different person.
- Sessions can't be added to an Archived offering or after an offering's end date, and nobody can be enrolled on an Archived offering.
- Two sessions of the same offering can't have the same date and time.
Bringing in past attendance
Moving history from spreadsheets or another system with Data Loader takes one extra step, because Presently creates attendance rows by itself.
- Load in this order: programs, offerings, enrollments, then sessions. Each session you load gets an empty attendance row for every person enrolled on its offering at that point.
- Load the marks as an upsert, not an insert. A person has one row per session, so inserting a second row is refused. Upsert matching on Unique Key: Data Loader then fills in the existing row.
- Build the Unique Key column as the session's 18-character record ID, a colon, then the person's 18-character Contact ID, for example
a06...AAA:003...BBB. The 15-character IDs that reports show won't match. Export your loaded sessions and Contacts with their IDs to look them up. - Give each mark its code by the short code. Put the code (P, A, L and so on) in a column and, when Data Loader asks how to match the Attendance Code lookup, choose Code. You don't need the codes' record IDs.
- Load as a Program Owner or Admin if any of the sessions are already closed. Staff can't change a closed session.
- Add walk-ins as a separate insert. Someone who attended without being enrolled has no row to fill. Put them in their own file with Session, Attendee Contact and the code, and no Unique Key column, and insert it. Presently fills in the key itself. Only a System Administrator can create rows by upsert, because everyone else has Unique Key read-only.
- Archive offerings last. Set old offerings to Archived only after their enrollments, sessions and marks are loaded.
- Keep batches moderate. One batch can create or change about 10,000 attendance rows (people times sessions). Lower the batch size for large rosters.
Changing data outside the app
You can also edit Presently records on their record pages and in list views. The rules above still apply, so a closed session stays protected wherever the edit comes from.