How to pass data from details screen table to custom CSS card collection actions?

Ask for Help
, ,
1

Hi Glide community! I’m working on a calendar event details screen and could use some guidance on a data flow challenge.

Current Setup:

  • I have a details screen for calendar events (main table: Events)
  • At the bottom, I’ve added a custom CSS card collection with 4 action cards (Go to Interview, Call Applicant, Text Applicant, Email Applicant)
  • The card collection sources its labels and icons from a separate helper table I created specifically for this UI component

The Problem: The actions need data from the main Events table (phone number, email address, etc.), but since the card collection is sourced from my helper table, the actions can’t access that contextual information from the details screen.

What I’ve Tried: I thought about trying to put these details in the users table, but these individuals aren’t users yet as they’re applicants to the company.

Question: What’s the best way to “enrich” these card actions so they can access data from the Events table that’s powering the details screen? Should I:

  1. Use relations/lookups in my helper table to pull the needed data?
  2. Restructure how I’m building this card collection?
  3. Use a different approach entirely?

Any suggestions on how to bridge this data gap would be greatly appreciated!

Screenshots:

Applicant Table
Applicant Table2790×283 52 KB

Card Table
Card Table3130×682 93.8 KB

Applicant Interview
Applicant Interview589×1077 84 KB

2

If you want to keep this look, I would suggest:

  • Creating a JSON in the Events table that contains the info you need for the component.
  • On entry to the details view of the event, set the event’s rowID to a column in a helper table (one row).
  • In the helper table where you store the actions, use a single value column to bring the viewing rowID over, and then a relation + lookup to pull back the JSON.
  • Add a column to specify the query JSON snippet you’re gonna use, and a query JSON column to query the value for each row.

E.g: $.phoneNumber if you want to query the phoneNumber.

3

An alternative is to build a custom AI component and point it to the relevant values in the same events row. You won’t need any helper tables.