Skip to end of metadata
Go to start of metadata

If you want to create a hierarchical data structure, e.g. Invoice with InvoiceDetail, you have to create relationships between entities. After specifying a relation, you have to specify keys for it.


RelatedEntityPoints to the entity to which an entity has a relation.
IsSelfJoinDeprecated. Do not use.

When the relationship has multiple keys they are normally rendered as "EntityA.Key1 = EntityB.refEntityAKey1 AND EntityA.Key2 = EntityB.refEntityAKey2".

When set to True, OR will be used between keys instead of AND.


Indicates that the base entity is a parent and the entity we are relating to is a child. By setting it to True, the following attributes are activated:

  • Cascading Delete: When data structure contains both parent and child entities, by deleting parent also child records are deleted.
  • Nested XML: Tags will get nested, which will result in faster XSL Transformations and the XML document will be easier to read.


Set IsParentChild only where child records are not linked to more than 1 parent. Otherwise you will get the "A child row has multiple parents" error after reading data to a data structure which contains this relation.

Example XML nesting if IsParentChild = False

Example XML nesting if IsParentChild = True

Child Elements

  • No labels