Form Entries

introduction entries are the submissions customers send through your sparklayer forms from the entries area, you can review responses, update data, add any admin internal information against the entry, monitor automation workflows, and manage the full lifecycle of each submission entries remain linked to the form version they were created with — helping ensure data consistency even when forms evolve over time 👀 viewing entries to access submissions open the forms listing page in sparklayer click view entries in the row matching the form you want you’ll see a table listing all submissions for that form entry table overview the entries table can be configured using views views allow setting up saved filters and other options to control what entries are shown in the table you can add as many different views as is needed for different purposes by default, each form comes with two views default view shows the submitted at date time, and first three fields in each entry all fields shows all columns this is mostly used for exporting data as a csv you can create a new view or edit existing ones to modify what columns are shown, as well as apply filter criteria to find specific entries for example, you might want to setup a "awaiting review" view for your registration form opening an entry click any row to open the full entry view this shows all field responses grouped by page system metadata workflow activity attached files revision history the entry view reflects the form version used when it was submitted, so fields always appear in the correct structure 🔄 entry lifecycle & statuses entries start with a status of "draft", and remain in that status until the entry is validated, and submitted at this point the entry changes into the final "complete" status for tracking other status information against entries, you can add administrative internal fields to your form by going to the internal fields form builder tab ✏️ editing entries admins can edit entries after submission — useful for correcting mistakes, updating account details, or continuing internal workflows how to edit open the entry click edit update any editable fields save your changes what happens when an entry is edited when you save changes field validation runs again conditional logic re evaluates related workflows may trigger (depending on setup) a new revision is created for audit purposes it is highly recommended to always add a message to specify the reason for the admin edit of an entry editing restrictions some fields cannot be modified read only fields system generated values calculated or derived fields locked workflow outputs if a field appears disabled, it is likely controlled by the form configuration or automation logic 🧾 entry revisions sparklayer tracks changes made to entries by admin edits automatically revisions help you see who made changes restore previous values understand workflow updates over time each revision records data captured example editor admin or system timestamp when the change occurred field updates previous vs new values this is particularly useful for b2b onboarding or approval workflows where entries evolve over time ⚡ entry actions delete an entry removes the submission permanently ⚠️ deleting an entry will remove associated files delete workflow history cannot be undone export data first if you may need it later 📎 files & attachments if your form includes file upload fields uploaded files appear inside the entry click to preview or download file details include name, type, and size files remain linked to the entry and follow the same permission rules deleting the entry removes all associated files 📊 entry metadata each submission stores system level information metadata description entry id internal unique identifier entry key key required to see and edit the entry in the form client form version version used at submission time created at draft entry creation date when user started filling out updated at last change timestamp submitted at when user submitted the entry status current entry state 🔎 workflow runs & debugging the entry view includes a history of workflow runs you can see when a workflow started whether it succeeded or failed duration and logs step level outputs if a workflow fails open the failed run check which step failed review input data and error messages correct the entry or workflow and re run this helps diagnose issues without needing developer access