Most forms are a submission of data into a database and then the form clears, waiting for another submission.
I’m trying to find a way where I can basically create a normally looking form with all the usual field types, but when the user ‘submits’ the form, it send it to the database for storage, but the fields themselves don’t become blank. Instead the data is held within the forms and the user can return to edit this data later which will then edit the corresponding data being held in the database.
It’s a bit like an address field where some websites ask you amend the form where the address is already pre-filled in the fields and when you ‘submit it’ a popup saying it has been saved appears and this reflects in the form, with the new edit.
Yes exactly, to see what they put before, and amend it, and save the form so when they return to it, they say what they updated it to in their most recent edit.
Haven’t tried initial content, can try that if that what its purpose is.
Hi,
You are looking for something which can be seen days after, for example. It’s that ?
Can’t you put a dynamic content into the input (on placeholder) ?
Yannick
Where can I find more information on using auto-binding?
@ecomerss Yes, the content should remain there indefinitely.
I’m wondering, if the user resubmits the data, it is possible for the data to create a new entry with a new date and time, the data of which is then accessible to the user via another data view.
Is there a difference between initial content and auto-binding?
My understanding is that autobinding saves the data as the user is editing it, and keeps it there. Initial content is me as the admin entering initial data, maybe as an instruction to the field before the logged in user enter their data.
