Breaking news from around the world
Get the Bing + MSN extension
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
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
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 | Talent TechTalks | Upcoming TechTalks
I'm trying to create a Business Process Flow that will take the user from the Lead into the Contact. The first stage of the BPF asks the user to check if the lead already exists as a contact, why then does the later stage (which relates to the contact record) still require the user to select or create a contact? And why does the already identified 'existing contact' not show up in the list? All I get is 'no records found'??
When you create a cross entity business process flow, you have to select the relationship between the entities. In your case when going from lead to contact, Business Process flow is looking for a "lookup" field of Lead entity on Contact entity. Be default, the lead lookup is called Originating Lead.
Now, assuming you have select the Contact entity with the relationship as Originating Lead, even thoug you have selected the contact in the Existing Contact field, this is not the relationship BPF are looking for. It is looking for a contact which has this lead record populated on contacts on the Originating Lead lookup field. Because its a new lead, there may not be a contact which has this lead populated for Originating Lead field thus displaying you no records.
What you can do is create a workflow on create/ update of lead and then update the "Originating Lead" field of the selected existing contact. I haven't tried this but looks like this will help.
Hope this helps.
Unfortunately when I try to setup a workflow to update the originating lead on the selected contact, I'm not able to as the field is locked...
Business Applications communities