Thanks Kevin This is the behavior I was expecting, except that in my case, it adds a new row with the field "disabled = 1" Is it a known bug that has been solved in a later version ?
Sylvain 2014-02-07 17:51 GMT+01:00 Kevin Falcone <[email protected]>: > On Fri, Feb 07, 2014 at 11:05:04AM +0100, Sylvain Auguy wrote: > > When I edit a custom field via REST, the associated > "ObjectCustomFieldValue" will, by default, > > appear as disabled in the database. > > Is there any reason for that ? How can I avoid it ? > > I use RT 3.8.4. > > When you update the value of a custom field on a ticket, the old > ObjectCustomFieldValue is disabled and a new row with the current > value is inserted. > > -kevin >
