Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 have some doubts regarding the Predictive lead and Opportunity Score.
You could refer to this article first, which is the official user guide for Dynamics 365 AI for Sales.
1) According to this paragraph in the user guide:
"Following are the key benefits of this product capability:
The basics and parameters of calculating scores are mainly these four:
2) Based on this section of the user guide, we can know the factors that affect the main score.
There is no specific algorithm. It is based on your existing more than 1000 records, calculating the attributes that affect Lead or Opportunity. And sort according to the degree of influence.
3) Based on the above two points, if your custom field is associated with Lead or Opportunity, and it has affected Lead or Opportunity in existing more than 1000 records, then this custom field will participate in the calculation of the score.
Hope this helps.
Hi Lu Hao,
This is Exactly what I need.
This is very useful information for everyone.
Lu Hao, Thank you so much for your efforts on this.
Thanks and Regards,
Hi, I agree on 1) and 2). But isn't your 3) pure conjecture? I haven't read anywhere that custom fields are used. Of course I also haven't heard or read of them not being used. And this is always one of the first questions asked because not all people use the standard fields. This info would upgrade the whole lead/opportunity scoring from nice-toy-so-far to really-useful-and-ready-to-rock.
Hi Philip, I agree we don't have custom attributes from COLA and has been in our backlog with top priority to get it out ASAP. WIP and will be soon there.
here are the fields used in computing
LEAD Budgetamount, leadsourcecode, createdon, modifiedon, jobtitle, revenue, budgetstatus, estimatedclosedate, estimatedvalue, purchasetimeframe, preferredcontactmethodcode, numberofemployees, address1_country
CONTACT Annualincome, createdon, jobtitle, preferredcontactmethodcode, statecode
ACCOUNT Numberofemployees, industrycode, statecode
OPPORTUNITY Budgetamount, campaigned, completefinalproposal, createdon, estimatedclosedate, estimatedvalue, identifycompetitors, identifycustomercontacts, identifypursuitteam, isrevenuesystemcalculated
ACCOUNT address1_country, createdon, numberofemployees, statuscode, statecode
Business Applications communities