Data Entity Lines

The rows under a data entity describe fields and the relationships to other data entities. A line is defined by the following fields:

Name	Description
Type	Defines the type of line (relation type). A line can represent a Field, i.e. contain the content of a field, a Relation to another table - a child element - or the value Lookup, which is used to determine a value of a sub-table.
Reference	The title of the reference or field. As for the table in the header, entries are possible as name, title or ID.
Child Data Entity Code	This code is used to reference an existing data entity. For example, if you configure the data entity for an article, you may need a relationship to the unit or article unit if data entities have also been created for these.
Field Usage	There are a few basic pieces of information that are used to prepare data. An important aspect is the Language, one of the two available options. The second option is E-Mail.
Lookup Field	This field is enabled if the Type is configured to Lookup. A field can now be selected here, which is embedded directly under the specified Name.
Name	This name serves as the key for this field when the structured data is generated, unless it is explicitly replaced by the processing.
Missing Relation	This field, which cannot be changed, provides information about a missing relationship definition for this line. Use Change relation filter to adjust it.

Type

Relation

The type Relation creates a child structure based on the relation resulting from the field content. This requires that an entity exists for this table.

Lookup

The Type Lookup allows the field of a relational table to be embedded directly into the structure. Instead of integrating an entire structure as a child element, only the selected field is returned.

Note

For example, the Description field can be included directly from a relation to the Item table in order to prevent the integration of a more complex structure in favor of the item description.

Field Usage

Setting up a field usage allows special handling for these fields, which is already integrated in word processing.

Language

If Language is defined as the Field Usage in a data entity line, the language of the data record is determined from the underlying field (code, text, integer). Data formatting is then continued with this information so that, for example, option values are returned in the determined language.

E-Mail

The field usage E-Mail indicates that the content of this field is an e-mail address. These are collected in addition to the data processing.

Actions

Manage - Edit Relation Filters

Use this to open the Data Entity Relations page, where you can configure the connection between tables and additional filter expressions. For more information, see Relation Filter.

Manage - Add Multiple References

Select several fields to be included from the field list that opens.

Suggest

The following suggestion functions are very powerful and save you a lot of configuration work. Use them to set up Data Entities to save time.

Fields and Relations

Automatically creates Entity Lines for all fields. For both regular and relation fields.

Field usages (Language, E-Mail) are also determined automatically if they result from the names and the field type.

Important

Child Data Entities can only be determined if they have already been created. It is therefore advisable to create data entities in a hierarchy from bottom to top.

Common Fields and Relations

As for Fields and Relations, this function automatically creates Entity Lines. However, it is reduced to the fields that are used in the current dataset. Unused fields are skipped.

Fields

Works like the Fields and Relations function, except that only Field lines and no Relations are created here.

Common Fields

Works in the same way as the Fields function, but only creates rows for fields that are used in the current dataset.

Relations

Works like Fields and Relations, but only creates lines for Relations, not for Fields.

Data - Show Demo Data Object

This action provides you with an identical function like in the header.

Relations Filter

This is a setup at the line level. See also Edit Relation Filters.

No Relation Filter is necessary for general fields that are given relationships as part of the development of a table object (applies to most fields that allow a lookup), as this results from the defined relationship and is used automatically.

Often necessary to describe the relationship between header and lines, as this does not arise from the header, but only from the viewpoint of the lines. For example, the definition of a relationship between the Sales Header and its lines:

Source Field (Sales Header)	Target Field (Sales Line)
Document Type	Document Type
No.	Document No.

To reduce the amount of data, you can optionally define a target table filter on the relationship page. This could, for example, restrict Sales Lines to the type Item.

Caution

In addition to the Target Table Filter specified here, the Table Filter of the child entity is also applied. This is done additively on the basis of the entity but not at field level.

A Target Table Filter in the Sales Line on the field Type is overwritten by the Table Filter of the child entity with filters on Type if necessary, but filters on different fields are additive.