This post is part of the Hands On With Microsoft Dynamics GP 2018 R2 New Features series in which I am going hands on with the new features introduced in Microsoft Dynamics GP 2018 R2 (which was released on the 2nd October). I reblogged the new features as Microsoft announced them along with some commentary of how I thought they would be received by both my clients and I. In this series, I will be hands on with them giving feedback of how well they work in reality.
The twenty-first new feature is Ship To Address Retained by Customer Combiner. This feature will retain the ship to address when customers are merged using the Customer Combiner tool:
I’ve tested this feature and compared it to the functionality in 2018 RTM, and I can’t tell the difference. The Ship To address of the destination customer, does not change in either version and the ship to address from both the source and destination customers are both available after the combine.
The Inside Microsoft Dynamics GP blog has started a series Feature of the Day posts for Microsoft Dynamics GP 2018 R2 on which I am following and adding commentary. The series index for this series of posts is here.
The twenty-fourth Feature of the Day is Ship To address retained by Customer Combiner.
When using the Customer Combiner tool to combine two customer records the ship to address will now be retained:
While Customer Combiner isn’t generally used that much (at least by my clients), keeping the ship to address could potentially be very useful.
We are currently in the process of upgrading a large 20 site client from Microsoft Dynamics GP 9 to a later version (unfortunately not 2015 due to third party add-ons which are not supported on this version). The client previously had standalone implementations at each site, but we are aggregating them into one implementation for ease of maintenance and also to reduce licensing costs.
The first few we centralised went fine, but we then ran into problems when we did the head office companies. When they ran the GL Summary TB on the old and new systems there was a mismatch between them.
After investigating, the support team established that the problem was down to some corruption in the Account Index Master table (GL00105) where some of the accounts had segments separated with dots instead of dashes as defined in Account Format Setup ( ).
The solution they followed was fairly simple, and in three steps:
- Run a script to clear the Account Index Master table:
DELETE FROM GL00105
- Run Check Links ( ) on Account Master.
- Run the General Ledger Reconcile utility (
) on all years starting with the oldest and working forward.
After this was done, the report produced from the upgraded system matched the old one.
The Inside Microsoft Dynamics GP blog started a series of Microsoft Dynamics GP 2013 R2 Feature of the day posts the other day. As they did with the Microsoft Dynamics GP 2013 Feature of the Day posts they are doing them as short posts containing a PowerPoint slide show. I am translating these from the PowerPoints into posts; you can find my series index here.
The thirty-third Feature of the Day covered is OLE Notes Migration Utility. The ability to attach documents to record level notes has been available in Microsoft Dynamics GP for a long time. The record notes were always stored as OLE attachments until now; in Microsoft Dynamics GP, the OLE Notes have been replaced with the Document Attachment functionality which stores the notes directly in the Microsoft SQL Server Database.
To facilitate this, a Migration Utility, which runs as a separate application, can be obtained from PartnerSource/CustomerSource. The utility will allow existing users to migrate the files that have already been attached to Notes using the existing OLE functionality into the new Document Attach functionality:
I’ve never liked the OLE Attachment available in record level notes; if one client had a different path defined in the ini file and the user opened and saved a window the attachments then they would get corrupted. Using Document Attachment functionality removes this risk of data corruption and provides functionality which is much more robust.
This feature is targeted at the following roles:
- System Implementers
He somehow slipped it out without me noticing, but David Musgrave of the Developing for Dynamics GP blog released Support Debugging Tool Build 17 before Christmas; this is the build which added support for Microsoft Dynamics GP 2013.
He was back yesterday with a hotfix release to fix a couple of issues.
Partners can download SDT from PartnerSource (login required); if you’re a customer you’ll need to contact your partner to obtain it for you.
David has links to SDT for Microsoft Dynamics GP 10 and 2010 here.
In this post I’m stepping away, briefly, from Microsoft Dynamics GP but will return in to it in my next post.
Microsoft have recently released a raft of new versions, including Microsoft Dynamics GP 2013 and Management Reporter 2012 Rollup 3, and to test I’ve been installing a few new virtual machines with Windows Server 2012 and have also updated a couple of machines with Windows 8 and, because they’re new machines without DVD players in them, to do this I used the Windows USB/DVD Download Tool which is available for free download from the Microsoft CodePlex|Project Hosting for Open Source Projects site in order to create a bootable USB drive. [Updated link on 20/4/2019 as CodePlex has been closed.]
I thought a step by step guide for others needing to install Windows 8 (or other version of Windows) might be of benefit. So after downloading the utility from the above link, double click the downloaded setup file to install the Windows 7 USB/DVD Download Tool Setup Wizard;
Continue reading “How To Make A Bootable Windows 8 USB Drive”