On clicking a button, i need to add a new record in another linked base, while passing parameters like the informations related to the record the user is on, to the new linked record - alongside with the user (so that the new record in the other base is linked to that user automatically).
This request is covered by a workaround, and it is on the roadmap as live.
Problem
From a record, a button should create a row in another database. The new row should receive fields from the record the person is on, and it should be linked to the person who clicked.
Why this is a workaround
A button in the app does not itself write a row. A workflow does. The button is the trigger, and Create record is the step that writes the other database, including the relation back to the current row and the relation to the logged-in user. That is the same job as a dedicated “create in another database” button, built from the workflow that already ships.
How to use it
- Open the screen for the source record. Add a button. Title it with the action, for example Create follow-up.
- Open Automation, then Workflows, and create a workflow.
- Set Trigger to Button. Set Where it happens to Button. Set Target to that button.
- Add a step and choose Create record. Choose the destination database.
- Set each field the new row needs.
- Copy values from the current record: name, dates, status, and any other field that should travel with the click.
- Set the relation that points back at the source record to the current row, so the new row stays linked to what they were viewing.
- Set the user or person property to the logged-in user, so the new row belongs to the person who clicked.
- If the source row should change at the same time, add Update record and set those fields on the current row.
- If a person should be told, add Notify.
- Publish the app.
- Sign in as a test user, open one source record, and click the button.
- In the destination database, confirm the new row exists, the copied fields match the source, the relation points at that source row, and the user property is the person who clicked.
When one click should create a fixed checklist of child rows, use Create related records and choose the parent-to-child relation and the template rows, instead of stacking one Create record step per child.