<div dir="ltr"><div><font face="courier new, monospace">Ok my bad... It does as you said Kevin, but I still have a problem. The new </font><span style="font-family:'courier new',monospace">customer field</span><span style="font-family:'courier new',monospace"> </span><font face="courier new, monospace">values are not recognized properly </font><span style="font-family:'courier new',monospace">by the pages Modify.html and ModifyAll.html and it acts as if these fields were without any value (while they appear correctly on Display.html).</span></div>
<div><font face="courier new, monospace"><br></font></div><div><font face="courier new, monospace">When I perform a request with the mysql CLI client, the display is very weird. While it is correct with a graphical client like mysql workbench.</font></div>
<div><font face="courier new, monospace">You can see it on the attached screenshots (the 3 last lines are the custom fields which have a problem).</font></div><div><font face="courier new, monospace"><br></font></div><div>
<font face="courier new, monospace">Any idea why these outputs differ depending on the mysql client and why it interferes with RT behavior ?</font></div><div><font face="courier new, monospace"><br></font></div><div><font face="courier new, monospace"><br>
</font><img src="cid:ii_1441beb2b0cbe25f" alt="Images intégrées 1" width="1348" height="207"><font face="courier new, monospace"><br></font></div><div><br></div><div><font face="courier new, monospace"><img src="cid:ii_1441beb300e3305d" alt="Images intégrées 2" width="1348" height="375"><br>
</font></div>
<div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><span style="font-family:'courier new',monospace">Sylvain</span></div><div class="gmail_extra"><font face="courier new, monospace"><br>
</font></div><div class="gmail_extra"><font face="courier new, monospace"><br></font><br><div class="gmail_quote">2014-02-10 7:11 GMT+01:00 Sylvain Auguy <span dir="ltr"><<a href="mailto:s.auguy@gmail.com" target="_blank">s.auguy@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">Thanks Kevin<div><br></div><div>This is the behavior I was expecting, except that in my case, it adds a new row with the field "disabled = 1"</div><div>Is it a known bug that has been solved in a later version ?</div>
<div><br></div><div>Sylvain</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-02-07 17:51 GMT+01:00 Kevin Falcone <span dir="ltr"><<a href="mailto:falcone@bestpractical.com" target="_blank">falcone@bestpractical.com</a>></span>:<div>
<div><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div>On Fri, Feb 07, 2014 at 11:05:04AM +0100, Sylvain Auguy wrote:<br>
> When I edit a custom field via REST, the associated "ObjectCustomFieldValue" will, by default,<br>
> appear as disabled in the database.<br>
> Is there any reason for that ? How can I avoid it ?<br>
> I use RT 3.8.4.<br>
<br>
</div></div>When you update the value of a custom field on a ticket, the old<br>
ObjectCustomFieldValue is disabled and a new row with the current<br>
value is inserted.<br>
<span><font color="#888888"><br>
-kevin<br>
</font></span></blockquote></div></div></div><br></div>
</blockquote></div><br></div></div>