• Skip to primary navigation
  • Skip to main content
  • Skip to footer

218.486.5095

Implementation Specialists logo

Implementation Specialists

Microsoft Partner providing ERP solutions, support and consulting.

MENUMENU
  • About Us
    • Careers
  • Industries
    • Contractors
      • Construction Contractors
      • Electrical Contractors
      • Mechanical Contractors
    • Distribution
    • Manufacturing
  • Solutions
    • Dynamics 365 Business Central
    • Dynamics GP
    • Dynamics 365 Sales
    • Dynamics 365 for Financials
    • Power BI
    • Microsoft 365 Copilot
    • wsTOOLS
    • AI Agents
    • BC Apps
  • Services
        • Business Process Review
        • Software Consulting
        • Project Management
        • Technical Consulting
        • Programming
        • System Optimization and Performance Review
        • Report Writing
        • Training for Business Central and GP
        • NAV to Business Central Migration
        • HR Consulting
  • Resources
    • Blog
    • Video Library
    • Webinar Archive
    • Our Partners
  • Events
    • BizCon
    • Webinars
    • Geeks on the Green
  • Contact
    • Support
Home / Microsoft Office 365

Microsoft Office 365

XRM: Managing Time Off Requests Through Dynamics 365 Customer Engagement

October 8, 2020

Time off requests can cause a lot of headaches and it’s an important subject for your employees. Having a simple and efficient process for requesting and responding to time off is a huge benefit.

An out of the box time off request and calendar exists within the field service app and you can bring this over to the other sections if you have access to the field service app. In our example today we did not have access to the field service app as we only utilized the sales and service sections, so we created a new entity and process directly within Customer Engagement.

Here are the steps we took:

Created a new entity called “Time Off Request”.

For the entity we made it available under sales and service as those are the two areas the employees used. This entity was set up to allow for notes, but does not require activities or document management. Queues are not used in our example, but as a process you could utilize time off queues versus an email notification directly to the manager.

Created custom fields and designed the form.

Here are the fields we created/updated:

  • Employee
    • This was set up as a look-up field and was pointed to users.
  • Department
    • Created as an option set with different team names. This allows us to track how many requests we have by team and manage staffing levels.
  • Start Date
    • Included both date and time so requests could be full days or just a few hours.
  • End Date
    • Set up the same way as the start date field.
  • Time Off Reason
    • Another option set where employees could choose PTO, Unpaid or Other time off reasons. If you have other reasons such as bereavement or jury duty those could be added to the list.
  • Status Reason
    • This field already exists but we did make a couple changes. Under the active section we changed active to requested. Under the inactive section we added two and renamed one so we have approved, denied and cancelled, with the default being approved.

Once we had all our fields created we designed the form. Here is what our form looks like:

Set up workflows.

We determined a couple different workflows were necessary to keep this process flowing smoothly.

  • Upon new time off request.
    • When a new time off request is saved the workflow gives the record a proper name based on the employee name and start date of request, then an email is sent to the manager alerting them to the time off request. The manager can access the record directly from the email. Here is our email set-up:

  • When the request is approved or declined.
    • A manager approves or declines our record by deactivating the record and then choosing the reason. Once the record is deactivated it triggers a workflow to send an email to the employee notifying them.

Updated/Created Views

We updated the default view to use our new custom fields to allow for easy filtering.

Here is what the active time off request view looked like:

A custom view was also created to show all approved and requested dates.

This view enables a manager to see all requests for their department so they don’t approve too many people off on the same day.

This process was fairly simple to set up but was very beneficial. This resulted in time savings and prevented negative morale issues due to problems or delays with time off requests.

-Jerica Coleman, CRM and Power BI Consultant

ryan mccollum
Ryan McCollum

Filed Under: CRM Tagged With: CRM, IS Services, Microsoft, Microsoft Office 365, Office 365, Online Services, XRM

CRM: Benefits to help transitioning workers to at home environments

March 31, 2020

During these uncertain times it is important to keep as much normalcy as possible. With so many companies moving to employees working from home having tools that will help employees work together virtually is essential. Microsoft Dynamics 365 Customer Engagement is a CRM system that provides many benefits for a virtual work environment.

Data Stored in One Location

With employees working from home it is even more important that data is housed in one location and is accessible to all that would need it. Keeping data within the CRM system eliminates time wasted tracking down each piece of information and prevents incorrect or incomplete information from reaching the customer.

