I've worked one it with your advice, but it just checkmarks the field for every contract.
--
Bethany Dickey
Program Administrator
Mobile Bay National Estuary Program
118 N. Royal St., Suite 601
Mobile, AL 36602
251-459-8870
------Original Message------
A few things I see here. Although going over Evans questions you may need more than this depending on how you want it to work exactly.
You said the documents table was a child to the contracts table. The automation is showing that you are looking for modifications to a record in Contracts. You want to look for a modification happening in your Documents table as that is where the record is being modified and the file uploaded.
In the second screenshot you have the automation set to modify anything that has been created after 3/23/2020 so this would potentially modify many records at once. What you usually want to stick with is something like "[Record ID#] is equal to the [Record ID#\ of the trigger" which will modify the record that triggered the automation. That is what is used in most cases to prevent the automation from modifying way more than it should. Just an FYI for you in the future.
However in this particular case what you likely want to do is have the trigger be in your Documents table. Then have the trigger be a record being added there and when the automation is editing the record in the Contract table it should match the "[Record ID#] is equal to [Related Contract]" I believe that would work for you but test it out first as I have not. I may have it backwords and it may need to be "[Related Contract] is equal to [Record ID#] from the trigger" it is hard without it being in front of me.