Skip to main content

Nice reporting through layers of relationships


Hello


I have a base structure of:


EVENT → VENUE SLOTS → STAFF ALLOCATIONS


Whee an event can have a number of venue slots (ie each day’s activity) and each slot has a number of staff allocated to it


I would like to be able to produce a report which shows all of the staff that have been allocated to an event, but I can’t see a way to do this. I can only insert a table for children of the master record - I can’t seem to go any deeper?


I was wondering about somehow exporting the data to google sheets but can’t see a great way to do this?

5 replies

Hi @Richard_Williamson


I assume you are linking all those tables via Linked Record fields?


If so, you can just use a Rollup field in Event table (using ArrayUnique(values)) to get all the names of the Staff


  • Author
  • Known Participant
  • 10 replies
  • November 2, 2022
Mohamed_Swella1 wrote:

Hi @Richard_Williamson


I assume you are linking all those tables via Linked Record fields?


If so, you can just use a Rollup field in Event table (using ArrayUnique(values)) to get all the names of the Staff


Thanks - the problem though is I would like to be able to get a rollup of all the information (name, start time, finish time, cost) - I suppose I could create a calculated field in the staff_allocations table and report on that but it seems pretty ugly


  • Inspiring
  • 69 replies
  • November 2, 2022

You need a direct connection between Event and Staff, bypassing Venue.

This way you’ll be able to use Page Designer to list the relationship.


  • Author
  • Known Participant
  • 10 replies
  • November 2, 2022

Urgh thanks - I suppose would need to be an automation which updates a field. Airtable is so frustrating how it’s almost great but falls down so badly on the reporting


  • Inspiring
  • 69 replies
  • November 3, 2022

Yes an automation would do Event 🔗 Staff.

And yes, reporting capabilities are rather poor. That’s why they called it Page Designer and not Report Designer.


Reply