Automation with table-to-table relationships
Hi there, I'm trying to automate some processes around budgets and projects but can't yet get it working in a simplified test-app. Am I chasing an utopia or should it work and am i doing something ...
Forum Discussion
Hi John,
What you basically suggest is to use the automation to set the status in the request record itself. and a second automation to act on that change.
I did not yet consider that approach to be honest but it's worth a try.
------------------------------
Jan-Willem S
------------------------------
What you basically suggest is to use the automation to set the status in the request record itself. and a second automation to act on that change.
I did not yet consider that approach to be honest but it's worth a try.
------------------------------
Jan-Willem S
------------------------------
Hi Jan,
Yes, that is correct. One more thing to note, as I am currently working on a somewhat similar use case. To make it more robust, you should create a summary field into the parent to prevent further changes while the copy Automations are running. You just need a simple total summary field filtered for the status being copying, or whatever your intermediary status is. You might need to summarize that field that was created up again to the "Grand-Parent" This will allow you to create a Data Validation Rule to prevent further updates to the "Grand-Parent"'s record that could cause a record to be missed in the automation.
I'd also check that internal status on add or modification if you're allowing the users to modify that.
Have a great day!
------------------------------
John Crosland
Software Developer
Inglett & Stubbs
Mableton GA
------------------------------
Yes, that is correct. One more thing to note, as I am currently working on a somewhat similar use case. To make it more robust, you should create a summary field into the parent to prevent further changes while the copy Automations are running. You just need a simple total summary field filtered for the status being copying, or whatever your intermediary status is. You might need to summarize that field that was created up again to the "Grand-Parent" This will allow you to create a Data Validation Rule to prevent further updates to the "Grand-Parent"'s record that could cause a record to be missed in the automation.
I'd also check that internal status on add or modification if you're allowing the users to modify that.
Have a great day!
------------------------------
John Crosland
Software Developer
Inglett & Stubbs
Mableton GA
------------------------------