MUST it be the case that when a row is updated via a form (app), the entered data is updated field by field, virtually in real time?
Or can multiple fields be changed one after the other, with a “Submit” button at the bottom that aggregates all changes to the row.
(Make doesn’t like the option of making changes field by field at all… it triggers the scenario again and again)
When using a form (app) to submit a new record, users can fill out multiple fields and then submit the changes at once by pressing a “Submit” button. The updates are sent to the database in aggregate, not field by field in real time. Data is only written to the table when the form is submitted.
Forms cannot be used to update an existing record. Can you provide more information like a screenshot about the problem?
[Just to let you know in advance: I apologize, this text was translated using a machine translation tool. I don’t have much experience writing in English, especially when it comes to technical topics.]
Thank you very much for the quick reply.
That’s correct for creating a new entry; the form (in the app) does indeed have a submit button after entering the data.
However, this submit button is missing when editing an existing entry—and that’s precisely the problem I’m having.
Attached are two screenshots of the input screen I’m referring to.
<<<ONE attached: “An error occurred: Sorry, new users can only put one embedded media item in a post.”>>>
See here: Edit entry (Eintrag bearbeiten)
There is no submit button at the bottom; instead, every change to a field is immediately sent to Make (via webhook).
It would be very helpful if there were a submit button here as well.
OK, you are not talking specifically about a form (neither a web form nor a form page in the app), but you are commenting on the way SeaTable handles modifications in existing records.
When you edit an record in the base editor or in an app, the modification is sent to the server and saved. Every modification is a separate request. This is the way SeaTable works (for good reasons).
I understand this causes problems with the way you have set up your Make workflow. In this case, you must modify your Make workflow.
Just one idea: Add a button that modifies a record in a particular row. Use this modification to trigger your Make workflow. You can then add this button in your app.
Can you work with this input?
Thanks for the reply 
Yes, I am talking specifically about forms. The idea of the new column as a checkbox, which would then trigger make.com, is probably already possible in principle, but the rationale is still vague. Because when you first create a form, there’s also a submit button and the field entries aren’t immediately written to the database individually — as would otherwise be the case if you were writing directly to the database (without a form).
And the form for edits/changes behaves unexpectedly differently than the form for the initial creation. 
If this isn’t intentional, I haven’t overlooked anything nor accidentally configured something incorrectly in the app.
Why “unexpectedly differently”? Why do you expect two DIFFERENT page types to behave INDIFFERENTLY?
As I said in my previous post:
So SeaTable, or the table/form page type for that matter, are not going to be changed. You’ll have to deal with the way SeaTable works.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
Do it like thousands of other people who have used SeaTable to develop powerful processes and get their ideas and tasks done more efficiently.
