Qualify Lead in D365 CE: Select which entity records should be created

August 8, 2019 priyeshwagh777 Dynamics 365, Dynamics 365 CE, dynamics 365 customization d365 Administration, d365 customer engagement, dynamics crm

Wave 2019 Updates brought some really sought-after features. Another one which I would like to bring up is the Lead Qualification experience.

I’ve written this post when I enabled the Early Opt-in of Wave 2 Oct 2019 Updates. To enable Early Opt-in, please refer this post – Early Opt-in for October 2019 Wave 2 Updates

This is set to release for the Oct 2019 Updates.

Default Behavior

So when you Qualify Lead by default – Account, Contact and Opportunity records are created.

Notice that by default, the created Account and Contact are always auto-filled.

Lead Qualify Experience in System Settings

By default, D365 will let you create all three – Account, Contact and Opportunity records when you Qualify a Lead.

When you select No, you’ll be asked which all entities should be created when you Qualify a Lead.

Lead Qualification for selected entities

No, when you click on Qualify button, you’ll be treated with this Dialog box where you can choose what records should be created.

I’ll select only Opportunity this time

And only Opportunity will be created and notice that the Contact and Account are blank this time.

Hope this is useful!

Thanks.

Related Blog on one of Wave 2 2019 Update: Customize Opportunity Close dialog box in D365 CE v9 Unified Interface – Wave 2 update

I’m also listed on the Top 100 CRM Blogs and Websites on Feedspot. It has a curated list of awesome bloggers.

How to add Rating Values to Rating Models in D365 Field Service and PSA

March 11, 2019March 13, 2019 priyeshwagh777 CRM with .NET Web Applications, Dynamics 365 CE, Dynamics 365 PSA d365 customer engagement, dynamics 365 field service, Dynamics 365 PSA, rating values

Rating Models and Rating Values are attributed to Bookable Resources in Dynamics 365 PSA and Field Service. Out-of-the-box, there are 3 Rating Values – Familiar, Good & Proficient. But obviously, you want to customize to have your own.

This is a tricky change and this post will exactly describe before you end up doing something wrong.

If you think all you need to do is add a Rating Value to the Rating Model and save, it won’t work

Because when you do this, the Value field is locked and you can’t enter anything and just saving the record with the name of the Rating Value will result in the error as shown below

Update Max Rating on Rating Model

So, the right way to do it is to update the Max Rating Value on the Rating Model record.

As soon as I save the record, see the an additional Rating Value appears. And in fact, these are the new records that were created when you updated the Max Rating Value and not that the old ones were renamed to ‘Enter rating label here…’

Note: You can simply enter the record and update all the Ratings inside to the corresponding values.

What happens to existing Ratings used for Resources?

They are all there but have been deactivated, if you query all the Rating Values as is, you’ll see the ones created due to the change we did above and the ones that already existed were suffixed with “[Inactive]” label. See below –

Well, since these are all the new records created, the old ones are ‘Deactivated‘. What remains with the existing Bookable Resource Characteristics records are the Inactive ones.

To update these, you can do a simple Advanced Find by querying one of the inactive Rating Values and updating them using Bulk Edit to set the new one.

Query the inactive ones
And simply Bulk Edit to update the Inactive ones

By the way, if you want to Bulk Clear and start fresh, you can check my blog on Bulk Clearing fields using Advanced Find here – D365 Quick Tip: Bulk Clear field values

Hope this helps you!

Enable entity for Party List selection in Appointment

January 13, 2019 priyeshwagh777 Dynamics 365, dynamics 365 administration, dynamics 365 customization activity party, appointments, d365 customer engagement, D365 Customization, Dynamics 365, party list

Out-of-the-box, you have fixed set of entities enabled for Party List fields in Appointment entity. Of which, you can select to be either in Required or Optional fields on Appointments.

But, what if you want to enable a custom entity for the same? You can do that was well.

Enable Entity for Sending Email

In your custom entity, you can turn on Sending Email option on the entity level and the entity will be enabled for Party List.
And Publish your customization.
Now, when you select the Required/Optional field in Appointment, Look for More Records
Select the Look For option to expose available entities
And look for the custom entity you created i.e. Office Representatives my this case.
And select the record you want
And the custom entity record will be added to the Party List field

The reason your see them enabled is because Email Address (emailaddress) field has been created for the entity i.e. the entity is now Email enabled.

Hope this helps!

D365 Quick Tip: Allow messages with unresolved email recipients to be sent

January 8, 2019 priyeshwagh777 Customizations, Dynamics 365, dynamics 365 administration, Dynamics 365 CE d365 customer engagement, dynamics 365 email synchronization, server side synchronization, unresolved email address

Most new users get stuck with issues saying ‘Email address of the recipient was not resolved’. Like in case you want to send out an email from D365 but you don’t have the same saved in the system as a Contact/Lead or any other record.

And it resulted in this the big red cross like the one below –

There’s a simple setting for this in Settings > Administration > System Settings, under Email tab.

You can simply flip the switch on ‘Allow messages with unresolved email recipients to be sent’ to Yes.

And, now simply enter the Email address in the Recipient (To) field and let the email go!

Hope this quick tip was helpful!

Using ‘Clone a Patch’ & ‘Clone Solution’ in Dynamics 365 Solutions

January 5, 2019June 26, 2020 priyeshwagh777 Customizations, Dynamics 365, dynamics 365 administration, Dynamics 365 CE, dynamics 365 customization clone a patch, clone solution, d365 customer engagement, D365 Customization, D365 solutions

Doing incremental deployments from Sandbox to Production is a part of every other D365 implementation.

And when do this, typically, you just create a new solution for every single time you move things over. This creates a lot of mess and leaves your Solutions in unorganized dump!

Let’s see how we can stay organized by using Clone a Patch and Clone Solution to keep things synced and clean

Clone a Patch

Clone a Patch should be used when you don’t want parent dependencies in the solution all over again unless you want to change them. So, always use this when you want to add newer things to a previously existing solution.

I have created MainSolution_1 as my main solution, the first time I started my customization. I added only 1 field, called Target Sale for demonstration purpose.
Now, let’s say I deployed it over, the next time I want to add some more functionality to the existing solution I deployed, I should not create another solution.
Rather, I’ll use Clone a Patch as shown below.
In Clone a Patch, I’ll keep the Display name same and the version number is configurable up to the last 2 sub-versions.
So this is how my Patched solution will look.
In this solution, I’ll add another field called as Min Target To Achieve and deploy it over to Production, maybe.

Clone Solution

Clone a Solution is used when you have a main solution and several patches. Clone a Solution will roll up everything into a new “parent” solution and remove every other solution of which you cloned including the source solution.

I’m select MainSolution_1, the first main solution I had created with the field Target Sale field. And then I chose to Clone Solution.
Similar to Clone a Patch, I have now the version control over the first 2 version numbers and since it is the first Clone, the final numbers are 0.0. I named it MainSolution_1_Cloned.
It takes a few moments to Clone everything.
Now, I have cloned the solution and the resultant solution has all the components from the Main Solution as well as from the Patch solution summed into 1 final solution.
Also, notice that all the other solutions including the MainSolution_1 from which I cloned this solution is deleted.