D365 Sales Team Fixes Power Automate Flow by Replacing Abstract activitypointer Trigger

A Microsoft Dynamics 365 implementation team discovered that their Power Automate flow for tracking customer activity was not running because it targeted activitypointer, an abstract entity that cannot serve as a Dataverse trigger. Since activitypointer is an aggregated view rather than a real table, separate flows must be created for each concrete activity type — task, phone call, email, and appointment. The team resolved this by building a working flow for tasks first, then duplicating it three times and updating only the trigger table in each copy. An additional consideration was noted: phone calls, emails, and appointments are often linked directly to an Account or Contact rather than an Opportunity, which can cause an Entity Not Found error in the row-lookup step if table names are not configured correctly. After testing, the updated flows successfully wrote back the Last Activity Date to the related Account records.