Learn how set up mirroring a field from one input form to another
Mirrored fields allow users to mirror a value from a field in form A to form B. This also enables them to use smart fields across input forms and workflow steps. This feature is available for scheduled events, surveys and (S)AEs.
Definitions:
- Source field = editable input field where data can be entered. This is mirrored to the destination field.
- Destination field = non-editable input field that shows/mirrors the value of the source field.
1. Form setup (step 3)
Before the mirroring function can be configured, it is necessary to set up both the source and the destination field inside the input form set-up.
⚠️ Please note that if you choose any of the following field types as your source field...
... the matching destination field must be either a short-text or a number field. For these two input field types, you can use their respective field type. ⭐ For the drop down and single choice fields, the option label will be mirrored to a short-text field and the option value will mirror to a number field, if all values of this particular field are strictly numeric. If date or date and time fields, are to be mirrored, the destination field must also correspond to the respective field types. In the "Mirrored table rows" tab, you can configure row mirroring from a defined source table. During data entry, site users select which rows to mirror into the (S)AE. Learn more in this article: How do I set up mirrored table rows from scheduled events to (S)AEs? Field types that cannot be used for mirrored fields (yet):
|

![]() | Set up your source input field inside the form set-up (step 3). |
![]() | Set up your destination input field inside the form set-up (step 3). ⭐ We recommend giving the destination input field a similar name to your source input field to facilitate the mirroring set-up in step 5 and to easily identify it in your data exports. |
⚠️ Please note that the source and the destination input field must be placed on two different input forms. |
2. Mirrored field setup (Step 5)
Once you have set up the source and destination field inside your forms, you can start to set up your mirrored fields function.

![]() | Navigate to the Trigger Events in Step 5. |
![]() | Select the "Mirrored fields" tab here. |
![]() | Click on "Mirror a field". |
![]() | Name your mirrored field comprehensively so you can identify it later on. |
![]() | Select the source form and field. Afterwards, please choose the destination form and field that the source value should be mirrored to. ⭐ Note that the form of the destination field must always be placed after the source form and it is not possible to place the source and destination field inside the same form. |
![]() | Check your set-up using the preview functionality. |
![]() | Don't forget to save! |
3. Mirrored fields: Good to know
⭐ Utilizing field mirroring to enable smart fields across forms The mirrored fields functionality enables you to perform smart field calculations with input fields that are placed across different forms. Simply mirror all fields that you wish to include in your calculation as destination fields into the same form. For this purpose you can, for example, create a data calculation sheet at the end of the workflow and exclude all collaborator roles that should not see this input form via the "excluded collaborators" setting in the input form setup (step 3). |
⚠️ Amendments/Updates to an active project: Please note that when a mirrored field is added to a study that already contains data for the source field, mirroring for these subjects needs to be triggered manually by updating any field in the form in which the source field appears. When updating the option labels of a single-choice or dropdown field (source field) in step 3 and the labels are mirrored to a text field (destination field), the updated option label will automatically be synchronised with the destination field. However, when updating the option values of a single-choice or dropdown field (source field) in step 3 and values are mirrored to a numeric field (destination field), the updated option values will not be updated in the destination field. |
✉️ Still have questions? Feel free to contact your Customer Success Manager or email us at support@climedo.de. |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article








