How Twine ties a stored Employee to its identifier in an external system
An EmployeeMapping is a small record that ties an Employee stored in Twine to that same employee’s identifier in an external system. Each mapping belongs to one Employee and one System Integration, which means a single Employee can - and usually does - have multiple mappings, one per system that knows about them.The same model exists for the other entity types Twine stores. The Employee variant is by far the most common in practice.EmployeeMappings are how Twine knows which remote record corresponds to which local entity when reading or writing data. Establishing the right mapping when an Employee is first encountered is typically done in the backoffice via the Entity Matcher.