Loads are defined into entities to:
Load data from source files into a target table (LOAD_FILE)
Load data from source entities into a target table (TRANSFORM_PERSIST)
See the below videos for quick tutorials on how to create an incoming load and use a load template.https://youtu.be/LVk7zjm4rTchttps://youtu.be/lW5ISk0E-CM
Loads are created in the Loads tab in the entity view with Create incoming load or Create outgoing load.
Create incoming load creates a load where the target entity is the entity where the load was created in. Once the load is created, source entities can be mapped in the load view with Create entity mapping.
Create outgoing load creates a load where the target entity is chosen when the load is created and the wizard navigates directly into a new entity mapping in the target entity.
Should I create an incoming or an outgoing load?
The end result is the same regardless of whether a load is created as an outgoing load from a source entity or as an incoming load into a target entity.
Note that the automatically generated load name will be more descriptive when creating an outgoing load because the source entity and the target entity are known.
Unique name for a load. The format of default load names is:
Source entity is populated automatically only if the load is created as an outgoing load.
Pick a schedule defined with CONFIG_LOAD_SCHEDULES or define a CUSTOM schedule (not recommended).
Used for defining a CUSTOM schedule (not recommended).
Custom schedules are not recommended because they cannot be edited in bulk. If a custom schedule defined for multiple loads has to be changed, the changes have to be done separately for all loads. Use CONFIG_LOAD_SCHEDULES instead.
Loads can be edited or deleted in the Loads tab in the entity view. Only incoming loads can be edited or deleted as they are a part of the entity that is being viewed. Outgoing loads can be edited or deleted in the entity view of the target entity.
A load can be disabled by unchecking the ENABLED box in the Edit incoming load view.
Entity mappings can be added with Create entity mapping.
Entity load logic can be saved as template with Save as a template. This saves the load steps and load options.
Entity load logic can be added from a template with Add from template.
Load steps can be added with Add load step.
Load options can be added with Add load option.
Use of CUSTOM schedules is not recommended. Use CONFIG_LOAD_SCHEDULES instead.
Use Export SQL in the entity Summary tab to check what kind of Entity Loads SQL would be generated based on the defined loads.