Skip to main content
Question

Trying to build connected records

  • May 13, 2025 3:18 PM UTC
  • 1 reply
  • 49 views

Forum|alt.badge.img+3

Table 1 - Requirements

Table 2 - Meetings 

For each requirement there can be multiple meetings, owned by separate sales rep.

I already have these two tables, Now if SalesPerson_A has a Meeting_1 for Requirement_1 then an associated record is created in Table 2 - Meetings, but if the same SalesPerson_A has 5-7 follow up meetings for the same Requirement_1 then 5-7 more separate associates records are created and we have created a field dropdown - Round of meeting where we are manually managing, 1st, 2nd, 3rd, etc to keep track, then we are manually copy pasting the previous meetings links in the coming up meeting to access them. this is too outdated and time taking.

Also SalesPerson_B can also have a Meeting_1 for Requirement_1 then another new record is created in Table 2 - Meetings n for further follow ups its same manual way.

What i want to achieve is that if SalesPerson_A has a Meeting_1 for Requirement_1 then an associated record is created in Table 2, Called Record 1, then I can have someway to keep all the next rounds of meeting under the same, each meeting is different, we have different agenda, people we are meeting, meeting links to join so for each record here there is a lot of information we need to enter, also various fields about how that meeting went, etc. need to manage this separately for each round. what can be the best way to achieve it.

we never know we will 1 only or 7 or 10 meetings for a requirement.

1 reply

Top Step
Forum|alt.badge.img+12
  • Observing
  • Oct 27, 2026 8:53 PM UTC

I'd add a table in the middle. Requirements > Engagements > Meetings, where an Engagement is one sales rep working one requirement. Requirement_1 with SalesPerson_A is one Engagement record and Requirement_1 with SalesPerson_B is another.

Every meeting then hangs off its Engagement, with its own agenda, attendees, meeting link and outcome fields. The Engagement form shows an embedded report of all its meetings sorted by round, so nobody has to paste links to earlier rounds again.

For the round number, add a summary field on the Engagement that counts its meetings, [# of Meetings]. When you create the Engagements to Meetings relationship, Quickbase already adds an "Add Meeting" formula URL field to Engagements, so you just edit it to also fill in the round:

URLRoot() & "db/" & [_DBID_MEETINGS] & "?a=API_GenAddRecordForm"
& "&_fid_11=" & URLEncode([Record ID#])
& "&_fid_14=" & URLEncode(ToText([# of Meetings] + 1))
& "&z=" & Rurl()

In my test app 11 was Related Engagement and 14 was Round, but yours will be different, so check the field IDs in the Meetings table. The auto-created field also already has your correct table alias in it.

If meetings might get deleted, use a Maximum of Round summary plus 1 instead of the count. It works the same whether a requirement ends up with 1 meeting or 10.

Want more detail? I wrote a full walkthrough here: https://www.topstep.tech/blog/quickbase-meeting-rounds-engagements-table