A colleague of mine has pointed out a potential issue around derived fields which can be summarised as follows:
Derived fields, when created, have a hidden attribute that is the length of the field they are deriving from AT THE POINT THEY ARE CREATED. If you subsequently change the length of the field being derived from, the derived field still retains the original length and will cause timeouts and “unknown errors” when trying to save things to the field being derived from that exceed the original length.
I raised this issue with support who explained that the link between the source and derived field is not dynamic i.e. the derived field only takes its attributes from the original source field which explains the scenario above.
The only solution found is to deleted the derived fields and re-introduce them. The obvious issue with this is that it not easy to re-populate derived fields to hundreds / thousands of records so we risk losing data from workspaces.
My request is therefore to introduce a dynamic relationship between source and derived fields.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.