eBiss 3

Hilfe & Dokumentation

User Tools

Site Tools


Sidebar

en:howtos:alternative_zum_entityselector

EntitySelector Alternatives for Flatfiles

Problem:

Incoming Flatfiles with identical structure should be differentiated based on the file name and converted into various target types with the help of different mappings.

Standard Solution:

Define and name the different entity typesEntitäts-Typen all based on the same object class. Define the relevant recoignition components Erkennungskomponenten and analyzers Analysator. Define the different file names as masks in the Erkennungskomponenten. Assign the appropriate components Erkennungskomponenten and entity types Entitäts-Typen to the various analyzers..

In the INBOUND Job use a specific eintity selector EntitySelector for each analyzed entity type Entitäts-Typen.

Advantage: the possibility of clear separation based on types in message boxes.
Disadvantage: additional maintenance in the repositories.

Alternative Solution

In the INBOUND Job use an EntityIf Case EntityIfCase for each type, to branch out each mapping. Define the expression in each EntityIfCase corresponding with the object class structure

/FlatFileNoHeader/FlatNoHeader_Line[starts-with( GetFileName(), 'Dateiname' )]

and connect EntityTransformer with OnTrue.

Advantage: low maintenance in the Jobs.
Disadvantage: no separation by types in the message boxes possible.

en/howtos/alternative_zum_entityselector.txt · Last modified: 2024/02/20 08:15 by 127.0.0.1