How do you share a saved form without creating a relationship loop?
Share a saved form from an Adalo list by binding the Share action to a direct text value, or use Deep Linking Share when the recipient needs a record URL.
A Share action needs a final text value or URL, not an open-ended relationship path. For a text summary, add a Share Text property to the submitted-record collection, build that text from the form values when the record is created or updated, and bind the list item's Share action directly to Current Submission > Share Text. Use Deep Linking Share instead when the recipient should open the saved record in your app.
Treat sharing as the last step of a record-selection path. The list or detail screen establishes which submission is current; the Share action then needs a concrete payload. For plain text, save a deliberately formatted Share Text property on that record and bind directly to it. For an in-app destination, configure Deep Linking Share with the current record's data and ID. In both cases, test multiple records and exclude private fields.
The intended outcome
Each list item shares the correct saved submission as readable text or as a deep link without traversing a circular relationship path.
Requirements
- A collection that stores each submitted form as its own record
- A list or detail screen with the current submitted record available
- A decision between sharing readable text and sharing a link back into the app
Step by step
- 01
Choose text or link
Use a Share Text property for a portable text summary; use Deep Linking Share when the recipient should open a particular record in the app.
- 02
Add a Share Text property
For text sharing, add a Text property named Share Text to the collection that stores the form submissions.
- 03
Build the summary
In the form's Create action, compose Share Text from the submitted values with clear labels and line breaks; update it again whenever an editable submission changes.
- 04
Place Share in record context
Put the share button inside the list item or on a detail screen reached from that item so Current Submission is available.
- 05
Bind directly to text
Set the Share action's Source to Current Submission > Share Text. Do not continue through Logged-in User or another relationship after reaching the saved record.
- 06
Configure a deep link if needed
For record URLs, add More > Deep Linking Share and fill its data fields with Magic Text for the current record, including the required record ID.
The underlying logic
The relationship identifies which record is current; the Share action still needs that path to terminate at a Text property or a generated URL.
Persisting a Share Text summary makes the button's source predictable and prevents the editor from repeatedly traversing user-to-record relationships.
Deep Linking Share is a different outcome: it generates an app URL from the screen's available data so a recipient can open the record rather than receive its contents as plain text.
Data model
| Collection | Important properties | Relationships |
|---|---|---|
| Form Submissions | Original form fields; Share Text (Text) | May belong to one User, but the Share action should terminate at Share Text |
What still needs checking?
- This answer is forum-native; it separates the accepted text-sharing pattern from Adalo's currently documented Deep Linking Share action.
Common failure modes
The Magic Text menu keeps looping
Stop at the saved record's Share Text property. A relationship is not itself shareable; the final selection must be Text or a URL.
Current Submission is unavailable
Move the button into the list item or navigate to a detail screen while passing the clicked submission so the screen has the correct record context.
Older records share nothing
Populate Share Text for existing records or provide a fallback; adding the property does not backfill records created earlier.
The shared text is stale after editing
Update Share Text in the same Update action that saves the edited fields, using the new values.
A deep link opens the wrong record
Check that each Deep Linking Share data field uses Magic Text from the current list item or detail-screen record, especially its ID.
Testing checklist
0 of 8 checked on this device
Current limitations
- The accepted answer documents the direct Share Text pattern, while Adalo's current official page documents Deep Linking Share; the exact current text-share controls still need a builder screenshot.
- Share Text is a stored snapshot and must be updated when the underlying fields change; existing records require a backfill.
- A shared payload can expose form data outside the app, so sensitive fields and authorization behavior require an explicit privacy review.
Current evidence screenshots have not yet been added. Treat the guidance as documented or legacy material according to the status shown above.
What the Adalo community is reporting
These are concise editorial summaries of public forum posts—not endorsements or independently reproduced results.
How do I add a share button for a form stored in a list?
The accepted answer says the Share source must resolve to text or a URL and recommends storing a Share Text summary on the submitted record instead of navigating through relationships.
Boundary: The reply does not show the current builder controls, and the separate Deep Linking Share alternative must be configured against the app's own record data.
Nb317 (question) and Ali-Bazzi (accepted answer) · June 2026Sources and status
This page was last reviewed on Aug 14, 2026. Its current status is Documented from current sources.
Verification owner: Automatically organized from an accepted forum answer; monitored for corrections. Next review: Oct 14, 2026.
Changelog
Automatically posted from a solved Adalo forum topic; corrections are monitored on the live site.
Report this answer.
Forum answers post automatically. If a step is wrong, outdated, unclear, or missing an important boundary, send the exact correction and the editor will check the live page.
Report a problemDid this solve your problem?
Never deal with an Adalo problem again.
Rehost becomes the monthly team behind your app. Fixes, releases, integrations, and ongoing changes have an owner.
See monthly managementBring us the messy version.
Describe what you expected, what happened instead, and what you already tried.
Ask Adalocado
