Activity rollup improvements
Important
This content is archived and is not being updated. For the latest documentation, see Microsoft Power Platform product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
| Enabled for | Public preview | General availability |
|---|---|---|
| Users, automatically | - | 
Nov 27, 2020 |
Business value
Users can now utilize activity rollups in Microsoft Dataverse that they had previously used in customer engagement apps. Performance improvements will allow queries to be more responsive. There are also improvements to stability and reliability.
Feature details
The following updates have been made to activity rollups:
Support rollup activities based on metadata availability
- Due to the Dynamics 365 for Sales separation from the Dataverse platform, activity rollups were limited due to missing required metadata attributes and entities.
Support activity rollups with Dataverse environments
- With this change, Dataverse and customer engagement apps will have the same behavior with activity rollups, after the required solution is installed.
- After installing the Sales Solution in Dataverse environments, the user should see the same data surfaced for the timeline control as is surfaced in customer engagement apps.
- Without installing the Sales Solution, Dataverse users will be able to see rollup data from common entities: account or contacts with activities, notes, as well as customer relationship data based on metadata definition.
Performance enhancement
- Activity rollup collecting will be inline with calling the queries.
- Only rollup results that meet the outer query requirements will join to outer queries. For example, when rollup queries are for incidents, only incident-type results will be joined back to the outer queries.
- Supports different query option hint on outer queries QueryOptionForActivityRollupFunction.
Supports a different table that has same row ID
- Previously, when two rows from different tables had the same RecordId, activity rollup would fail. Now, the primary key will be on ObjectId preventing this failure.
Supports multiple modes of rollup
- Customer engagement apps environments can run an activity rollup by calling a SQL function or inline rollup result. In the future, this may result in deprecation of rollup by table-valued function (TVF) SQL function as well as rollup by stored procedure.
- Dataverse rollup supports rollup by metadata that's fully consistent with customer engagement apps functionality, rollup by SQL function (supports common tables), and by RegardingobjectId.