Skip to main content

Handy Opportunity Views for Dynamics CRM

As a user of Microsoft Dynamics CRM, I find myself creating my own views frequently, and sharing the most popular of them with other users at my company.  Here are some of the views that I use for Opportunities:

  1. Opportunities by Owner. This is the most frequent view that I use for pipeline meetings.  Included fields are Topic, Potential Customer, Sales Stage, Est. Close Date, Proposed Date, Est. Revenue, and Owner. 
  2. Opportunities with Proposals Due.  Add fields for RFP Received and Proposal Due dates. Filter by status of RFP Received and sort by Proposal Due date.  Great way for quick glance at proposals that are in the works. 
  3. Proposed Opportunities by dollar threshold. Create a dollar threshold for what you consider to be large projects and apply it as a filter along with status of "proposed".  You can also sort by value in other views, but using this view allows you to exclude smaller projects and still sort by owner. 
  4. Opportunities by Type.  We added a field to show the type of project for an opportunity.  This is not a standard field in CRM but quite handy for understanding the breakdown of opportunities and useful for dashboard views as well. 
You can start by creating your personal view and show them to other users.  If they are a hit, you can ask your system administrator to add them to system views which are visible to other users.  If you drop down the list of views for Opportunities, the following menu appears.  Near the bottom of the menu is the option to create a personal view. 

If you choose Create Personal View, you will get to the Advanced Find screen where you can create a new view. 

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ by James Townsend Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do