Our CRM tip last week was talking about using queues in CRM but what is a queue? A queue is one of the many great entities in Microsoft Dynamics CRM. It is used to act like a container to hold anything that needs to be worked on. You have the ability to prioritize the items listed in the queue and filter to specific users and teams. Here are some examples of what a queue can offer CRM users:
Microsoft Dynamics 365/CRM offers users the ability to create their own personal email signatures when sending an email out of CRM.
Each user can have multiple signatures and can select them from the email record when creating an email. You can also set one as your default signature.
This simple guide will walk you through setting up a custom email signature in your Microsoft Dynamics 365/CRM system. Be sure to share with your colleagues! Creating a company-wide signature is always good for branding.
One of the many fantastic features available to users (and most often used) in Microsoft Dynamics CRM is the ability to create saved, personal views with an advanced find to see a filtered list of records.
Ownership for each account and contact in CRM is always assigned to a specific CRM user. There are many reasons and advantages for doing this. Among them are assigning sales and marketing tasks and responsibilities to an individual salesperson, securing sensitive data, and sales pipeline reporting.
One of the many fantastic features available to users (and one of the most often used) in Microsoft Dynamics 365/CRM is the ability to create saved, personal views. These views are created with an advanced find to see a filtered list of records.
While your System Administrator does their best to create a set of system views, (available to all users), they simply cannot predict all the views that each viewer will want see.
Personal Views are a great way for users to get a quick, simple custom view of a specific list of records and retain that view for future reference.
Do you ever wish you could have a one-off workflow that you can control when it runs instead of having to setup a workflow with a trigger? Using on-demand workflows in Microsoft Dynamics 365 will allow you to run processes and/or update data without relying on a workflow trigger.
What Triggers your Workflows in Microsoft Dynamics 365/CRM, or what causes them to actually run?
The most important one is the one that gets confused the most, called Record is Created.
In the world of CRM, when a Record is Created, it literally refers to every single action that is created before you hit Save the first time.
Admins will typically set up a Workflow and think no one will adjust the field until the Record is created, or only want to Trigger it when the Field is changed, but what if the Field is changed before the Record is saved for the first time?