Skip to main content
The Entity Matcher is a backoffice tool used to establish the initial mapping between entities stored in Twine and the corresponding records in a connected system. It is opened from a System Integration’s overview page.

​
Selecting a domain and match field

After opening the matcher, select a domain and a match field - a field on that domain whose value is used to find candidate remote entities. The match field is only used for the initial search; once a mapping is saved, the stored mapping almost always references the remote system’s database ID rather than the match field value.

​
Reviewing matches

The matcher shows all local entities on the left, paired with a dropdown on the right that lists candidate remote entities. The bidirectional arrow between them indicates the match status:
  • Arrow with default background - an existing, saved mapping. This entity is already matched.
  • Arrow with orange background - a suggested match based on the match field. The suggestion should be reviewed before saving.
  • Transparent arrow - no match could be determined. The dropdown can be searched manually to find the correct remote entity.
Rows without a candidate match can be filled in manually by searching the dropdown. Incorrect prepopulated suggestions can be changed the same way.

​
Ignoring entities

The checkbox next to each entity’s description controls whether that row is included when saving. Unchecking it means the entity is completely ignored - no mapping is created or changed for it, even if a match is shown. This is useful for excluding entities that should not be mapped to the target system.

​
Saving

Saving the matcher persists the resulting EmployeeMappings (or the equivalent for other entity types) for the selected System Integration. Only rows with the checkbox enabled are affected. Once saved, subsequent changes to the match field do not affect existing mappings - they are anchored to the remote database ID.