Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I successfully created a flow that updates a few custom fields on the Opportunity Product entity in Dynamics from the selected Existing Product record.
I see that this flow executes every second - see attached screenshots.
Is this the expected behaviour for this trigger?
And does that mean that with each execution, even though no new Opportunity Product records have been created or modified, that my quota of Flow events will be used?
Thanks very much.
can you share the Ms flow setting?
Here's the details of the Flow - it's in 2 screenshots:
Not sure what the issue is but I would recommend using the 'Common Data Services' connectors instead as you can filter out attributes rather than the entire record. You can put them through dev - test - prod a lot easier.
You have created a loop. You modify the Opportunity Product record which triggers the flow again. That's why every second the flow runs.
You should use the CDS connector that provides attribute filtering, like Thomas suggested.
And check if there's no CRM workflow triggered on this entity.
Thanks Stefan - makes sense - real silly error on my part.
You could add a condition to check if the fields are already set to prevent the update record action from running.
Business Applications communities