Master -> Slave EspoCrm

[item]

Hi Yuri,

You know, we can configure mysql as Master and Slave. .but it's possible with AdvancedPack have same data with 2 instance of EspoCrm ? (all entity, maybe not actionHistory and login ?)
I don't know if other "EspoCrm" user can find this usefull but imagine my situation :

Two department. (2 type of User).
one instance of EspoCrm is used in production by one department at this moment.
second instance must be try and validate by second department in a few week.

These 2 department have different task.. first prepare create account/contact/and so and second create sample meeting, call and so

Is there any magic "webhook" (maybe) for same think as Master->Slave, so it's easy for "me" to see where i have issue for our second department without altering master EspoCrm

Best Regards

[yuri]

Hello Item,

It possible to use Workflow Send HTTP Request action for a such one-way sync task. If only create an entity – that will be quite easy to implement. Syncing updates – harder. You will need to store a returned ID in the first instance, to be able to sync updates after.

[item]

Thanks Yuri,
yes i will do that

[dimyy]

It is not very clear from the description what the problem is in using one instance.

Technically, it is possible to do database replication with the exception of several tables (what relates to the cron, possibly to users and their settings) as well as folders with attachments. Plus agree on the order of making changes so that there are no data conflicts.

Since all entities in the system have a unique ID, there should be no problems.

[item]

Hi dimyy,
the problem is "since 25 year" one department use "Filemaker" and other department hate computer !
all "data" is make with paper ! paper agenda, paper task, paper ... and paper -> department one print paper -> departement two complete paper -> departement one complete "database".

All process change with EspoCRM .. this is "explosive for Users" .. all (90%) process from department one go to department two in EspoCrm.
And yes, why not in one instance.. because there are many "new process for invoice and others" and must be "validate" by law and so.
In my demo instance, all seemts OK.... but if User find one "issue", i will be killed by all Users of department 2 !

[dimyy]

Changing mentality is the hardest thing in IT
Proving that a computer is more efficient than an abacus is usually difficult.

[item]

Hi,
love this : "Proving that a computer is more efficient than an abacus is usually difficult."
Yuri have say something so but forget where post and forget complete word but it's +- so : it's not math, so it's not ...