MAAAAAASIVE update in the search experience for Dynamics, and I am extremely excited about it. The global search has received a major face-lift and is now looking really good. I personally never used the old relevance search, because I thought it looked bad and was confusing for the end customer.
My customers personally fond this search confusing when the database started to grow. I therefore always told the users to chose categorized search instead.
This way it was easier for the user to find the Accound/Contact/Oppty they were looking for.
New Search experience ✨🎉👍
The new search places the search bar in the middle on top, just like many other office applications. A fairly intuitive placement for the global search, and the results look awesome!!!
Did you know that it is possible to setup a fully functional Customer Service installation in less than one hour?
I am proud to present all 3 parts 1. The community solution – Download 2. The Video for installation 3. The Video for demonstrating the product
I have put a lot of hours into this configuration, because I wanted other consultants to see how nice and easy Customer Service could be delivered. I have been using countless hours every time I wanted to show a new demo, so I finally put in the extra work to make it complete. This will hopefully save you a LOT of work next time you want to demo Customer Service, or deliver a good solution to your customer.
Go get my free community solution for Customer Service.
In the preview for release wave 2020 2 Microsoft is moving the signature to UI. While doing this, they have the possibility to brush up on some old tech. Almost every piece of the old Dynamics moved over has had been given at least a small upgrade, of not a total overhaul. If you want to read about my take on signature in Dynamics, head on over here.
Limitations of the old signature: 1. Personal signature only. Could not define a signature for the organization or group. 2. No images could be added
So what has changed?
The old signature did not have a rich editor, and limited us to primitive text editing. Exactly like the old email editor.
If you tried to enter a picture, you would get an error message. For this example, I just wrote the text “no picture possible”.
The signature would be added to the email as expected if it was defined as default signature, but again with little formatting.
The new signature is available in the new UI
I added a picture of the blue color, just to demonstrate that there can be a picture in the signature.
Opening a new email will automatically add the signature as expected, but now with the picture included. 👍
Does the signature support images? YES, it finally does.
It is stored as a Base64, so no need to consider where the actual image is stored (notes, azure, blob etc etc). Migration from system A – B would work fine.
Can we use the signature multiple users? Well… Yes, but No.. It seems every signature is meant to be personal, but you can search for other signatures if you want to. But in regards to automatic signature added to email, you need to create one for each user.
As of now, I could only find the signature in the Customer Service Hub, and that confuses me a bit. Why not start off by adding it to the Sales Hub. If the signatures are personal, why not let the sales people use this first. In customer service I would have thought that a organization signature would make more sense.
While this is a great update to the last signature experience, I hope they are able to add global signatures in the future for groups of users. This would make the administrative experience a little better when you have hundreds of users.
If you read my article on signatures, I provide a different way of handling the signature experience. I try to centralize the management of the signature for faster changes. The good thing is that we have both solutions available, so pick and choose what suits your need.
Maybe in the next version we might see some structural changes to the way signatures are connected to users/groups.
This weekend I was so fortunate to talk at the Field Service BootCamp. I have tried to design the Field Service solution to be as simple as possible. I remove most of the logic from view, but keep the essence of the process. What do you think?
In the video I will explain why UNMANAGED, but I am not an ISV is the short answer. I have written about what’s included, so easy to reverse.
Remember to PUBLISH CHANGES
You will now see a new App called CS
3. Add Team + Security Role
Next you need to add a new team to Dynamics. Open the Advanced Settings in the navigation to the top right. We will be doing the next part in the old client
Open Settings – Security and Team. Add a new team and give it a name. I have chosen Customer Service. This is the team name that will own the Cases before they are assigned.
Also remember to add the security role “Team – Customer Service”. This security role is imported along with the solution
4. Add Queue + assign Team
This is the step where we connect Microsoft Exchange with Dynamics 365
Name of the queue is not important, but make something that is sensible.
When you click save, a new Mailbox will be created automatically by the system. Open the Mailbox, an navigate to the next step.
5. Approve Email and test receive mailbox
This is the point where you need to be Global Admin to continue. Start by approving the mailbox/email address.
Step 2 you test and enable the mailbox. Once this is done, head on over to “alerts”
You might need to refresh this a few times before it displays anything. The refresh button in the upper right corner is the easiest way to update the feed. You should only see information messages now. This should not generate any errors.
6. Email Settings
Next step is really important for keeping the subject logic. All of this will make sense later when you see the reply of the emails you send. Open the Email Configuration Settings and make sure it looks just like below.
7. Create Account and Contact
Now we create an Account and Contact that we use for our demo. The Account name can be whatever you want, but the contact needs to have a valid email address.
8. Send Test Email Outbound
Now it is important to check that emails actually are going out of the system. Open the contact you created with the valid email address. Create a new email activity.
NB! make sure that you substitute the from address to Customer Service (queue you created earlier) before you hit send. This will send FROM the queue to the Contact.
If things go as planned you will see an email appear in the mailbox. Be sure to check you spam if nothing is in the inbox!!!
9. Activate Record Creation and Upadte + add Team to Case Created Owner
Navigate to the Record Creation part Service Management. Before you comment on not choosing the flow way, it’s not working. I have a support case with Microsoft ongoing to fix this now.
First thing you need to update is the queue “Customer Service” for which the rules will run. I prefer the following settings below. You might disagree, but then change to your liking.
Next important step is to update the Record Creation rule. Open the “Create Case” Set Properties.
REMOVE the current customer service, and replace it with the one you created for Owner. This is important so the process assigns the cases to the Team.
When done, activate the rule.
10. Add Signature
Next step we have create a signature for the user. Signatures can be personal or company specific. The signature is located under the setup section. Navigation is at the bottom left of the CS app.
The signature below is HTML. I don’t expect you do this from scratch. I have a great guide here
11. Add User with Signature and Default Queue
Getting close to the end now, we have to add all our hard work to the Customer Service User replying to the emails. In the user form you see 2 fields “Signature” and “Default Queue”.
Update with the queue you created earlier, and the signature you just created. This is what will defines what the email leaving the system will look like.
12. Add Email Warning – New Activity on Case
This last step is optional. I created it in Flow, so beware of possible hitches with a few things regarding the current environment connector.
The purpose is to notify the Agent that a new Email has arrived for the case. If for some reason the system received email to a close case, I reopen the case and notify the agent.
This post confused me way to much. Nothing seemed to make sense, and the only thing I could focus on was the extremely odd name Dataflex.
What about the name….
A quick online search shows that the name is already in use. Not only is it in use, but it is used by a competitive product offering low-code development! How on earth is it even possible to miss out on this?
This sounds like a whole new SkyDrive – OneDrive problem, so I’m going to wait a bit before I rebrand everything to Dataflex
The voice of reason
My mind has been twisting and turning to understand the reasoning of it all of this, and luckily we have Jukka. His post is what Microsoft should have posted originally. It explains everything I was wondering about….. Except the name 😂
Microsoft released a new way to do automatic record creation a few months ago, but I never got around to ckeck it out before now.
The most obvious reason for the new release is creating something that is possible use within new UI. Therefore you can only find this in the customer service app at the moment.
At the current moment the new approach doesn’t work, for a contact that is known by the system with an account. I am working with support help them understand the error with the flow. Will update the post when they fix the error. This means that the new solution only works when the contact is not connected to a parent account.
In the “old” days we created everything via settings in the navigation. You start off creating a new record and link it to a queue you want to listen to. I prefered the following setup, and I have explained why in my other post regarding Customer Service
When you created the role for creation of case, it would use the following standard setup. Notice that the contact here would be set if account and contact were known. Contact would be contact, and account would be customer.
The new way of doing things is a lot like the old, but there are some differences.
Don’t get fooled by the name in queue to monitor. This is a regular email queue, but I gave it the name “flow”. The first thing we have to create is a new rule for the queue.
Here is where we see the first major difference. The condition for creation seems to use the same visuals as the new advanced find.
At the bottom you choose the rule and click create. This brings you over to Microsoft flow. Instead of the old WF, MS autocreares a new flow for you.
Just like the old flow, Microsoft didn’t want to you touch the details of the flow.
The old flow filled out the contact and customer fields, while the new one for some reason doesn’t (yet). I will try to work with MS on this also.
What to do next?
I honestly don’t know when they expect all of these rules to be transfered over, but I guess it will have to be done in the future when they try to sunset the old WorkFlows.
In the meanwhile I hope they fix the flow, so that it works as expected:)