A Table Population defines and executes mapping and data transformation rules from a data source, like a DB table or Input file, into a target Logical Unit (LU) table. The population acts as a map that renders a graphical display of the transformation’s business logic from the source object to the target LU table. Source data can be mapped directly to LU table columns and Fabric transformation objects like Functions or Globals, and can be added to define the mapping logic into the LU table.
Each table can have one or several table populations that can be executed simultaneously or according to a predefined execution order. Each table population extracts data from a data source, transforms it when needed and then populates the data into an LU table. Table populations can be categorized as follows:
Based on a Broadway flow, whereby a Broadway Flow template is created to extract the data from the source and populate it into the target LU table. A Broadway Flow template can be enhanced with additional logic pre and post loading.
Click for more information about Table Population based on a Broadway flow.
An LU Schema displays a hierarchical representation of the data related to the Root Table. Parent-child links in LU tables are created via their Table Population objects:
Click for more information about Building an LU Hierarchy and Linking Table Populations.
A Table Population defines and executes mapping and data transformation rules from a data source, like a DB table or Input file, into a target Logical Unit (LU) table. The population acts as a map that renders a graphical display of the transformation’s business logic from the source object to the target LU table. Source data can be mapped directly to LU table columns and Fabric transformation objects like Functions or Globals, and can be added to define the mapping logic into the LU table.
Each table can have one or several table populations that can be executed simultaneously or according to a predefined execution order. Each table population extracts data from a data source, transforms it when needed and then populates the data into an LU table. Table populations can be categorized as follows:
Based on a Broadway flow, whereby a Broadway Flow template is created to extract the data from the source and populate it into the target LU table. A Broadway Flow template can be enhanced with additional logic pre and post loading.
Click for more information about Table Population based on a Broadway flow.
An LU Schema displays a hierarchical representation of the data related to the Root Table. Parent-child links in LU tables are created via their Table Population objects:
Click for more information about Building an LU Hierarchy and Linking Table Populations.