Having the ability to remove the "Submit" button on Smartsheet Forms would be helpful in cases where users need to go to a form to submit a request, but where we have exceptions to the rule. If they answer "Yes" to a specific question at the top of the form, then we show a dependency child question that says "Please reach out to your Project Manager to manage this request in your project plan instead..." We don't want the user to still "submit" the form as it doesn't serve a purpose. All it does is send to the intake sheet with no data since it's not a valid submission. Can we have the ability to "remove" the Submit button "based on dependency" questions asked at the form?
Thank you
I'd like SS to allow form logic that prevents someone from submitting a form. I can put notes all day that someone doesn't submit the form and does something else instead, but it's too easily missed. I'd like form logic to allow for the "Submit" button to be disabled under specific conditions.
I hope you're well and safe!
Would it work to use the Required option?
I hope that helps!
Be safe, and have a fantastic week!
Best,
Andrée Starå | Workflow Consultant / CEO @ WORK BOLD
✅Did my post(s) help or answer your question or solve your problem? Please support the Community by marking it Insightful/Vote Up, Awesome, or/and as the accepted answer. It will make it easier for others to find a solution or help to answer!
SMARTSHEET EXPERT CONSULTANT & PARTNER
Andrée Starå | Workflow Consultant / CEO @ WORK BOLD
W: www.workbold.com | E:andree@workbold.com | P: +46 (0) - 72 - 510 99 35
Feel free to contact me for help with Smartsheet, integrations, general workflow advice, or anything else.
A required option won't help in this scenario because we don't want the user to submit a form. How do we vote for idea? I'd really need the option to eliminate the submit button on a form.
I would also love to hide the submit button. I'm using a form with one drop down and logic to reveal email templates for various things for my team. It's been useful for them and they can't accidentally edit them or change the templates, but the submit button can cause accidents/confusion sometimes.
This would be useful for me too!
This would be a super helpful feature if we could write enough logic into this to remove the submit button.
Michelle Choate
michelle.choate@outlook.com
Always happy to walk through any project you need help with!
I agree - I have a form that we are going to stop using, but I want to add a message indicating where the new process resides on the existing form so anyone with a saved link will see the message but be unable to complete the form.
Logic has the first question required prior to anything else showing. Hiding the first question, leaves just the submit button, which looks stupid.
I would like the Product team to enable the feature that the submit button is hidden and it shows up at the very end when all the logics in the forms are satisfied. As of now, you can only make a field required, but you can not make any if statement (for example if a selected "date" field is not within a range the users won't be able to submit the form)
This would be an extremely useful function to add.
There are myriad reasons why a given form should not be submitted because the user is putting in data that violates business rules for the underlying data. Simple example entering an expected completion date that is in the past. Presently only thing you can do is to use conditional logic to display an error, but the user still has ability to hit submit with the error present.
Adding ability to control when the submit button is lit would facilitate validating the date before it is submitted.
I would set a flag saying there was a form error present based on conditional logic for the data fields. When the flag is turned off, the submit button would become active.
This feature would be helpful for us!
We have two different forms for types of requests. We have an info box that tells people to use the other form if they need help with our other service, but having the Submit button disabled based on certain criteria would be a timesaver and less frustrating for us and our users.