nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Smartsheet Community

Connect with peers, share your expertise, and inspire what’s next in Smartsheet — from proven practices to practical how-to insights from fellow users and product experts.

Form Submission Triggered Full Sheet Approval Automation

EOsborne

Just had a single form submission trigger an approval automation for every row in the sheet.

The sheet is set up to send an approval automation once a user submits a request via form. In this case, once the form was submitted the automation triggered for every row in the sheet where "Principal Approval" was blank, even when "Project Name" was not added or changed. This workflow has been in place for over a year and it's never done this before.

Anyone have any idea what happened here and how to prevent it from happening again?

The automation:

Example cell from the "Project Name" column that has not been changed in years and shouldn't have triggered this workflow, but did anyways:

Find more posts tagged with

Forms

Automations

Approval Request

Accepted answers

All comments

Adrien Leduc

Hi @EOsborne

Is your form populating rows on top or bottom of your sheet? I've had the top option do something similar in the past, so I do not use it anymore…

EOsborne

The form is populating at the top, so maybe that is the culprit.

Adrien Leduc

Have you changed that setting? any improvements?

Paul Newcome

@Adrien Leduc I've seen you mention this before. How many times has this happened to you? I have the majority of my forms submitting at the top of the sheet and have never had this issue. Just trying to get a feel for how common this may or may not be.

Adrien Leduc

To be honest, after it happened once (and consistently at the time), I didn't want to take the risk anymore, given hundreds of emails depend on it.

Based on what I'm reading here I assume that stopped happening at some point, and that other factors might be at play, but I can't put my finger on it.

bieng25

Sorry to bring up an old topic, but has this resolved for you? I've encountered what appears to be the same issue.

EOsborne

I added in extra parameters into my automation to try to prevent it from happening again, and everything has been working as it should over the past week. I still don't understand why the automation was triggered outside of its parameters so I can't say for sure that the issue has actually been fixed.

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, category/bannerImageAlt, locale, siteSection, siteSection/basePath, siteSection/contentLocale, siteSection/sectionGroup, siteSection/sectionID, siteSection/name, siteSection/description, siteSection/bannerImageAlt, siteSection/apps, siteSection/attributes, layoutViewType, discussionID, commentID, page, latest, sort, sortType, lookupSort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.