To live with your systems without fighting for the truth
When two systems say different things about the same data, someone has to send. Here's who's in charge of each type of data.
Work changes tool, not identity.
Customer, place, quantities and window of attention. An identifiable request, without a second inventory.
Explanatory outline. The connection and its scope are validated for each case.
Master by domain
Each type of data has a default responsible system. Define it before integrating it avoids the classic problem: two truths that differ in silence for months.
| Date | Master by default | Rule |
|---|---|---|
| Trabajo y evidencia propios | Drometra | The changes occur by domain actions, not by editing loose records. |
| Customer catalogue and stock | Tu ERP | Drometra consults or matters. Do not create a parallel inventory that will then have to be reconciled. |
| Position of an external device | The supplier of that observation | The source and its quality are preserved, with a vehicle selection policy. |
| Documento tributario emitido | Tu emisor y la autoridad | Drometra conserves different intentions, references and states. |
| Cobro informed by the processor | The processor, for the transaction | Drometra applies the payment to the balance after confirming by API and reconciling. |
First read, then write
An integration that begins by writing in both ways fails in difficult ways to diagnose. Order matters.
1. Reading connection
Initial import and then updates per cursor. The cursor is recorded after the page received persists, never before.
See API2. Express export
Writing to the other system occurs by concrete and audible actions, not as a side effect of a synchronization.
See API3. Bidirectional, then
It requires property by field, external version, causation, eco detection and conflict tail. It does not resolve with "win the last timestamp."
Talk about it.With two different watches there is no way of knowing which change is most recent. That's why the two-way synchronization is carried out as a job, with rules written for each field.
Health of connection, visible
A broken integration that appears to be well is worse than an obvious fall. The state is always shown, with the action available next to it.
- Conectado
- Permission expired
- Late synchronization
- Validation error
- Tired supplier's share
- Last success recorded
The credentials are kept separate by client and environment. An authenticated supplier does not acquire general authority over Drometra: it retains exactly the scope that was granted it.
Preguntas frecuentes
We map your systems.
With the list of what you already use we can define who is master of what before you write a code line.