D365 Customer Insights for Our Own Sales Team (Customer Zero) (3) Fixing the D365 Sales Customization

Short summary

This article details fixing a D365 Sales customization where a Power Automate flow failed because activitypointer cannot be used as a Dataverse trigger—it's an abstract aggregation view, not a real table. The solution requires creating separate triggers for each concrete activity table (task, phonecall, email, appointment) and duplicating the flow accordingly. The author also flags that phone calls, emails, and appointments may link to Accounts or Contacts rather than Opportunities, requiring careful table configuration.

• •activitypointer cannot trigger Power Automate flows—use concrete tables instead
• •Duplicate flows per activity type: task, phonecall, email, appointment
• •Watch for Regarding field pointing to Account/Contact vs Opportunity to avoid lookup errors

Generated with AI, which can make mistakes.