Invoice ID: The identifying number or code of the invoice.
Name: A descriptive name for the invoice. Currency: The local currency for the record. This makes sure that budgets are reported in the correct currency.
Price List: The price list associated with this record. This makes sure that the products associated with the campaign are offered at the correct prices.
Prices Locked: Status of prices specified on the invoice. They may be locked from any further updates or unlocked.
Date Delivered: Date when the products included in the invoice were delivered.
Due Date: Date by which the invoice should be paid by the customer.
Office 2010 / Microsoft Dynamics CRM Demo -- Coordinating Sales and Customer Support (Part 2 of 2)
In this demonstration, you will see how the user, such as an account manager, can easily access customer information from a central dashboard in SharePoint Server 2010, and also seamlessly access customer data stored in Microsoft Dynamics CRM.
Record Type: Product Catalog
In Microsoft Dynamics CRM Product Calalog has following componenets:
Products: Product Represents
Units of Measure:
Unit of how received from Vendor
or Sold to Customer
Defines prices that are charges for product under ceration circumstances.
Can be muplitple price lists for different occasions and markets.
Discount Lists: Allows to offer product at different sales price, depending on quantity purchased.
Discount can be:
Dynamics CRM 2011 Workflows, Queue Items and E-Mail Marketing
This video shows how to use CRM 2011 workflows to automatically route CoreMotives e-mail responses to queues.
Goal Management is one of the great new features in CRM 2011, but like a lot of great new features...it's got a bit of a learning curve! One question I get a lot is how do goal criteria work, and in particular, when do you need to use a rollup query. That's the topic of this recording.
[Job] - Accenture: Microsoft Dynamics CRM, India
Location: Pune, India
"Role:- Developer Years of experience:- 3 to 4 years
Must to have:-
• Experience with Microsoft CRM 2011 Modules and features related
• Experience with Microsoft CRM 2011 customizations and Configuration [Sitemap, Writing jScripts, Developing/Registering plug-ins, workflows and dialogs, SDK, importing data and CRM Deployment Manager
• Experience with developing and implementing web/windows applications with Microsoft Visual Studio .Net
• Experience with developing XML Web Services and Server components
• Experience in writing oData and Linq
• Identify build or development changes, code and peer reviews and unit testing
• Experienced working on development project Good to have:"
- Basic qualifications
Full Time Graduation
What is Plugin Profiler?
Plug-in Profiler is a tool that profiles the execution of plug-ins for an enhanced debugging experience in Microsoft Visual Studio. Thistool can be used in either the debug or replay mode.
This can be run from the Command Prompt window or from within the Plug-in Registration tool, makes developing plug-ins against Microsoft Dynamics CRM and Microsoft Dynamics CRM Online quicker and easier.
In the tool's main window, select Install Profiler. You will now see a Plug-in Profiler node in the list.
Select a plug-in step and click Profile to enable profiling.
Perform the operation in Microsoft Dynamics CRM that causes the plug-in to run. For example, if the step is configured for an update to an account, then update an account.
After the plug-in throws an exception and the Business Process Error dialog is displayed, click Download Log File and save this file. Alternately, if the plug-in does not throw an exception, click Stop Profiling.
Conditional formatting of grid records in Microsoft Dynamics 365
Microsoft Dynamics 365 lacks essential feature conditional formatting similar to which we have in Microsoft Excel which is often demanded by the business users.
With Color Grid for Microsoft Dynamics 365 you can colorize grid records in Microsoft Dynamics 365 based on a certain criteria, color schemes are also completely configurable to match the customers taste and can be configured by the end users.
Some examples of using Color Grid are:
Highlight HIGH priority cases
Highlight today's activities
Highlight Qualified leads
Highlight Opportunities with revenue Greater than X amount
Highlight Due activities in Next 7 days
Following is the link to Color Grid for Microsoft Dynamics 365
Above grid formatting are applied based on matching of certain criteria on particular field value of record which could be string, numeric or date type field.
To define the matching criteria multiple operators are available as defined below, these matching criteria are similar to what is available in advanced find of Microsoft Dynamics 365:
Does Not Equal
Does Not Contain
Does Not Begin With
Does Not End With
Does Not Contains Data
Is Greater Than
Is Greater Than or Equal To
Is Less Than
Is Less Than or Equal To
On or After
On or Before
Next 7 Days
Last 7 Days
Example: Colorize case records based on PRIORITY options (High, Normal, Low)
High priority Option Text
Create a Color Config record to match the below values
Normal priority Option Text
Low priority Option Text
Now all three criteria are defined, open the case grid to view the result
To have the impact selected attribute should be visible in the column of grid.
Hope you like it, if you have any query or suggestion please comment.
For any query about Color Grid for Microsoft Dynamics 365 please email to firstname.lastname@example.org
Email Router Demystified in MS CRM Part -3
Troubleshooting Incoming email issues
Now let’s shift our focus on troubleshooting to incoming email issues. This is where the Email Router is going to connect to a mailbox and process the mail. There are a few things to take into consideration when we talk about troubleshooting incoming emails. The first one is to figure out if the user configuration is set to use Email Router or Forward Mailbox. Each of these have different troubleshooting steps.
Troubleshooting the Incoming Email option for Email Router is relatively simple. It’s very similar to the Outgoing troubleshooting steps. For this route, the user’s “Incoming Email” option must be set to Email Router:
Since this user is configured to use the Email Router for “Incoming Email” lets refer to the following mail flow diagram referenced from the earlier blog post (Email Router Demystified – Explanation) in the section labeled “E-mail Router – Incoming E-mails”:
Each step constitutes a potential problem so let’s break down each step below:
Someone must send an email to the user. Now, it’s important to ensure that the Email Router is connecting to the same mail profile that the user is using within Outlook. I have actually run into cases where the user’s mail profile is configured for a different mailbox within Outlook and the Email Router is configured to use another one. Typically, this is seen where the Email Address for the user in CRM does not match what is in Outlook.
The Email Router connects to the user’s mailbox. There are a few things that could be an issue here:
Connecting to the user’s mailbox: This is done by what is specified in the Incoming profile, specifically what is set under Access Credentials.
If Access Credentials is set to Other Specified, then this is going to be using a service account or the user’s own credentials to connect to the mailbox. If using a service account, that account must have permissions to access user’s mailboxes.
You can give permissions, within Exchange, per mailbox using the Add-MailboxPermission or you can set the service account to use a Role Group such as View-only Organization Management. However it is done, the credentials must allow for GetFolder and GetItem requests within the mailbox.
Exchange is not the only protocol we can use to process incoming emails. We can use POP3 as well. In this case, you need to work with the POP3 provider to determine how to give access to a service account to other user’s mailbox
User has not specified credentials in the Mailbox profile: If you have defined the Access Credentials within the Email Router to use User Specified, the user must enter in their credentials within their mailbox profile
The user is not listed in the Email Router Configuration Manager after clicking on Load Data: This could be due to the Email Access Configuration for the user not set to Email Router for Outgoing or the user’s email address has not been approved.
Lastly, once the Email Router has processed the inbox and it has items to send to CRM, it must connect to CRM and query to see if the email should be a CRM email. A user’s personal options dictate what emails make it into CRM. If we go into the Personal Options for Email, what is the option for “Select the email messages to track in Microsoft Dynamics CRM”? Based on the setting determines what emails are created or promoted into CRM:
All email messages – This will promote every incoming email the user receives
Email messages in response to CRM email – This will promote only emails that were either sent out of CRM or they were in response to an email that was tracked within the CRM Outlook client
Email messages from CRM Leads, Contacts and Accounts – This will promote any emails that have an email address that correlate to a Lead, Contact, or Account
Email messages from CRM records that are email enabled – This will promote any emails that have an email address to any CRM records that are email enabled.
Additionally, if you are sending emails between users and you want both the outgoing and incoming emails to be created into Microsoft Dynamics CRM, you must check the Email System Setting for “Track emails sent between CRM users as two activities”
If the user’s profile for “Incoming Email” is set to Forward Mailbox, then this will mean that the Email Router is going to be connecting to a Forward Mailbox and processing email from that mailbox:
This would mean that we would need to refer to the following mail flow diagram referenced from the earlier blog post (Email Router Demystified – Explanation) in the section labeled “Forward Mailbox”:
Again, each one of these steps indicate a potential break point in the email routing process for the forward mailbox. You’ll notice that this is very similar to the Email Router method except that the email router is no longer connecting directly to a user’s mailbox but to a forward mailbox. Additionally, emails are being forwarded as an attachment from the user mailbox into the forward mailbox. Hence why we call it the forward mailbox.
Since most of what we talked about previous applies to the Forward Mailbox option, I will simply highlight them rather than going through those steps in detail:
Someone must send an email to the user.
The email is being forwarded as an attachment from the primary user’s mailbox into the forward mailbox. We use the Rule Deployment Wizard to try and help to automate this task by applying the forwarding rules programmatically for users. However, there are situations where the Rule Deployment Wizard does not work and you must manually create this rule. The bare necessities of the rule is that you forward the email as an attachment to the mailbox you designated as the forward mailbox:
The Email Router connects to the Forward Mailbox. The Forward Mailbox is defined within the Email Router Configuration Manager:
Lastly, once the Email Router has processed the forward mailbox and it has items to send to CRM, it must connect to CRM and query to see if the email should be a CRM email. A user’s personal options dictate what emails make it into CRM as we discussed above.
Once the Email Router has been able to process the email for the forward mailbox, it has the ability to delete the message out of the mailbox for the forward mailbox as long as the option within the Forward Mailbox profile has been set: This helps maintain the size of the forward mailbox and not to retain emails that are unnecessary for the forward mailbox.
So now that we understand the various breakpoints, we can now determine what tools we can use based on the different Incoming protocols being used. Troubleshooting incoming issues are the same as troubleshooting outgoing email issues. Our two options, realistically, is Exchange Web Services (EWS) and POP3.
When we are connecting to Exchange, we are connecting using Exchange Web Services. We’ve already seen how we can troubleshoot EWS issues by using Fiddler and by using EWS Editor.
Troubleshooting POP3 issues are like troubleshooting SMTP issues. To troubleshoot POP3 issues, we use a network sniffer like Microsoft Network Monitor (NetMon).