Dynamics 365 Sales Automation — Power Automate Mockup

DYNAMICS 365 + POWER AUTOMATE — PROJECT 10🔵 BONUS / SPECIALIZED

Lead-to-Opportunity trigger patterns inside Dynamics 365 Sales — filtered Dataverse triggers, a command-bar instant flow, and BPF coexistence. Static reference only.

🔷 Dynamics 365 Sales — Opportunity: Aster Manufacturing — Server Upgrade

Save

Qualify

⚡ Send to Contract Review

Deactivate

Qualify

Develop

Propose

TopicServer Upgrade — Aster Mfg

Est. Revenue₹18,50,000

OwnerR. Shah

Contract Review Requested✔ true — set by command-bar flow

Automatic trigger config (Lead → Qualified)

connector: Dataverse (current)
trigger: When a row is modified
table: Lead
scope: Post-operation (After)
filtering_attributes: statuscode
filter_expression: statuscode eq 3

Test results — filter working correctly

Edited: Lead phone numberDid not fire ✔

Edited: Lead notes fieldDid not fire ✔

Changed: statuscode → QualifiedFired ✔

What this shows: the command-bar button triggers a user-initiated instant flow bound directly to this specific Opportunity's record context, while a separate, properly-filtered automatic trigger only fires on the one Lead field change that actually matters — proven by the test log showing irrelevant edits correctly ignored. The Business Process Flow stages continue guiding the user in the UI, entirely independent of either flow.