Category: Microsoft

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 2^nd 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 seventeenth new feature is SmartList Designer Favourites in Navigation List. This feature will see favourites created for SmartList Designer SmartList objects added to the SmartList Favorites navigation list.

As an example, I have created a Vendor EFT SmartList object in SmartList Designer and saved a couple of favourites:

Continue reading “Hands On With Microsoft Dynamics GP 2018 R2 New Features: SmartList Designer Favourites in Navigation List”

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 2^nd 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 sixteenth new feature is Option To Not Display Inactive Checkbooks in Lookup. This feature allows users to hide inactive checkbooks when performing a lookup.

When doing a lookup on Checkbook ID, click the blue bar above the list and select Exclude Inactive Checkbooks:

Continue reading “Hands On With Microsoft Dynamics GP 2018 R2 New Features: Option To Not Display Inactive Checkbooks in Lookup”

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 2^nd 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 fifteenth new feature is Checkbook ID Defaults on Check Batch. This feature means that when you create a new EFT payment batch in Payables Management, the Checkbook ID field will be automatically populated from Payables Management Setup:

Again, this is a small feature, but will save users time selecting the chequebook when creating a payment batch. It never really made sense that the chequebook would default in on a cheque batch, but not on an EFT one. This has now been remedied so both types of payment batch work the same way.

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 2^nd 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 fourteenth new feature is Duplicate Check Numbers Option Extended.

This feature sees the Checkbook Maintenance (Financial area page » Cards » Chechbook) option to allow or not allow Duplicate Check Numbers extended to other windows. This means that if this option is not marked, duplicate checks are not allowed in these three windows. Previously, this option only applied to Payables checkbooks but now it includes:

• Bank Transaction Entry
• Payroll Manual Checks
• Miscellaneous Checks

Continue reading “Hands On With Microsoft Dynamics GP 2018 R2 New Features: Duplicate Check Numbers Option Extended”

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 2^nd 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 thirteenth new feature is Email Customer Statements. This feature of the day allows a single statement to be emailed to a customer direct from the Customer Maintenance window (Sales area page » Cards » Customer) using the Email button on the action pane:

Continue reading “Hands On With Microsoft Dynamics GP 2018 R2 New Features: Email Customer Statements”

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 2^nd 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 eleventh new feature is Increase Dynamics GP Password Maximum Length. This feature sees the maximum length of user passwords increased from 15 to 21 characters:

Any increase in the maximum length of passwords is to be welcomed, but, seeing as this change required a database schema change to increase the SQL field length from 15 to 21, I am a little surprised that the new length is only 21 characters.

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 2^nd 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 tenth new feature is Exclude Items on HITB Report With Zero Quantity or Value. This feature adds two new options to the Historical Inventory Trial Balance (HITB) report. The new options are:

• Include Items with Zero Quantity
• Include Items with Zero Value

These items will be excluded on the report if the options are not checked; previously, by default, these items were included. Make sure the checkboxes are unmarked to exclude the items with either zero value or quantity:

When I first read this feature of the day announcement, I thought it would be a good addition. However, now that I’ve been hands on with it, I’m not so sure. Initially, I’d misremembered what the HITB showed; it is basically a report which shows movement of stock. The report I was thinking of, is the Stock Status report and it already allows you to filter out zero quantities or values.

Having played around on Fabrikam, I can’t actually see how excluding items would be useful from the HITB report; when running a Trial Balance, you’d want to see all transactions.

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 2^nd 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 ninth new feature is New SmartList for Deposits on Unposted Sales Transactions Has Been Created. This feature adds a new Deposits on Unposted Sales Transactions favourite to the Sales Transactions SmartList object:

When the feature of the day post was announced, I expressed some skepticism as to the value of it. It is basically a copy of the default favourite with two columns removed and the Deposit Received column added; very quick and easy to create if it is needed.

I’ve not really changed my mind. It might save you 20 seconds once to create the favourite if you wanted it, but nothing more.

I’d have been happier if it was a new SmartList Object, such as a Budget SmartList, instead of just a new favourite.