Forum Discussion
QuickBaseCoachD
Qrew Captain
Yes, you got it. I would agree that it will save some micro seconds to only update records which need to be updated so I agree with the filter (it also helps with sort of self documenting what the saved table to table import is doing, as it will be less obvious 2-5 years into the future when you or someone else is trying to remember what that saved table to table import is doing).
Yes, since it's only 36 fields, then I would set like 35 to Do Not Update so just update that one field, just to make it even more obvious what the import is doing.
Yes, since it's only 36 fields, then I would set like 35 to Do Not Update so just update that one field, just to make it even more obvious what the import is doing.
AdamKrzyzanek
3 years agoQrew Captain
I come to same problem and previously I use table-to-table import but it is not sufficient to my needs.
Process description:
1) After user mark completion with "check" box I have 1 automation which capture User Name and Date of Completion.
NOTE: It works for 95% of cases, but sometimes it fails to capture User Name or Completion Date.
2) Then I run "Daily Workaround" automation with table-to-table import - when checkbox is marked and user name not capture I just copy name from field "Last Modify by"
Issue is that when Automation touch record it capture "automation owner" name in "Last Modify by". For this purpose I would like to use automation as it gives possibility to copy "Old Values"
Any potential solutions?
------------------------------
Adam Krzyzanek
------------------------------