The external system
Not us
A file, a table, a call. That ERP’s name is not in the code. Nesso is not that system.
The field
The owner is chosen field by field. The night run does not clear a field whose owner is Espo.
Espo on one side
Clearing a field is a write. It has an owner.
The default is the source. If tonight's file brings an empty city, the city on Espo becomes empty. It is the behavior expected of a load: the file is the truth of those fields.
Clearing is not a side effect on the whole sheet. It applies to the fields the source owns. An unmapped field is not touched.
A field can be said to belong to Espo. A note written by a person, a value corrected by hand, stay. If the file brings a different value, that value goes into a queue to look at. The field on Espo does not change.
On create the field is written anyway: there is not yet a note to protect. From the next run the owner counts.
The badge on the record says who wrote last. It is there for whoever needs to see whether the row is still the file's or whether someone in Espo corrected it.
It is not a legal history. It is the mark, on the record, of the last run that touched it.
The passage
Nesso stands in the middle. It reads the channel, applies the mapping, and writes through Espo’s API. It does not open the CRM tables.
Not us
A file, a table, a call. That ERP’s name is not in the code. Nesso is not that system.
This is us
Channel, sheet, fields. If the write switch is off, it does not write. If the field belongs to Espo, it does not clear it.
The sheet
The record, if it is born, is born there. CRM mail stays in Espo. The Advanced Pack is not rewritten.
Nesso always has Espo on one side. It is not a bridge between any two systems.
The trial is the public repository. It starts an empty Espo. It does not import a production dump.
How the trial works