Parent/Child Relationship

[louie.aldons-locke]

Hi All,

I am creating a logging system which will be used within an Event Control Room.

The system will log all calls and radio messages inbound and outbound. That being said, by the nature of what this function does, a user should not be able to edit a call once it has been logged, only add updates.

I have 2 tables:

1. Call details this records all of the information from the initial call
2. Call updates this records updates for the call

I need a way to link the two tables together so that the updates for Call 1 only show for Call 1 and the updates for Call 2 only show for Call 2 etc etc.

Is there a way to achieve this?

TIA!

[Jeff_Hager]

As long as you have a common value in both tables, such as a Call ID, you can create a relation in the Call table linking it to the Updates table.

With that relation, you can have a collection of Updates in the Call Detail Screen sourced from the relation.

[louie.aldons-locke]

Sounds like this is exactly what I need! I’m looking at making a sequential counter for Call Reference. This would be the field in each table.

Could you advise on a simple sequential counter?

[Darren_Murphy]

For the sequential counter, take a look at the video in the below doc:

Make | Glide Docs

[louie.aldons-locke]

Thanks, do I have to do this through a third party? Is there not a way I can do this within Glide?

[Darren_Murphy]

It depends. Glide does not do atomic operations, so if it is essential that you should never have duplicates, then you should use the solution shown in the video.

Otherwise, see below:

How do I create an auto-incrementing row number with Glide Tables?

This is a question that comes up a lot, so creating this topic to use as a reference. Typically, there are two distinct use cases when it comes to auto-incrementing row numbers. Use Case 1: – We need to generate a Part Number, or an Order Number, or an Employee ID. Once the number is generated, it should never change, even if rows are deleted. – The general approach for this use case is to maintain a static counter, use it to craft a suitably formatted ID, and increment it by one every time…

[louie.aldons-locke]

Sorry to reply again, @Jeff_Hager. Is it possible you can better explain your solution here?

[Jeff_Hager]

Here is the documentation on creating a relation between two tables.

https://www.glideapps.com/docs/automation/computed-columns/relations

Here is documentation on Collections. The source of a collection can be set to the relation on the Call Details screen.

Collections | Glide Docs

Review the documentation and let us know if you are still not understanding something.

[louie.aldons-locke]

Thanks, Jeff.

The thing I’m not understanding…

I am using ‘ROW ID’ as the unique reference for each new ‘Call’ being logged. This is in the ‘General Call’ data sheet.

I can’t work out how the call ID is copied across to the ‘Call Updates’ data sheet to ensure that only updates that are added from that calls page are shown.

I hope this makes sense?

[Jeff_Hager]

When you use your Add Updates form to add call updates, you can add various Value components to the same form to pass various values from the current parent Call Detail row into the newly added Call Update row. Choose the appropriate Value component to add to your form and set it to write the Call ID into a column in your Call Updates table. That’s the column that your relation will use.