<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div id="AppleMailSignature">Sure. We have dozens of clients adding custom fields possibly. We also add a few custom fields as well as code changes. There would be conflicts in IDs assigned. </div><div id="AppleMailSignature"><br>Sent from my iPhone</div><div><br>On May 8, 2018, at 1:49 AM, nilay khatri <<a href="mailto:nilay.spartan@gmail.com">nilay.spartan@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">Why there would be a conflict with Ids?<div><br></div><div>Upgrading from one version to another does not create records or something similar to crmentity table or field tables.</div><div><br></div><div>Could you put some more light on the conflicts and the upgrades?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 7, 2018 at 10:31 PM, Chris Thompson <span dir="ltr"><<a href="mailto:cthompson@moderas.org" target="_blank">cthompson@moderas.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72"><div class="m_-3723870660113244063WordSection1"><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">How are people managing database conflicts when updating a client from one version of custom vtiger to another? Issues with IDs for crmentity, vtiger_field, etc. <u></u><u></u></p></div></div>
<br>______________________________<wbr>_________________<br>
<a href="http://www.vtiger.com/" rel="noreferrer" target="_blank">http://www.vtiger.com/</a><br></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span><a href="http://www.vtiger.com/">http://www.vtiger.com/</a></span></div></blockquote></body></html>