Custom fields can be created within CRM, so if you have data that is currently not stored within Dynamics 365 now is the time to look at getting it moved into the system.

Integration with SharePoint or OneNote

Dynamics 365 integrates with SharePoint allowing documents to be saved that are attached to particular records. A salesperson could put together job specifications and save them into a SharePoint folder directly from Dynamics and the project manager could either access the information from Dynamics or directly from SharePoint to begin planning the project.

Dynamics 365 also has integration capabilities with OneNote allowing multiple users the ability to work on the same file.

Customization Capabilities

Dynamics 365 gives you the ability to customize your CRM system to meet the changing needs of your organization. Here are some examples to consider:

  • Set new business process flows to reflect business procedure changes due to COVID-19.
  • Create new entities for other business processes previously handled in person or via email.
  • Publish standard company response information within the sales literature for employees or as a word template to send out to customers.
  • Use “What’s New” posts to provide daily updates to all employees. These can be placed on a dashboard so the posts are seen on the employee’s home page.

We are all navigating this as best we can, and many people are unsure of how things are going to be once this is over. Every little decision that can help make these times easier will be extremely beneficial to everyone involved. Any questions? We’re here to help.

-Jerica Coleman, CRM and Power BI Consultant

ryan mccollum
Ryan McCollum

Filed Under: CRM Tagged With: CRM, Dynamics 365, IS Services, Microsoft, Microsoft Dynamics 365, Microsoft Office 365, Online Services

Choosing the right Office 365 partner

February 25, 2020

A wrong choice in selecting your Office 365 partner brings many unpleasant consequences. The worst being lost productivity – meaning lost revenue. There’s a true cost related to choosing the wrong Office 365 partner. Here’s what’s at stake:

Migration confusion

Microsoft makes it sound easy to move to their cloud-based Office 365 solutions – and it is. But only if you have a professional partner who knows the right way to do it. Microsoft has amazing online technical resources, but wouldn’t you rather be focusing on your business than troubleshooting with Microsoft?

Make sure your Office 365 Partner is certified. You can measure the cost of the wrong choice in actual dollars. Unexpected issues or a failed migration means that you and your employees can’t do business.

Avoiding wrong choices

Microsoft loves acronyms. The most important one for this exercise is POR. That stands for Partner of Record. It refers to the organization helping you with your Office 365 setup.

Your POR won’t add to the monthly subscription cost. But it will impact another acronym, TCO. Choosing the right partner should reduce your Total Cost of Ownership. It’s your partner’s job to provide you with the expertise to take advantage of what Office 365 has to offer. They should be able to help you and be available to talk to you if you have any issues.

If you’ve never had a conversation with your partner on record, maybe it’s time to look for a new partner.

There’s money at stake

The move to Office 365 is seamless when you choose the right partner. The benefits are immediate. You run the risk of costly mistakes if the partner you select isn’t a certified Microsoft provider. To be fair, those risks aren’t guaranteed. But, why take a chance? Choose one who’s going to add value to your Office 365 investment and Implementation Specialists would love to assist you with this.

Brett Colliton, Sales Account Executive

If you’d like to explore this as an option for your business, contact us.

ryan mccollum
Ryan McCollum

Filed Under: Dynamics 365, Uncategorized Tagged With: Dynamics 365, IS Services, Microsoft, Microsoft Dynamics 365, Microsoft Office 365, Office 365, Online Services

CRM: Workflow Examples

February 5, 2020

In the last couple CRM blog posts we covered the basic set-up for workflows and gave definitions of steps that can be used. Today we are going to look at two examples of how these different steps can be combined within a workflow.

In these examples we will be creating workflows within Microsoft Dynamics 365 CRM versus using Power Automate, which was previously Microsoft Flow.

Workflow: Send an email to different managers based on account type.

In this workflow when a new account is created it will check for the account type and send an email to the appropriate manager for that account. Here are the steps utilized:

Check Condition: The first line is the check condition. Here we are checking if the account type equals customer.

Conditional Branch: There are two conditional branches. One to check if the account type is wsTools resller and one to check if the account type is ISV partner.

