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.
Use tax, the lesser known counterpart of sales tax, suffers from a basic lack of PR. Buyers and sellers alike pay it no mind. Despite 27 states having a dedicated line item in tax returns for reporting use tax owed, only 2% of taxpayers actually report it. This has left the states with a $23 billion deficit annually in uncollected use tax.
Your ERP system (Dynamics GP) is the backbone of many organizations. A plan should be in place to support Dynamics GP in order to minimize issues, downtime, or data loss. Here are a few ideas to better maintain your ERP system.
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.
Almost every major software company encourages and solicits other companies, knows as ISV’s, to develop solutions for their packages to give them a broader appeal. For those that aren’t sure what an ISV is, an
Microsoft Dynamics Customer Relationship Management (CRM) is a fantastic tool for managing customers, accounts, cases, opportunity, sales people, etc. The possibilities with CRM are endless, which is why we often refer to it as xRM (the x can be anything you want it to be). As a CRM implementation, support, and development partner we often get questions from customer starting out with, “Can CRM do (insert request here)?” And the answer is usually, “Sure it can, but the question really is ‘Do you have the data to support a function like that’?”
Sign up for our mailing list to get the latest updates and offers.