Adding an Attachment from Dynamic View is Not Triggering an Automation

In my Dynamic view, I have allowed users to add an attachment (this is the only update they need to make to the row). In my sheet, I have an automation that is triggered 'when a row is changed' and an 'attachment is added or changed. The action is to change a cell value.

When I add an attachment via the Dynamic view, the workflow will not trigger. However, if I add an attachment via the Grid (and make no other cell changes) the workflow triggers no problem.

The automation does not seem to recognize that adding an attachment via a DV is a row change.

Interestingly, if I first add an attachment to a row via the DV and then add an attachment to a different row in the Grid, the automation will run for BOTH the row that was updated in DV and the one that was updated directly in the grid.

How can I get the automation to trigger from the DV?

I thought about doing a scheduled automation to run once a day, but I get an error message that says workflow timing is unavailable / not allowed for a trigger of an attachment change.

Find more posts tagged with

Attachments

Automations

Dynamic View

Accepted answers

Jason P

Hi @scottreiter

Attachments added through DV don’t initiate automations like when a row is updated or when an attachment is added / changed because DV doesn't log those as row updates, this is a recognized limitation unlike Grid view. Easiest workaround is to add a checkbox column “Attachment Added” & have your users in DV tick off after they add an attachment. Then set your trigger when that checkbox is checked that way the row will show a change and your workflow will continue as wanted – give this a crack, works all good if not I'm at a loss.

Cheers

All comments

Jason P

Hi @scottreiter

Cheers

scottreiter

Than you @Jason P for confirming what I thought was happening. Ideally, I wanted to avoid having to make the user check a box/ fill out a field AND have to add the attachment. I feel the users may forget to update the field. But we can build that out and see what happens. You mention it is a recognized limitation .. has a product feature request been put in for this? (I am happy to submit one) Or is it a no go for some technical reason?

Jason P

Hi @scottreiter

We've held off on rolling out DV for this and a few other reason, shame really as benefits in information flow are amazing. I suggest you submit a product enhancement request, 'squeaky gate gets the oil'

Cheers.

Sign in to join the conversation!

Quick Links

Component react.discussion.discussions had an error.

ref must be one of: categoryID, siteSectionID, category, category/categoryID, category/name, category/description, category/url, category/allowedDiscussionTypes, locale, siteSection, siteSection/basePath, siteSection/contentLocale, siteSection/sectionGroup, siteSection/sectionID, siteSection/name, siteSection/description, siteSection/apps, siteSection/attributes, layoutViewType, discussionID, commentID, page, sort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.