An LU schema structure displays a hierarchical presentation of the data related to the Root Table. Parent-child links in LU tables are created via their Table Population objects :
Each LU table can have one or several Table Population objects. Each such object - except the Table Population object of the Root LU table - should be linked to a parent table via its input arguments.
Each Table Population object can be linked to a different parent LU table.
For instance: an ADDRESS LU table is populated with two populations:
A link from a Table Population object to a parent LU table can be based on several columns, all of which should be linked to the same parent LU table.
Note: An LU table can be added to an LU schema without a Table Population object. Such table is not populated by the sync of the instance, but rather by a separate transaction.
Input arguments of a population flow are defined by the PopulationArgs Actor's input argument that must be set to an External population type.
Each population flow should have at least one Input parameter. A Root table's population can have only one input argument, which is populated by the Instance ID.
Input arguments are a property of the Source Object of a Table Population object.
There are two types of Source Objects for a Table Population object:
DB Query
Root Function
Click for more information about Table Population Types.
When creating a DB query, by default all Input fields are set to True.
To edit an Input argument, do the following:
Click the source object of the Population window (the DB query) and verify that the fields that should be linked to the parent table are set to True. Other fields which do not need to be linked to a parent table, can be set to False.
A link can be added in both directions:
Note: Link all the Input fields of the selected Table Population object to one parent table. A Table Population object cannot be linked to several parent tables.
An LU schema structure displays a hierarchical presentation of the data related to the Root Table. Parent-child links in LU tables are created via their Table Population objects :
Each LU table can have one or several Table Population objects. Each such object - except the Table Population object of the Root LU table - should be linked to a parent table via its input arguments.
Each Table Population object can be linked to a different parent LU table.
For instance: an ADDRESS LU table is populated with two populations:
A link from a Table Population object to a parent LU table can be based on several columns, all of which should be linked to the same parent LU table.
Note: An LU table can be added to an LU schema without a Table Population object. Such table is not populated by the sync of the instance, but rather by a separate transaction.
Input arguments of a population flow are defined by the PopulationArgs Actor's input argument that must be set to an External population type.
Each population flow should have at least one Input parameter. A Root table's population can have only one input argument, which is populated by the Instance ID.
Input arguments are a property of the Source Object of a Table Population object.
There are two types of Source Objects for a Table Population object:
DB Query
Root Function
Click for more information about Table Population Types.
When creating a DB query, by default all Input fields are set to True.
To edit an Input argument, do the following:
Click the source object of the Population window (the DB query) and verify that the fields that should be linked to the parent table are set to True. Other fields which do not need to be linked to a parent table, can be set to False.
A link can be added in both directions:
Note: Link all the Input fields of the selected Table Population object to one parent table. A Table Population object cannot be linked to several parent tables.