In the upcoming KTL User Conference 2016, we will have a session on the benefits of moving to CRM Online. You will get all the details on the ease of the move, plus details on the additional features you will get just by choosing CRM Online. As I type this blog, Microsoft has already released the preview guide for what’s coming as an update to CRM in Spring 2016.
You can increase productivity and efficiency by using hyperlinks in your Excel documents. Hyperlinks are incredibly easy to setup and even easier to use.
Reports are a way of presenting useful data to the users in an organized format. CRM reporting needs are often solved by using out-of-box CRM reports, Advanced Find,
When writing a custom SSRS report for CRM, one of the greatest features is the ability to include pre-filtering in your reports. By adding the CRMAF_ prefix to the alias assigned to the table you are querying, it will pass your selected CRM records as the context for your report. E.g.:
SELECT * FROM FilteredAccount AS CRMAF_Account
When writing a custom SSRS report for CRM, one of the greatest features is the ability to include pre-filtering in your reports. By adding the CRMAF_ prefix to the alias assigned to the table you are querying, it will pass your selected CRM records as the context for your report. E.g.:
SELECT * FROM FilteredAccount AS CRMAF_Account
When writing a custom SSRS report for CRM, one of the greatest features is the ability to include pre-filtering in your reports. By adding the CRMAF_ prefix to the alias assigned to the table you are querying, it will pass your selected CRM records as the context for your report. E.g.:
SELECT * FROM FilteredAccount AS CRMAF_Account
When writing a custom SSRS report for CRM, one of the greatest features is the ability to include pre-filtering in your reports. By adding the CRMAF_ prefix to the alias assigned to the table you are querying, it will pass your selected CRM records as the context for your report. E.g.:
SELECT * FROM FilteredAccount AS CRMAF_Account
When writing a custom SSRS report for CRM, one of the greatest features is the ability to include pre-filtering in your reports. By adding the CRMAF_ prefix to the alias assigned to the table you are querying, it will pass your selected CRM records as the context for your report. E.g.:
SELECT * FROM FilteredAccount AS CRMAF_Account
Having attended, but not spoken at the KTL User Conferences of the past, I have a unique perspective on attendee observations. Without the time constraints imposed by presenting at sessions, I get a chance to sit with and chat with attendees, go over things at lunch and generally “kibitz” with everyone while at the conference.
The “IPluginExecutionContext” contains a property called “MessageName.” This is the name of the message that was called to perform the action. Here is a link to a list of messages: https://msdn.microsoft.com/en-us/library/gg309482.aspx . I couldn’t find my original source for this, so you can assume that each message name is just the class name listed without the request at the end. The one we are interested in is the “ConvertQuotetoSalesOrderRequest” or the “ConvertQuoteToSalesOrder” message. This is what is called when you click the “Create Order” button and can be called through the API as well. So to figure out if that is what is creating our sales order we would simply need to traverse the parent context list and check to see if the “MessageName” property equals “ConvertQuoteToSalesOrder”. Here is a code snippet to do that.
At KTL
Stopping an operation using a plugin is a simple process. All you need to do is throw an exception, but its best to not just throw any exception. CRM provides the “InvalidPluginExectionException” that allows you to pass in a message that will get displayed to the user. Using that, we can alert the user that the action they took is not allowed and guide them in the direction of the correct way to create an order.
The customer wants to stop users and outside processes from being able to create a sales order directly in CRM. Instead, they have set up a requirement that all sales orders must be created through the sales process. They first create a quote and then use the CRM “Create Order” button on a submitted quote form to convert that quote into a sales order.
The write off routine is quick and simple to use in Microsoft Dynamics GP 2015. This blog will go through quick, step-by-step procedures on how to go through the write off routine within GP.
Sign up for our mailing list to get the latest updates and offers.