[Vtigercrm-developers] Managing conflicts

[nilay khatri]

>
> I did this for a customer last year who had two separate companies and
> vtiger systems and wanted to merge them into one. It is quite a lot of work.


Really a lot of work.

We did introduce a branch concept. Where each user had access to a
particular branch/s data only. But this required to modify all code where
the queries are generated to add the condition to restrict data to assigned
branch of the currently logged in user.

Though we were able to achieve this but then the problem came when user
wanted to install few extensions.

Moreover you need to think about the operational aspects of business, like
the inventory item sequencing, invoice numbering, duplication of data
across branches etc. just to name a few.


On Tue, May 8, 2018 at 7:35 PM, Alan Lord <alanslists at gmail.com> wrote:

> On 08/05/18 14:35, Chris Thompson wrote:
>
>>
>> How would that be possible if both we and customers are adding custom
>> fields to two different databases?
>>
>
> That is not what you originally asked. It sounds to me more like you are
> trying to combine (merge) two separate systems into one. In that case you
> will need to write your own code to deal with this or pay someone to do it
> for you.
>
> It is non-trivial, especially if both systems use Inventory modules and
> lots of products ;-)
>
> I did this for a customer last year who had two separate companies and
> vtiger systems and wanted to merge them into one. It is quite a lot of work.
>
>
> Al
>
>         <mailto: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/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20180509/f8619e47/attachment.html>