A Table Population can be created by:
Dragging the table from the LU Schema DB Objects tab into the LU schema working area to create the LU table including its Table Population object.
Creating an LU table using the New Table from SQL Based DB Query or New Table from SQL Based Root Function options in the LU Schema window to create the LU table including its Table Population object.
Using the Auto Discovery Wizard to automatically create the LU table and a DB query population for each LU table.
From the Project Tree -> Logical Units -> [Name of Logical Unit] -> Tables -> right click on the [Table Name], and select New Table Population.
From the Project Tree -> Implementation -> Logical Units/Data Products -> [Name of Logical Unit] -> Tables -> right click on the [Table Name], and select New Population.
LU tables can be populated by either a DB query or a Root function source object. To decide which source object to use, refer to the comparison analysis of Table Population Source Object Types.
A source object can return one or many records whereby each output record is mapped and populated into a target LU table. Note that a Table Population can extract data from other LU tables in the same Logical Unit. It is recommended to always check the execution order of a source table’s population objects to verify that the source LU tables are populated before the target LU table. For example, the SUBSCRIBER LU table must be populated before the OFFER LU table to enable populating the OFFER LU table based on data from the SUBSCRIBER LU table.
When an LU table has two populations, a second Table Population can extract data from the same LU table. For example, the ADDRESS LU table has two Table Populations:
Click for more information about Creating Table Population Objects.
The starting points for creating a population based on a Broadway flow are:
The population is created as a template with predefined Stages and designated Actors. When creating a flow from the Auto Discovery Wizard or from the LU Schema, the input fields, interface, and SQL statement are added automatically based on the selected table's fields. Complete the missing information and if needed, update the flow and then connect the table population to the LU hierarchy via the LU Schema window.
Note that for the population to be effective on the server side, LU deployment is required. When running in debug mode, the deployment to debug is performed automatically.
Click for more information about deployment from the Fabric Studio.
When the LU Schema is created, each LU table is created with a population flow.
Do the following steps if an additional population flow is needed for an LU table:
Note that for the population to be effective on the server side, LU deployment is required. When running in debug mode, the deployment to debug is performed automatically.
A Table Population can be created by:
Dragging the table from the LU Schema DB Objects tab into the LU schema working area to create the LU table including its Table Population object.
Creating an LU table using the New Table from SQL Based DB Query or New Table from SQL Based Root Function options in the LU Schema window to create the LU table including its Table Population object.
Using the Auto Discovery Wizard to automatically create the LU table and a DB query population for each LU table.
From the Project Tree -> Logical Units -> [Name of Logical Unit] -> Tables -> right click on the [Table Name], and select New Table Population.
From the Project Tree -> Implementation -> Logical Units/Data Products -> [Name of Logical Unit] -> Tables -> right click on the [Table Name], and select New Population.
LU tables can be populated by either a DB query or a Root function source object. To decide which source object to use, refer to the comparison analysis of Table Population Source Object Types.
A source object can return one or many records whereby each output record is mapped and populated into a target LU table. Note that a Table Population can extract data from other LU tables in the same Logical Unit. It is recommended to always check the execution order of a source table’s population objects to verify that the source LU tables are populated before the target LU table. For example, the SUBSCRIBER LU table must be populated before the OFFER LU table to enable populating the OFFER LU table based on data from the SUBSCRIBER LU table.
When an LU table has two populations, a second Table Population can extract data from the same LU table. For example, the ADDRESS LU table has two Table Populations:
Click for more information about Creating Table Population Objects.
The starting points for creating a population based on a Broadway flow are:
The population is created as a template with predefined Stages and designated Actors. When creating a flow from the Auto Discovery Wizard or from the LU Schema, the input fields, interface, and SQL statement are added automatically based on the selected table's fields. Complete the missing information and if needed, update the flow and then connect the table population to the LU hierarchy via the LU Schema window.
Note that for the population to be effective on the server side, LU deployment is required. When running in debug mode, the deployment to debug is performed automatically.
Click for more information about deployment from the Fabric Studio.
When the LU Schema is created, each LU table is created with a population flow.
Do the following steps if an additional population flow is needed for an LU table:
Note that for the population to be effective on the server side, LU deployment is required. When running in debug mode, the deployment to debug is performed automatically.