Merry Christmas to everyone in the Microsoft Dynamics GP and ClassicPress communities and to anyone else reading this.
I usually just include a Christmas card type image, but thought I’d give you a song this year (although I’m sure you’ll be pleased to know I’m not the one singing). I’ve spent a lot of time in Ireland this year and YouTube has started suggesting Irish music to me, so here is a Christmas song from Celtic Woman:
This post is part of the Hands On with Microsoft Dynamics GP October 2019 Release New Features – Financial Enhancements series where I am going hands on with the financial enhancements of the new version of Microsoft Dynamics GP; it is part of the larger Hands On with Microsoft Dynamics GP October 2019 Release New Features series.
The fourth financial enhancement is the addition of Class ID to the Transfer and Mass Transfer windows; when you change the class Id, the assigned GL accounts will default from a related account group and can then be edited:
This addition should prove quite useful when transferring assets, as updating the GL accounts is often something clients want to do when performing this action.
This post is part of the Hands On with Microsoft Dynamics GP October 2019 Release New Features – Financial Enhancements series where I am going hands on with the financial enhancements of the new version of Microsoft Dynamics GP; it is part of the larger Hands On with Microsoft Dynamics GP October 2019 Release New Features series.
The third financial enhancement is the addition of a User Who Posted field on the Journal Entry Inquiry window () now has a new field that shows the user who posted the entry:
The User Who Posted field shows for both open and historical journals. Being able to see information on which user has been entering or posting transactions has become a much more common question from clients recently, so it is nice to see this addition.
I’ve posted a couple of articles now on making MySQL backups using Cron, time-based scheduler, on Linux based hosting.
This is, currently, the last post on this subject. The examples so far have been on backing up single databases, but it is possible to backup multiple databases using one command.
The below example shows the syntax to make a compressed backup of all mySQL databases, with the sections to change highlighted:
/*
Created by Ian Grieve of azurecurve | Ramblings of an IT Professional (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).
*/
/usr/bin/mysqldump -u {username} -p'{password}' --all-databases | gzip -c > /home/{username}/backups/backup_{databasename}_$(date +\%Y\%m\%d\%H\%M\%S).sql.gz
The below example shows the syntax to make a compressed backup of multiple named mySQL databases, with the sections to change highlighted (any additional database names can be specified):
/*
Created by Ian Grieve of azurecurve | Ramblings of an IT Professional (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).
*/
/usr/bin/mysqldump -u {username} -p'{password}' --databases {databasename} {databasename} | gzip -c > /home/{username}/backups/backup_{databasename}_$(date +\%Y\%m\%d\%H\%M\%S).sql.gz
Earlier this month I posted an article on making MySQL backups using Cron, time-based scheduler, on Linux based hosting.
Since then I’ve realised that I have two databases which are well over 1GB in size and have now looked into making compressed backups.
The below example shows the syntax to make a compressed backup of a mySQL database, with the sections to change highlighted:
/*
Created by Ian Grieve of azurecurve | Ramblings of an IT Professional (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).
*/
/usr/bin/mysqldump -u {username}-p'{password}' {databasename} | gzip -c > /home/{username}/backups/backup_{databasename}_$(date +\%Y\%m\%d\%H\%M\%S).sql.gz
This is only a little different to the uncompressed backup syntax, but results in a file of much smaller size.
This post is part of the Hands On with Microsoft Dynamics GP October 2019 Release New Features – Financial Enhancements series where I am going hands on with the financial enhancements of the new version of Microsoft Dynamics GP; it is part of the larger Hands On with Microsoft Dynamics GP October 2019 Release New Features series.
The second financial enhancement is to the Fiscal Period Setup window () where the length has been extended to give you an expanded view of the fiscal periods:
As every company I work with has had at least 12 periods, it always annoyed me that the window only shows the first 8 and you had to scroll. This will make life easier for clients when they are closing or opening periods at month end as well as for those who have financial periods which are not based on a calendar month (I have a few operating a 4-4-5 weekly cycle).
This post is part of the Hands On with Microsoft Dynamics GP October 2019 Release New Features – Financial Enhancements series where I am going hands on with the financial enhancements of the new version of Microsoft Dynamics GP; it is part of the larger Hands On with Microsoft Dynamics GP October 2019 Release New Features series.
The first financial enhancement is the addition of a Long Description field, allowing up to 200 characters, to payables transactions. The new long description needs to be enabled before it can be used. To enable the new field, open Payables Management Setup () and mark the Enable Long Description in Payables Transaction Entry:
This post is part of the Hands On with Microsoft Dynamics GP October 2019 Release New Features – Financial Enhancements series where I am going hands on with the financial enhancements of the new version of Microsoft Dynamics GP; it is part of the larger Hands On with Microsoft Dynamics GP October 2019 Release New Features series.
This post is the series index for the financial enhancements made to Microsoft Dynamics GP October 2019 Release
The series index will, if you’re heading this on azurecurve|Ramblings of a Dynamics GP Consultant, automatically update as posts go-live.
This post is part of the Hands On with Microsoft Dynamics GP October 2019 Release New Features – System Enhancements series where I am going hands on with the system enhancements of the new version of Microsoft Dynamics GP; it is part of the larger Hands On with Microsoft Dynamics GP October 2019 Release New Features series.
The fourth and final enhancement in the System module is the ability to add more than 32 report options to a report group:
This is an enhancement to all of the report groups throughout Microsoft Dynamics GP, but is an odd addition. I don’t have a single client who will find this at all useful.
Most clients don’t generate many reports using the standard reports functionality in Dynamics GP, but rather use a variety of tools such as Management Reporter, Jet Reports, Reporting Services Reports, Qlik and so on to get the reports they require. They will likely use the Aged TBs in Payables and Receivables, but even there are often using the Reporting Services version.
This post is part of the Hands On with Microsoft Dynamics GP October 2019 Release New Features – System Enhancements series where I am going hands on with the system enhancements of the new version of Microsoft Dynamics GP; it is part of the larger Hands On with Microsoft Dynamics GP October 2019 Release New Features series.
The third of the new features in the system module, is the ability to filter inactive users from the list in the User Access Setup window () by unmarking the Include Inactive Users checkbox:
