Hi Guido,<br><br>vtiger CRM migration will not overwrite any of your changes to UI types or field types, unless the migrating version has some changes on the same field and has something to do with the uitype or field type changes.<br>
<br><div class="gmail_quote">On Tue, Aug 24, 2010 at 5:29 PM, <span dir="ltr"><<a href="mailto:machianera2002-altri@yahoo.com">machianera2002-altri@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div style="font-family: 'times new roman','new york',times,serif; font-size: 12pt; color: rgb(0, 0, 0);"><div>Hi,</div><div>Perhaps this issue was already discussed before, but I couldn't find the right answer therefore I am using the developers lists.</div>
<div>As per obtaining the proper number formatting, I had to change in the 5.1.0 database some registers' UIType (i.e. from 1 to 7), or modifying the table field type (i.e. from 25,3 to 25,2).</div><div>My questions are:</div>
<div>(1) When planning migration from my current 5.1.0 installation to 5.2.0 should the migration keep my table modifications, in both situations (register and/or field type)? Or the migration tool must find the table structure/register contents (UITypes) as originally deployed?</div>
<div>(2) Is there a way to keep vtiger informed about table structure/UITypes changes I would like to keep as standard for
future releases?</div><div>Thank you,</div><div>Guido</div><div><br></div><div></div>
</div><br>
</div><br>_______________________________________________<br>
<a href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a><br></blockquote></div><br><br clear="all"><br>-- <br>Regards,<br>Asha<br>vtiger Team<br>