I do demonstrations of quite a bit of functionality in Microsoft Dynamics GP which often necessitates restored databases or otherwise reversing transactions and processing. One of the modules I’ve done some demonstrations of recently is the Advanced Bank Reconciliation module from Nolan Business Solutions. One of the features of this module is allowing you to atch statement entries with transactions in Dynamics GP.
/* Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (http://www.azurecurve.co.uk)
This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0 Int).
NCABR011 --NC Matched Statement Trx 11003k (NCABR011)SET
NC_Matched = 0
,NC_Match_Number = 0
NC_Matched = 1
NCABR012 --NC_Matched_GL_TRX (NCABR012)SET
NC_Matched = 0
,NC_Match_Number = 0
NC_Matched = 1
This script was created for use ona demo/test system and appears to run without adverse effect, but I would recommend caution (via a backup) and thorough testing before using it on any system.
In our most recent webinar, we took a look at Powerful document generation for Dynamics GP. In this webinar, we covered how dox42 can be used to design attractive document templates in Microsoft Office and integrate data from Microsoft Dynamics GP and other systems such as SharePoint or Microsoft 365. If you want to catch up on this, or any other, webinar, you can do so here.
In this blog post, I am going to recap the webinar and show the benefits and some example uses of dox42 for generating documents with data from Dynamics GP and other systems:
dox42 are headquartered in Vienna Austria and sell dox42 through a partner channel using companies such as ISC Software. It allows you to generate individualised documents from all your existing systems, including Microsoft Dynamics GP, automatically. Offers, quotes, contracts, inspections or server-reports, presentations, Excel-charts and insurance policies; dox42 is a flexible, powerful and intuitive application which allows you to use the common interface of Microsoft Word, Excel or PowerPoint to design document templates.
I implemented Audit Trails from Fastpath for a client a while ago. They created the required triggers in a few company databases and all worked well.
Recently they deployed the triggers to another company, but none of the data was flowing through to the portal.
I did some investigation and found the triggers were working correctly as the audit tables in the company database were being populated, but the data collect wasn’t moving them to the audit table in the FPAUDIT database. Further investigation and a quick suggestion from the Fastpath support team had me checking permissions on the databases; the database triggers were being added to did not have the required permissions for the Fastpath SQL login.
When I checked with the user, this was a company created after the initial deployment of Audit Trails and so the user had never had permissions to this database. We re-ran the minimum permissions script and the data collect was then able to run successfully and collect the audit changes from the new company.
In our most recent webinar, we took a look at Controls & Security in Microsoft Dynamics GP. In this webinar, we covered how you can improve controls and security in Microsoft Dynamics GP using a mix of standard ad third party functionality. If you want to catch up on this, or any other, webinar, you can do so here.
In this blog post, I am going to recap the webinar and cover the salient points:
As always in this type of webinar, I try to use standard functionality as far as possible, but this is not always possible as not all of the areas being covered are included as standard. This was a deliberate design decision from the very creation of Microsoft Dynamics GP where they decided that supporting third parties would allow many more developers to work on modules for the system and encourage competition and improved standards from those third parties (known as Independent Software Vendors or ISVs for short).
There are three key areas where I am recommending third party modules and I will try to be clear when I am doing this.
In our most recent webinar, we took a look at Automation in Microsoft Dynamics GP. In this webinar, we covered how automation can be used in Microsoft Dynamics GP to improve efficiencies and accuracy of data. If you want to catch up on this, or any other, webinar, you can do so here.
In this blog post, I am going to recap the webinar and cover the highlights of how automation can be used in Microsoft Dynamics GP to improve efficiencies and improve data accuracy:
Where possible in this webinar I highlighted standard, or Microsoft supplied, features or additional products where they are available. However, in many cases the standard functionality does not allow for full automation. This is an intentional design choice made when Microsoft Dynamics GP was first created back in the md-90s. The company who created Great Plains, the original name of Dynamics GP, was intended from the very beginning to be extensible with the intention that there be a thriving third-party marketplace for add-ons.
This is the current situation; the core Dynamics GP system has strong core financials and distribution modules, but wider functionality is provided by third party (Independent Software Vendors (ISVs) who have a variety of add-ons and complimentary products which provide the functionality required or automating processes. In each of the areas, there are usually a number of products available from several vendors, but I have selected one in each area. usually an add-on which I have used with several clients across a number of years and which has received positive reviews.
Before implementing one of the solutions, I’d recommend reviewing the functionality it includes, the functionality of competing products and making your own decision about which will best fit your requirements.
I’ve been doing work with a client recently to refrsh their security in Microsoft Dynamics GP. We used the Microsoft Dynamics GP Security Matrixc from Fastpath to get the core security tasks assigned to the relevant roles. However, after security roles were created and testing was done, one user role was received errors when logging into Microsoft Dynamics GP:
You don't have security privileges to open this window. Contact your system administrator for assistance.
The Audot-Detect rules covered in the last post are sufficient for those cases when workflow is not being used or when the auto-detect rule can be configured using the Batch Number. I’ve worked with a few clients to implement Post Master Enterprise now and there usually comes a point when the in-built rules are not sufficient.
However, Post Master Enterprise can be extended to allow more complex auto-detect rules including selecting only batches approved in workflow (as a side note, I’ve discussed this with Envisage and for workflow batches they are looking at including this as a standard feature in the Auto-Detect window). Post Master Enterprise has been developed to call pro and post SQL stored procedures which can be used to insert batches in the pending table.
The pre/post stored procedures are deployed by Post Master Enterprise during the installation, but don’t include any functionality. The first time we did this, Envisage supplied some standard code to submit a batch into the pending tables and I extended that with my SQL function to return Workflow Status to pick up only those batches at a status of Final Approval.
This approach could be taken to select batches based on any criteria (such as user who posted, posting date or even specific GL accounts).