Help

Re: Record Template vs Template Table + Automation

Solved
Jump to Solution
355 0
cancel
Showing results for 
Search instead for 
Did you mean: 
chrisberry
6 - Interface Innovator
6 - Interface Innovator

Hi All!

Looking for a quick gut check on a build method...record templates vs task template table.

Path 1
I've built out the base this way task template (table C) and have it all structured,  tasks (table B), and a project (table A). So when a form is submitted it creating a record on (table A) an automation is triggered that reads the project type then finds the related tasks (table C) creates copies of them on (table B) and then links them to the project. This happens for each project created. 

Path 2
I've built the same idea using the record template feature so when automation form is submitted to (table A) the automation is fired that looks to see what program type it is and then updates the record using a record template of the same name and adds new tasks to (table B) linked to the project. 

There's obviously a lift on the system to run the automation and do all the steps/complex logic work in the first version and an extra table that is not needed in the 2nd. Having the template table give me an exact copy of the data structure visually and sounds like it was the "work around" method prior to record templates.

I'm leaning toward moving the team to using the record template method but want to see if I'm missing any considerations based on others insights/experiences.

Thanks!

1 Solution

Accepted Solutions
TheTimeSavingCo
18 - Pluto
18 - Pluto

Yeah record template sounds good; easier to manage overall since you don't need to maintain the same schema between two tables.  The only thing that comes to mind is the possibility of the record templates not having functionality you need that using the table version provides, but given that both methods work fine feels like you're good to go

See Solution in Thread

2 Replies 2
TheTimeSavingCo
18 - Pluto
18 - Pluto

Yeah record template sounds good; easier to manage overall since you don't need to maintain the same schema between two tables.  The only thing that comes to mind is the possibility of the record templates not having functionality you need that using the table version provides, but given that both methods work fine feels like you're good to go

chrisberry
6 - Interface Innovator
6 - Interface Innovator

Appreciate your response as always!