Send Email: There are three send email lines. In the first one we are sending the email to the sales manager for a customer account. The second one sends to the resales department for a wsTools reseller. The final one sends to our partner account executive for an ISV partner. The body is kept the same for each email, but the recipient is different. There are a lot of options available when creating your email template. We will explore this more at a later date.

Stop Workflow: The workflow is set to stop after each email send.

Workflow: Create tasks and flag as overdue 7 days after opportunity is created if it remains open.

With this workflow when an opportunity is created two new tasks are created for the owner of the opportunity. The workflow will then wait until 7 days after the opportunity was created. When it resumes the workflow checks to see if the opportunity is still open and if it is the opportunity will be updated and flagged as overdue. Here are the steps utilized:

Create Record: Two task records are created that will be related to the opportunity. One task is to send information to the design team and the second is that the proposal is due within 3 days of the opportunity creation.

Wait Condition: After the tasks are created the workflow will be placed on a wait until 7 days after the record was created. This looks similar to a check condition, but instead of selecting the entity type to check a particular field select “Process” from the bottom of the list.

Check Condition: The first condition checks if the opportunity status is open.

Conditional Branch: The conditional branch checks if the opportunity status is lost or won.

Update Record: If the opportunity is still open the record will be updated to show past due.

Stop Workflow: There is a stop workflow after the record is updated or after the conditional branch as there will be no action taken if the record is lost or won.

Working with dynamic values.

Within record creation, update or wait condition you can select from dynamic values within a record. In our screenshots everything highlighted in yellow is a dynamic field value. Dynamic values are available on the form assistant located to the right-hand side of the window when setting properties. Depending on the field type there are a couple different ways you can use dynamic values. See the screenshot below for tips on how to use these.

I hope this has given you a couple ideas of how you can combine different workflow steps to help within your organization.

-Jerica Coleman, CRM and Power BI Consultant

ryan mccollum
Ryan McCollum

Filed Under: CRM Tagged With: CRM, IS Services, Microsoft, Microsoft Office 365, Online Services

CRM: Using Conditions in Business Process Flows

December 10, 2019

Business process flows are created to help lead end users through the series of steps required for a record. Sometimes different records may need to take different steps. This is where conditions within a business process come into play.

Let’s look at how to set conditions within a business process and what that looks like for the end user.

Conditions are available underneath the components tab on the right-hand side of the screen within your business process window. To utilize drag the condition box onto the canvas.

Once placed onto the canvas give the condition a name and set the criteria.

In this example we are setting our business process paths based on potential revenue within an opportunity. If a customer is going to spend over $5,000 I want the customer to have an additional contact point within the sales process.

Once the criteria has been entered select “Apply” and the condition will update on the canvas.

After the criteria has been set design a path for records meeting the criteria by pulling stages onto the canvas connected to the green check mark. The path for records not meeting the criteria is set by pulling stages onto the canvas connected to the red x.

In our example we have three stages set for high-level purchases and records that are not a high-level purchase only have two stages.

 

 

 

 

Let’s look at how the end user will see the stages.

In our example two of the stages were the same in each path; however, each stage is individual based on path so they could be completely different stages. Further conditions can also be added within each path to branch out the process even further. Remember that there is a maximum of 30 stages per process.

To achieve the same result as we designed above a stage can be skipped using a condition as well.

Here we have the condition and the maximum three stages set within the business process. If the estimated revenue is less than $5,000, per our condition, we want to skip the customer contact stage. With the condition box highlighted select the connector button from the toolbar and choose connect. All stages after the next immediate stage will be bordered in yellow with 2nd point beneath them. We are going to select the prepare estimate stage to be our 2nd point when the criteria is not met.

If we connect to the wrong stage, we can disconnect by highlighting the condition box, select the connector button and choose disconnect.

The view for the end user will be exactly as we saw above, but we did not have to create those duplicate stages twice.

Conditions are an awesome tool within a business process if you have additional things you want to do within certain records or if you have multiple areas within an organization that all have a particular record type but may need to process it in different ways.

Looking for more CRM resources? Check out our Resource Library for our free webinars on CRM.

– Jerica Coleman, CRM and Power BI Consultant

 

 

ryan mccollum
Ryan McCollum

Filed Under: CRM, Uncategorized Tagged With: CRM, Dynamics 365, IS Services, Microsoft, Microsoft Office 365, Online Services

CRM: Creating custom forms makes CRM more efficient

October 29, 2019

Time is money.

