You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of the sync compares objects and their fields in the DB with the standard object defined in the code. To do that and avoid any issue with the diff while maintaining the correct order, we map objects and fields with their names. However, because of that we can't easily rename them and the sync will interpret them as different entities.
Technical inputs
First improvement would be to introduce a new column: standardFieldId? The value will never change and will allow us to map standard fields with rows in DB even if they've been renamed.
Scope & Context
The current implementation of the sync compares objects and their fields in the DB with the standard object defined in the code. To do that and avoid any issue with the diff while maintaining the correct order, we map objects and fields with their names. However, because of that we can't easily rename them and the sync will interpret them as different entities.
Technical inputs
First improvement would be to introduce a new column: standardFieldId? The value will never change and will allow us to map standard fields with rows in DB even if they've been renamed.
cc @magrinj @charlesBochet
The text was updated successfully, but these errors were encountered: