We have this custom object and a custom attribute in it.
In the GUI in Administration there is a default.
When we try to change or delete the default the current value is returned after save.
When we create a new instance the field is populated with something else.
There is no process we can relate either behaviour to.
In the database the field does not have a default in odf_custom_attributes
There is a trigger for auditing the object and that attribute.
Have not done a trace yet.
Where else could we look for the reason not being to set a new default and the new instance being populated with something other than the default?