[Vtigercrm-developers] Managing conflicts

[nilay khatri]

Yes, there would not be any changes to the Record ID or fieldnames etc..
All your custom fields, Module, Record entries, etc.. will remain intact.

On Tue, May 8, 2018 at 6:18 PM, Conrado Maggi <comaggi at gmail.com> wrote:

> It shouldnt. Vtiger migration starts with your existing DB and adds/remove
> rows and columns to bring that db schema to the last version.
>
> You will need to migrate each of your customers, one by one. Run the
> script one for each database.
>
>
>
> On Tue, May 8, 2018 at 2:42 PM Chris Thompson <cthompson at moderas.org>
> wrote:
>
>>
>> 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.
>>
>> Sent from my iPhone
>>
>> On May 8, 2018, at 1:49 AM, nilay khatri <nilay.spartan at gmail.com> wrote:
>>
>> Why there would be a conflict with Ids?
>>
>> Upgrading from one version to another does not create records or
>> something similar to crmentity table or field tables.
>>
>> Could you put some more light on the conflicts and the upgrades?
>>
>> On Mon, May 7, 2018 at 10:31 PM, Chris Thompson <cthompson at moderas.org>
>> wrote:
>>
>>>
>>>
>>> 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.
>>>
>>> _______________________________________________
>>> http://www.vtiger.com/
>>>
>>
>> _______________________________________________
>> http://www.vtiger.com/
>>
>> _______________________________________________
>> http://www.vtiger.com/
>
>
> _______________________________________________
> http://www.vtiger.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20180508/2ff4c005/attachment.html>