Completed Tasks
0
crmstrat_completedtaskcount
Activity Rollup Pro · Dynamics 365
Activity data already lives in your environment. It's just buried in the timeline, one record at a time. Activity Rollup Pro adds four count fields to Account and Contact and keeps them current automatically — so you can sort, filter, chart, and set views on activity volume like any other field.
Activity Rollups
Completed Tasks
0
crmstrat_completedtaskcount
Completed Meetings
0
crmstrat_completedmeetingcount
Completed Phone Calls
0
crmstrat_completedphonecallcount
Sent Emails
0
crmstrat_sentemailcount
The solution installs as a managed solution and runs entirely on Power Automate flows inside your own environment.
STEP 01
Someone marks a task, meeting, or phone call complete, or sends an email. The activity is linked to an Account or Contact through Regarding.
STEP 02
A single-record refresh flow fires on create and update, recounts that parent record's activities, and writes the new total.
STEP 03
The field updates in seconds. A scheduled sweep runs every four hours as a safety net, so counts stay right even after bulk imports.
Each one is a standard whole-number column — usable in views, charts, filters, rollup dashboards, and anywhere else a field works.
| Field | Schema name | Counts |
|---|---|---|
| Completed Tasks | crmstrat_completedtaskcount | Tasks with a completed state |
| Completed Meetings | crmstrat_completedmeetingcount | Appointments with a completed state |
| Completed Phone Calls | crmstrat_completedphonecallcount | Phone calls with a completed state |
| Sent Emails | crmstrat_sentemailcount | Emails with a status of Sent |
Added to both Account and Contact. Publisher prefix crmstrat.
This is a Dataverse solution, not a hosted service. There is no middleware, no external API, and nothing phoning home.
Every flow executes inside your own environment against your own Dataverse tables. No records are copied, cached, or transmitted anywhere else.
Installs as a managed solution and uninstalls cleanly. Tested for install and uninstall in a fresh environment with no leftovers.
No connection strings, service accounts, or environment variables to wire up. Turn the flows on and the counts start filling in.
Consulting
Activity Rollup Pro is one afternoon's version of a problem I solve on much larger systems every week. CRM-Strategy takes on implementation, automation, integration, and admin work across the Microsoft and Zoho stacks — and the connective tissue between them.
Primary stack. Day-job depth, not weekend familiarity.
Full suite, including the pieces most consultants skip.
Where CRMs meet the rest of the revenue stack.
Standing up a new CRM, or moving off one that stopped fitting. Data mapping, staged cutover, and a plan for what happens to the records that don't map cleanly.
Power Automate flows and Zoho workflows that replace manual steps — with error handling, logging, and retry behavior, so you find out when something breaks.
Getting CRM, marketing, enrichment, and outreach tools to agree on the same record. Native connectors where they exist, Zapier or custom flows where they don't.
Security roles, solution and release management, environment strategy, and the governance work that keeps a growing org from turning into a pile of one-off customizations.
Power BI and Zoho Analytics reporting built on data models that hold up — including fixing the upstream data problems that make reports wrong in the first place.
Inherited an environment nobody documented, or a build that stalled halfway? Assessment first, then a prioritized plan you can act on incrementally.
Start with a conversation, not a proposal. Tell me what's not working. If it's a fit, I'll say so — and if you'd be better served by someone else, I'll say that too.
Get in touchCRM-Strategy is the independent software practice of Tim Barczak, a senior Dynamics 365 and Power Platform administrator based in Ohio.
Activity Rollup Pro started as an internal fix for a problem every CRM admin recognizes: leadership wants to know how much activity is actually happening against an account, and the answer is locked inside a timeline that nobody can report on. The counts should just be fields. So they became fields.
Questions, bugs, or feature requests go straight to a real inbox — there's no ticket queue in between.
Email [email protected]