T
Twenty3mo ago
L.Num

Field rename problem

Hello! Unfortunately new problem appeared.
I moved to 1.0.2. And with crm web interface recreated all workspaces from scratch. I have workspace Set tasks, which has related fields with other workspaces like Products, Managers etc. So in setTasks for task record I could select current product, manager etc. Also I have webhook on update setTasks event. So I can see fields in request data. Steps to Reproduce: In workspace setTasks I changed name of field from "manager" to "responsible manager". Expected behavior: Field name changed, new requests have ID - responsibleManagerId instead managerId. Actual behavior: - In interface name changed. However with webhook request I see that previous field name stayed (managerId).
- I can not choose manager in renamed field "responsible manager" in workspace setTasks, when I select him - error pops and displayed value sets to untitled. - When I at Managers workspace - error 'column does not exist' pops. My workspaces' field types and errors are on attached screenshots. Not sure if it's related to previous issue: https://discord.com/channels/1130383047699738754/1387927633622208644/1387927633622208644
No description
No description
No description
No description
No description
2 Replies
Guillaume
Guillaume3mo ago
"responsible manager" is a reference to another column right ? therefore it's waht we call a "relation". The "relation" fields should not be updated. We released too early this feature and it is not ready so far, sorry. We are removing this feature so the issue will not be possible (until we have a clean version) In the meantime, do not update the names of the relations ! Ping @charles
charles
charles3mo ago
Yes, it's a known bug, it will be patched in 1.1 let's not rename relations in the meantime

Did you find this page helpful?