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
pgpjEANdW1Gsf.pgp
Description: PGP signature
