Automatically establish 2-way relationship between records created by QB action

  • 0
  • 1
  • Question
  • Updated 1 year ago
Advisors use the Activities table to plan and keep track of their activities. Specialists can request an activity in the Requests table. I have setup a QuickBase action, when a specialists adds a request (in the Request table), it creates a record (Activity) in the Activities table.
Now I would like specialists and advisors to be able to communicate with each other via the Remarks field, each in their respective table, and have the Request table lookup other data from the Activities table, like the status of the activity. So I have setup two relationships between these tables (1 in each way). In one way, from the Request to the Activity, the relation is automatically established by the action, i.e. I set the action for the record ID to become the related request, so the Remarks field in the Request table can already function as a lookup field in the Activities table.
But now my problem is how to automatically achieve the same in the other direction. Since I don't need an Action in the other direction (the request and the related activity already exist, they're just not linked to each other yet), I don't know how to automatically have the record ID from the Activities table recognized as the Related Activity in the Request table. 
Photo of Yoel Kuliasko

Yoel Kuliasko

  • 520 Points 500 badge 2x thumb

Posted 1 year ago

  • 0
  • 1
Photo of Yoel Kuliasko

Yoel Kuliasko

  • 520 Points 500 badge 2x thumb
Since I didn't find a solution, I tried to implement it manually on the form in the activities table. My problem is that, although the proxy field for the "Related activity" is one of the columns in the report I'm using, this column is not displayed in the embedded report on the Activities form. So I need to go to the Requests table, edit the request of which the record ID corresponds with the related request in the Activities table, select from the drop-down of the proxy field the activity with the record ID of the related activity, save the record, and only then the relationship is established.
So I guess I'm overlooking something. In the attached screenshot, since QB knows that the related request has record ID 57, there must be a way to also know that the record ID of the related activity is 979. Or?
(Edited)