When a new field is added to a class, if this class is synchronized via a Synchro Data Source it seems that sometimes (always ??) the trigger xxx_bu is not rebuilt.
The effect is that when you change the synchro data for the new field, nothing happens during the synchro and the new value is taken into account only when another column is modified.
Investigation showed that:
1) The new field was properly added to the list of synchro data fields (and you can indeed mark it as "update = yes")
2) The triggers are designed to take into account a change in the value of any field (not just the ones marked as "update = yes")
3) But the trigger was not rebuilt, the definition of the trigger does not know about the new field
If we delete the xxx_bu trigger and run the setup again, the trigger is properly rebuilt, taking into account the new field.
Related to [#1115]
Related
Tickets:
#1115