It seems there is some inconsistency with how Baserow treats semi-colons upon copy-paste in linked fields.
In short: if one established a link with a field with a semi-colon its name, it produces errors upon trying to copy it back into the linked field column, whenever there is an intermediate step (like copying the value to a text field or an external app first - and then copying it back to Baserow)
Also:
Commas and semi-colons seem to have a different behaviour with copy paste.
When one copies the value from a linked field to a text fields - Baserow adds " " for values with commas, so that when one copies the value back to the linked field column, the value is recognized correctly.
However, for semi-colon in linked fields, Baserow does not add the quotations marks automatically (not even in exports), so when one attempts to paste the value back into a linked field from a text field or external source - an error appears:
This does not seem to happen when one attempts to paste many values (one of which includes a semi-colon) when all are separated by commas.
Adding quotation marks to the pasted value with semi-colons seems to solve the paste issue, but it is very annoying when dealing with larger sets of data, especially when part of the workflow requires the use of other apps. The other solution is to not use semi-colons but enforcing that among regular users may be tricky.
Hey @dev-rd, thanks for reporting this. I’m having some problems reproducing the exact scenario. When you’re talking about a field with semi-colon in the name. Are you then talking about the field name, or the cell value? It would be appreciated if you can share a screenshot of the problem, or steps on how to reproduce it.
more on the json import
in the preview the values with commas and semi colons (apparently, regardless of the use of quotation marks) are treated as separate values
but enforcing that among regular users may be tricky.