We’ve all heard it, many of us have said it and most of us believe it. In this digital age that fact has become even more true. With the ability to have data at your fingertips in a matter of seconds consumers are less likely to work with a business that makes them wait too long.

Smaller decisions have a larger effect.

This may be a newer thought for a lot of us, but it’s something I have heard stated more and more and it is true. Large decisions can have an immediate impact on business, but it is the smaller day to day decisions that have a more lasting impact and can revolutionize your business over time.

Creating custom forms within CRM doesn’t seem like a huge deal, but it saves time for your end users and ensures all necessary data is being collected, which saves time spent trying to track down missing data. Let’s look at a couple scenarios where not using custom forms can lose business.

Scenario 1:

A salesperson has an opportunity with a new client and an estimate needs to be provided. The salesperson gathers data about the project and then sends it to the project manager to get an estimate of what it will take to complete the project. Once they receive that they will write up the formal estimate and provide it to the customer.

With a non-customized CRM form there will be fields that do not need to be filled in, so the salesperson must scroll through and find the fields they need and try to make the data fit into general areas on the form. This results in a lot of pertinent data being typed into a description field and makes the initial form entry take a long time.

When the project manager receives the opportunity, they spend time reading through the form to piece together the project and there could be data missing. Missing data requires the project manager to email or call the salesperson with questions. Finally, the estimate information can be put together and sent back to the salesperson most likely typed into notes.

The salesperson now reads through the information and writes up a formal estimate to send the client.

By now the client has already received two other estimates from competitors and the costs are comparable, so the client chooses the one that provided their estimate the quickest. Consumers will view those businesses as more efficient and that sets the tone that those businesses would likely be more efficient in getting the project completed.

Scenario 2:

A current customer calls in with an issue that requires a service call. The customer explains to the phone agent exactly what is occurring.

The same thing occurs as with the salesperson where the phone agent must scroll through and find the fields to enter. This results in the customer being on the phone longer and other incoming calls are holding while the agent completes the form. With no customized fields the agent summarizes the problem as best they can within a description field and forgets a few questions they should ask the customer.

The information is sent to the service technician and they go out to the customers site. Upon arrival they are not prepared for the extent of the problem because the summarization was too brief, and questions were missed.

The customer is now upset because they are explaining the entire problem again and there is a delay in getting the problem resolved as the technician was not prepared.

Sales are important, but a business succeeds or fails on customer satisfaction after the initial purchase.

Now these scenarios may be extreme examples, but I have seen them happen within businesses. Using a generic form for your specialized business is like trying to fit a round peg into a square hole. This can result in low employee morale and low customer satisfaction.

When creating custom forms, it is important to spend time thinking about that particular process to help dictate how the form should flow. What information needs to be gathered? When is the information is collected and who is responsible for collecting it? Should forms be quick create to speed up the process or is it something that requires the longer form because of the amount of data necessary?

Always, create forms from the perspective of the end user. Saving just 5 minutes on form entry means that for every 100 records entered 8 hours of work is saved. Forms that are easy to use eliminate frustration for employees which raises morale and that is something that is vital to a successful business.

Watch for an upcoming blog post on the different things you can customize on CRM forms.

-Jerica Coleman, CRM and Power BI Consultant

ryan mccollum
Ryan McCollum

Filed Under: CRM Tagged With: CRM, Dynamics 365, IS Services, Microsoft Office 365, Office 365, Online Services

  • Page 1
  • Page 2
  • Go to Next Page »

Footer

We provide complete solutions for your business challenges.


920 O’Donnell St
Hawley, MN 56549

p. 218.486.5095
f. 218.486.5094

Connect With Us

  • Facebook
  • LinkedIn
  • YouTube

Our Solutions

  • wsTOOLS
  • Dynamics 365 for Financials
  • Microsoft Dynamics GP

Our Services

  • Business Process Review
  • ERP Software Consulting
  • Programming
  • Technical Consulting
  • Project Management
  • Report Writing
  • System Optimization & Review

Our Company

  • About Us
  • Testimonials
  • Careers
  • Contact Us

Our Resources

  • Resources
  • Blog
  • Events
  • Support

Join Our Mailing List!

  • This field is for validation purposes and should be left unchanged.
Copyright © 2026 Implementation Specialists | Privacy Policy | Terms of Service | Site Credits