Rows added/Changed Trigger automation is not working based on columns referencing another sheet?
I have a sheet that is supposed to move rows to another sheet if a column is checked.
Well its not working. It only works if I manually change a cell within that row.
In the second screenshot above, in the "d" column, there's a lookup formula that checks if the column to its left is not blank. If column "d" is not blank then it will be checked. The column "Ready to archive" is referencing another sheet. So its a vlookup that based on if a project is in another sheet. If the project is not there, then its blank.
When column "d" is checked I want that row moved and its not happening.
Some background on this process that may help:
This is an archive process that's going on between multiple sheets.
Sheet A is the main sheet. This is the sheet where the user manually checks a box and that row will move to an archive sheet (Archive Sheet A).
Sheet B, which is shown above has data based on sheet A. Sheet B also has its. own archive sheet (Archive Sheet B), which is where I am trying to move the rows to. So Sheet B looks in Archive Sheet A, and see if a project is in there (To be Archive Column). If the project is in there those column fields are filled with data as seen above.
The workflow automation should look at that check box and see that its checked and move the rows. I think the trigger is not working. Remember, that check box was unchecked on sheet B at first until I move the rows from Sheet A to Archive Sheet A
Smartsheet is not counting when that check box is checked as a row change. I tried other methods as well, like set my automation condition to when column "to be archived" is not blank. Same results.
Best Answer
-
@mbsamuel6 You are probably bumping into this restriction, based on the cross references you have:
dm
Answers
-
@mbsamuel6 You are probably bumping into this restriction, based on the cross references you have:
dm
-
Yup you are absolutely right.
Looks like system columns will help with this
-
@mbsamuel6 When I encountered this issue, I ended up creating a series of workflows that basically run every hour to check a condition and move the row if the condition is met. Those workflows use a trigger of "When a date is reached" instead of when rows are added or changed.
if your process is simply archiving data, that might work. Just run it overnight, cleaning up all the rows that meet your condition.
Cheers,
dm
-
Thanks Dale and yes that is what I concluded.
I just tried setting up a system column and having the workflow trigger be that. Didn't work.
So now I my plan is to change to trigger to "when a date is reached" and have it run once every day in the morning. That should honestly be enough. Thank you so much
Categories
- All Categories
- 14 Welcome to the Community
- Customer Resources
- 64.9K Get Help
- 441 Global Discussions
- 139 Industry Talk
- 471 Announcements
- 4.9K Ideas & Feature Requests
- 129 Brandfolder
- 148 Just for fun
- 68 Community Job Board
- 494 Show & Tell
- 33 Member Spotlight
- 2 SmartStories
- 300 Events
- 36 Webinars
- 7.3K Forum Archives