Data aggregation

The first option in the Aggregations settings page is to enable or disable Last Activity.

Enabling this feature will create the fields "Last Activity" (date and time field) and "Last Activity By" (person or group field).

These fields are then used to aggregate information about the last activity on each entity on the business module. The "Last Activity" field records the date and time of the last activity on each entity and the "Last Activity By" field records who performed the last action.

To enable "Last Activity", follow these steps:

5. Enable the "Enable last activity information on entity" checker.
6. Click the "Save and update all entities" button.

Here is shown an example of the fields in use:

Next, we will look at how to add new aggregations for a business module.

7. On the Aggregations page, click “Add aggregation”.

In this example, a column will be added to a Projects master site list, which will display the latest time and date that a report document has been filed in the various project’s document libraries. The Projects master site list will aggregate this information from the individual entities themselves.

The configuration for this example is as follows:

8. The aggregation is set active. Deactivated aggregations will not run.
9. A descriptive title of “LatestReportDate” is given to the aggregation. This title is used exclusively to distinguish this aggregation from possible other aggregations.
10. We want to aggregate data from lists on entities located on the Projects business module, thus “Project site list” is selected.
11. As we wish to aggregate data from report documents on the entities, the “Documents” library is selected for Project Site List.
12. The Aggregation Type decides what type of data we want to aggregate. In this case, we wish to aggregate the latest report’s “modified” date. We can do this by sorting the list after the latest modified date in descending order, and then fetching the first item. Therefore “First” is selected in this example. Be aware that some aggregation types only support aggregation from and to certain field types. For more information, check out the Notes section.
13. For Aggregation field, we select the “Modified” field, as the data in this field will help us find the latest date that a report was filed.
14. For Target field, we can either choose an existing field or create a new one to hold the output of the data aggregation. In this example we create a new field by selecting the “Create Field” option from the menu.
15. The new field is given a descriptive name of “Latest report date”.
16. Optionally, we can add the target field to the default view of the Projects master site list. In this case, we deactivate this option.

17. Through a feature called “Active field mapping”, entities can be marked as active. This is useful for e.g. filtering out e.g. cases or projects that are archived or in other ways inactive. If Active Field Mapping is enabled and set up, the aggregation can be set up to only run on entities set to active. In this case, this setting remains deactivated.
18. Data aggregation runs whenever a change to data is made, which is what is needed for this configuration. However, sometimes it is necessary to aggregate data regardless of change to data has been made. In these cases, aggregations can be set up to run on a schedule, e.g. once every day. This is done by enabling the “Run on aggregation scheduler”-option. An example of a scheduled aggregation could be “Number of overdue tasks”, where the CAML query would be relative to current date.
19. To filter the output of the aggregation to only consider documents that are tagged as reports and order them in descending order, we use filtering. Thus, the option is enabled.
20. Filtering works by setting a CAML query for the system to execute. In this case, the CAML query tells the system to only consider documents where the value of a field called “IsReport” is equal to a value of “True”. The “IsReport” field is a custom field that can be either “True” or “False” (a so-called Yes/No field). Each report document must have a value of “True” in this field for this aggregation to work properly. The query then tells the system to order the results by the value in the “Modified” fields in descending order. Along with an Aggregation Type of “First” in pt. 10, this will return the latest date that a report document was filed for the given entity.
21. Optionally, we can test the aggregation by entering the internal ID of an existing entity in the Projects list. In this case, we have an entity with an internal ID of “11”, which already holds several documents that have been tagged as “Yes” in the “IsReport” field. The data aggregation test should therefore return the latest date and time a report document was filed.
22. The result displays the name of the entity that the test was run on, as well as the result. In this case, the latest time a report was filed for this entity was the 23th of July 2019 at 3:07:39 PM.
23. Once the configuration of the data aggregation is set up, click the “Save”-button.

• “First”: Return the value of the aggregation field of the first item returned
• “Average”: Return the average value of the values in the aggregation field
• “Count”: Return the number of elements
• “Min”: Return the minimum value of the values in the aggregation field
• “Max”: Return the maximum value of the values in the aggregation field
• “Sum”: Return the sum of the values in the aggregation field
• “Concat”: Return the concatenation of the values in the aggregation field
• “Union”: Return the union of the values in the aggregation (multi) field

WorkPoint Data Aggregation supports aggregating to target fields:

• Pre-existing fields
• Creation of new fields during aggregation

Please note that business modules using the "Cross module parenting" option cannot be used as aggregation source.

• Using Active Field mapping to aggregate from active sources only
• Running aggregation on a schedule using Scheduled Jobs
• Filtering using CAML queries

Please note that the field types in the following table are those that can be shown. In some instances no aggregation fields will be shown if the underlying list has no fields matching the criteria:

You should make sure when using any aggregation type, that the fields aggregating from and to match the valid types from the table above. This will ensure correct rendition of the fields in your lists.