With the advent of the web client, a lot of things have had to change in the way we create customizations in Dynamics GP. VBA is not used with the web client, so right away, all those old VBA
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.
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
PaperSave, a software developed by WhiteOwl, is a complete document management, electronic workflow, and transaction automation solution that directly interface with Microsoft CRM, Microsoft Dynamics GP, Microsoft Dynamics AX, Microsoft Dynamics SL, and other ERP systems.
The advantages of the PaperSave Document Management Solution are more than just going ‘Green’ and reducing paper. Here is a list of the many benefits that may be realized by using PaperSave:
Another year has come and gone, seemingly faster than ever – and we’re already into the second month of 2016. At the end of 2015 or in early January, some people were writing about Business Intelligence (BI) and Corporate Performance Management (CPM) trends they predicted we would see manifest this year. However, much like my current approach to New Year’s resolutions, I felt it was important to let the dust settle, work through the workload hangover of the holidays, and have the New Year function as a soft opening. This way, we can approach 2016 with a rolling start that doesn’t set us up for failure. This article will discuss some key trends and trajectories that data management and analytics will take in 2016.
Recently we had the task of getting a large number of customization that had been created using VBA and Modifier to function on the GP2015 Web Client. Since VBA will not function on the web client, we had the option of re-writing the functionality in Dexterity or Dot Net. Our development team is mainly focused on Dot Net, with a few of us that are well versed in Dexterity. For this reason, we decided that Dot Net would be the best tool to use in this
The Dynamics world is all a buzz with the news of GP2016 set to release right around Envision (Convergence for those of you who remember the old days.) There are some great new features and enhancements with this version, one of the most exciting being the HTML5 Web Client!
Sign up for our mailing list to get the latest updates and offers.