We noticed that, after a relationship field is running as multiple choice, we cant edit this field to single choice, neither turn a single relationship field into a multiple relationship field.
Would like to understand how to set this change after the fields are already in usage. I undestand this type of change may be delicate if we already have multiple values in a field, but it is important to understand if we have any workaround for changing this field setting or if we must create a new one and update through upload.
thanks a lot for your feature request. Yes you are absolutely right, because the realtion field is very delicate it is a dedicated feature called a field converstion, because in a badge job the database properties have to be changed.
But we have already rolled out some field converstion for other fields and with your request the conversion from single to multi relation and vice versa moves forward in the roadmap!
We are evaluating the development time and I will get back to you here with an update.
But in the meantime there is an quite easy way with the automations. Just create a new relation field as single or multi and with a manual run copy the relations from the existing into the new field and after successful migration delete the no longer needed field.
If you copy from a multi to a single relation field, then the first relation in the mulit relation field is set.
@Leo - reviving this old post, as I’m having the same issue right now. I knew this had come up many months ago, and I’m surprised to see it’s still not possible to do a field conversion on the relationship fields (unless I’m missing something)
I can see how a relationship field that allowed multiple could be problematic to change to linking to only one record.
But our case is a field that was originally built with the selection for “Allow linking to only one record”
Now the client has seen a need to allow multiple records selected in this relationship field.
While we could create a new field with alternate settings and run a workflow to update the existing data across, it still creates several other issues.
Dashboard app reports, saved filters, and automations that referenced the original field now all have to be updated because this change of setting is not possible.
I just ran into this problem yesterday and ended up creating a new field with multiple relationships. Now I’ll probably have to find a way to delete the old field after moving all the dependencies.
Thanks a lot for sharing your experience! I totally agree with you. We’ll be addressing this as part of the rollout of the new fields for forms and the redesigned records.
In the meantime, to migrate your existing records to the new field, you might consider using an automation with a manual run. That could help move all the dependencies over in one go before you delete the old field.
