Entity To Entity was designed to support load of (multiple) Entity Details to the Main Entity regardless of its Entity Type (COMP, PORT, INDX).
Entity To Entity inbound interface allows loading and updating the data in the following database tables:
- RULESDBO.ENTITY_DETAIL
Main entity table RULESDBO.ENTITY is also updated to link details to it. RULESDBO.ENTITY_XREFERENCE is used if you load xref identifiers for Entity Details.
Processing Logic
Before you load Entity To Entity you should have a Main Entity which exists in the DB with known entity identifiers (or xref identifiers which allow to resolve entity ids). These are to be specified in the main section of the object,
EagleML/entityTransaction/entityToEntity/entityId
EagleML/entityTransaction/entityToEntity/entityName
or
EagleML/entityTransaction/entityToEntity/entityXrefs
Note: Entity To Entity cannot load new Main Entities into the database
On the other hand, you have Entity Detail which you want load and attach to the Main Entity - specify identifiers for it in the Entity Detail model of the object:
EagleML/entityTransaction/entityToEntity/entityDetail/entityDetailId
EagleML/entityTransaction/entityToEntity/entityDetail/entityDetailName
or use xref identifiers (in this case you can link only an Entity Detail, which already exists in DB):
EagleML/entityTransaction/entityToEntity/entityDetail/entityDetailXrefs/
For one Main Entity you can load several Entity Details (several RULESDBO.ENTITY_DETAIL records) as repeating models, just make sure their identifiers are set.
Resolution Options
Supported Entity Resolution options for Entity Detail Resolution:
- 1st Match
- Match All
Read more about Entity Resolution
Entity Batting Order is supported. Other Entity Resolution options are not supported for Entity Detail. Validation for Main Entity and Entity Detail is also supported. If Entity Id does not exist, load will throw an error.