Enable smarter selling with embedded AI
Focus on the right customers, build trusted relationships, and take swift action with a solution that unifies relationship data and provides contextual AI-driven insights.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
Do you need to process a lot of Common Data Service records as fast as possible? Then you should consider setting the Concurrency degrees of parallelism to as high a level as your service will support. In an earlier blog I did a test of updating 15,000 Account records. It took 168 minutes to retrieve the records and update two text fields. I didn’t make any changes to the default setting for the number of loops that would run at a time.
For the next experiment I then went in to the flow and edited the settings for the Apply to each action to move the slider all the way to 50.
The post Using Microsoft Flow Parallelism to process CDS Records appeared first on CRM Innovation - Microsoft Dynamics 365 Consulting and Marketing Solutions.
Business Applications communities