With a different transactional filter selection
Posted: Mon Dec 23, 2024 5:11 am
Example table structure:
image04-1.png
This section has given a walkthrough of the steps needed to create the basic actions we need to take to aggregate fields from multiple child tables.
Each column within the resulting grid can potentially be:
From a different transactional table.
In our example we have just cyprus mobile phone numbers used two tables, but we could have also included aggregated information from the Communications table, or any other table that is a child of the People table.
This allows for instance multiple columns to be defined as the last purchase date for particular product types.
With a different variable used to sequence the transactions.
This allows for instance multiple columns to be defined such as the last destination visited, the destination with the highest cost etc.
In designing this improvement to data grids we have tried to make this extension as natural as possible.
image04-1.png
This section has given a walkthrough of the steps needed to create the basic actions we need to take to aggregate fields from multiple child tables.
Each column within the resulting grid can potentially be:
From a different transactional table.
In our example we have just cyprus mobile phone numbers used two tables, but we could have also included aggregated information from the Communications table, or any other table that is a child of the People table.
This allows for instance multiple columns to be defined as the last purchase date for particular product types.
With a different variable used to sequence the transactions.
This allows for instance multiple columns to be defined such as the last destination visited, the destination with the highest cost etc.
In designing this improvement to data grids we have tried to make this extension as natural as possible.