The Silent Data Loss Problem
One of the most frustrating Adalo bugs isn't a bug at all - it's a configuration gap. Users fill out your form, tap submit, even get a success message. But when you check the database: nothing. No record created. No error logged. The data simply vanishes.
The 6 Reasons Forms Don't Save
1. Missing Create Action on Submit Button
This is the #1 cause. Adalo form components collect input, but they don't automatically save to the database. You must add a Create action to the submit button that explicitly creates a record in the target collection.
Fix: Select your submit button → Add Action → Create → Select your collection → Map each form field to the corresponding collection property.
2. Unmapped Form Fields
Symptom: Record is created but some fields are empty.
Cause: Each form input must be individually mapped to a collection property in the Create action. Unmapped fields are silently ignored - no error, just empty values.
Fix: Open the Create action on your submit button. Verify that every input component is mapped to the correct property. Pay attention to data types - a text input mapped to a number property will silently fail.
3. Form Inside a List Component
Symptom: Form saves data for the wrong record, or saves to the collection but with unexpected values.
Cause: If your form is inside a list item, the Create action may reference 'Current Item' data instead of the form inputs. The context gets confused.
Fix: Move forms to dedicated screens, not inside list items. Pass any needed context (like a record ID) as a screen parameter, and reference the screen parameter in your Create action instead of 'Current Item'.
4. Validation Blocking Submission
Symptom: Nothing happens when the user taps submit. No record created, no navigation.
Cause: If any form field has validation (e.g., 'Required') and the validation fails, the entire action chain is blocked. Adalo shows a small red message near the invalid field, but users often miss it.
Fix: Test the form with all fields filled in. Check that validation rules match the expected input format. For email fields, make sure the user is entering a valid email format.
5. Relationship Not Set on Create
Symptom: Record is created but doesn't appear in filtered lists or belongs to the wrong user.
Cause: If your collection has a relationship (e.g., 'belongs to User'), you must set that relationship in the Create action. Otherwise, the record is orphaned - it exists in the database but isn't linked to any user.
Fix: In the Create action, set the relationship field to 'Logged In User' (or the appropriate context). This is the most commonly forgotten step in Adalo form setup.
6. Action Chain Order
Symptom: The form navigates to a confirmation screen before the Create action completes.
Cause: If you have a Navigate action before the Create action in your chain, the navigation fires first and the Create action is interrupted.
Fix: Always put database actions (Create, Update) BEFORE navigation actions in the chain. The correct order: Create Record → Update User → Navigate to Confirmation.
Testing Forms Properly
- Fill out all fields with test data
- Tap submit
- Immediately check the database in Adalo's backend (Database tab → select collection)
- Verify the record exists AND all fields have correct values
- Verify any relationships are properly set
- Check that filtered lists (e.g., 'My Orders') show the new record
Advanced: Multi-Step Forms
For complex forms (onboarding flows, multi-page wizards), create the record on the FIRST screen with minimal required fields, then use Update actions on subsequent screens to fill in additional data. This prevents data loss if the user abandons the form midway.
Need Expert Help?
If your forms involve complex logic - conditional fields, multi-table writes, file uploads, or payment integration - the configuration gets intricate fast. Rehost builds production-grade Adalo forms with proper validation, error handling, and data integrity guarantees. Get Expert Rescue →
FAQ
Why is my Adalo form not saving to the database?
The most common cause is a missing Create action on the submit button. Adalo forms don't auto-save - you must explicitly add a Create action, map every field to a collection property, and set any required relationships.
How do I connect a form to a database in Adalo?
Select your submit button → Add Action → Create → Choose your collection. Then map each form input to the corresponding collection property. Don't forget to set relationship fields (like 'belongs to Logged In User').
Can I validate form fields in Adalo?
Yes. Adalo supports basic validation on text input components: Required, Email format, and Min/Max length. For complex validation (like checking if a username is already taken), you need a Custom Action that queries the database before creating the record.