Follow

Data aggregation

Contents

1. Introduction

Data aggregation is used for summarizing data from an entity onto that entity’s module master page. This is useful for gaining overviews of certain details from entities without having to go to their entity sites. This data can instead be displayed in a column in the business module list.

Here is a visual representation of what data aggregation does:

 

A case where this feature can be useful is if a project manager wants to be able to see when the latest report on each project was filed from the Projects master site list. Each report could be tagged as such, and this information can be used to aggregate data for when the latest document tagged as report was modified on each project and display this data in a column for each entity in the Projects master site list. This is useful, as it grants an overview of report dates for each project without having to go into each project site and check for report documents and their latest modification date, thereby freeing up time for other tasks. Another example could be aggregation of how many open tasks there are on each entity.

2. Requirements

There are currently no requirements for the utilization of this feature.

3. Configuration

Data aggregation is set up through the WorkPoint Administration, which can be accessed by following these steps:

  1. Click the “Home”-button on the solution.
  2. Click the cog-icon to access the WorkPoint Administration.
  1. Click the header of the business module for which data aggregation should be set up.
  2. Click the “Aggregation”-menu item.
  1. 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:

  1. The aggregation is set active. Deactivated aggregations will not run.
  2. A descriptive title of “LatestReportDate” is given to the aggregation. This title is used exclusively to distinguish this aggregation from possible other aggregations.
  3. We want to aggregate data from lists on entities located on the Projects business module, thus “Project site list” is selected.
  4. As we wish to aggregate data from report documents on the entities, the “Documents” library is selected for Project Site List.
  5. 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.
  6. 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.
  7. 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.
  8. The new field is given a descriptive name of “Latest report date”.
  9. Optionally, we can add the target field to the default view of the Projects master site list. In this case, we deactivate this option.
  1. 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.
  2. Data aggregation runs whenever a change to data is made, which is what is needed for this configuration. However, situationally 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. Once the configuration of the data aggregation is set up, click the “Save”-button.

4. End User Guide

In order to run a data aggregation, access the data aggregation settings page for the business module in question. From here, follow these steps:

  1. Click the “Run”-button.
  1. Click the “Run aggregation”-button.

The aggregation will now run:

  1. The progress of the aggregation can be viewed in the list by clicking “Refresh”.
  2. The progress is displayed in the “Details”-column of the list item.
  3. During the aggregation a stop-button is displayed in the "Actions" column, which can be prematurely stopped by clicking the “Stop”-button. In this example, the aggregation is complete, thus the button is not showing.

Upon completion, the aggregated data has been fetched and can be displayed in the specified column, granted that the column is set to be displayed in an available view. In this case, the “Last report date”-column from the configuration example was added to a view on the Projects master list called “Compact”, which is shown below:

5. Notes

Data aggregation is performed automatically whenever data changes in a WorkPoint solution. Therefore, scheduling data aggregation jobs is not always necessary. It may, however, be needed if data should be aggregated on a specific schedule regardless of whether data changes.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments