In Dynamics 365, when a lead is qualified, the opportunity is created via the internal system process rather than as a manual "create" operation. This means that your Power Automate flow, which is triggered on the creation of an opportunity, may not fire because system processes (like lead qualification) bypass certain triggers.
Here are a few ways to address this:
1. Use the “When a row is added, modified, or deleted” Trigger
The "When a row is added, modified, or deleted" trigger in Dataverse may capture changes even if the system creates the record. Try using this broader trigger and specifying the Opportunity entity.
Make sure to add a filter condition to the trigger to ensure it only fires when a new opportunity is created.
2. Use a Trigger on Lead Qualification Instead
Alternatively, you could add the trigger to fire when the Lead is qualified. In this case, you would use the "When a row is updated" trigger on the Lead entity, filtering on the field that indicates the lead is qualified (e.g., status or lead state).
Once the lead is qualified, you can query for the newly created opportunity and copy the custom fields from the lead to the opportunity.
Thank you,
Amit Katariya
