Submit action?

[rleinen]

I have a form with three buttons calling custom actions. Is there a way to have each of them also submit the form so that the data gets saved?

[Jeff_Hager]

No, I don’t think that’s going to work. Trying to use a built in form outside of what it’s intended for will make things more complicated. The only way to submit data in a built in form is the use the built in submit button.

What I would advise is to set up a custom form, which will allow you to use your buttons how you intend for them to be used.

How do I create a custom form?

I’m just dropping this here so I have something to refer people to when they ask. This is a simple concept app (copyable), that demonstrates the following techniques: Building custom forms for adding and editing list items (as an alternative to the native forms provided by Glide) Preventing duplicate new entries using User Specific Columns and Relations Enforcing mandatory input items The use of visibility conditions and user specific booleans to control user flow There is nothing particula…

[rleinen]

Jeff, thank you for the reply. Somehow I’m thinking that I should be able to have a simpler solution. I’m essentially just wanting to have two options on a form - one to assign a person to the work order, the other to complete the work order. In each case I auto-populate a date and a status field, and then trigger a zap. Is there an easier way to do this than I’m trying? FYI, I’m a newbie to Glide.

Thanks for your help!

[ThinhDinh]

Maybe you can have a choice component for the status, say “Pending” and “Completed”. If “Pending” then show another choice component to assign a person?

Then trigger a zap based on the chosen status.

[rleinen]

That’s a slick idea. It would be nice if the actions would allow more than one decision tree. Maybe that will come in the future.

[David_Gabler]

@rleinen

actions would allow more than one decision tree

There are a lot of posts about that, but this request has too few votes:

Better and more consistent IF THEN logic

I’ve spent the past few days trying to work out some IF/THEN logic for a side project. The problem is that this is something I could have worked out in a matter of a few minutes with actual code. I’m running into several limitations with the current IF/THEN logic we currently have in Glide. First of all there inconsistencies between what’s possible with an IF/THEN column, and what’s possible with If/Then logic in visibility conditions or actions. Most importantly, an IF/THEN column only all…

[rleinen]

I voted for it