Month: December 2018

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.

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 eighth new feature is Vendor Document Number added to Purchasing All-in-One View. This feature adds the Document Number to the Payments and Credits column of the Purchasing All-in-One View (Purchasing area page » Enquiry/Inquiry » Purchasing All-in-One View):

This feature is a good feature which will provide additional information to users that they have found the correct information.

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 seventh new feature is .When transaction posting is enabled, this feature allows users to perform posting through the General Ledger at a transaction level. The following is a list of supported transactions for this feature:

• Invoice Entry
• Receivables Apply Doc.
• Receivables Cash Receipts
• Receivables Sales Entry
• Sales Deposits
• Sales Trx Entry
• Voided Trx Maintenance (Sales)
• Payables Trx Entry
• Payment Entry
• Purchasing Invoice Entry
• Purchasing Prepayments
• Receivings Trx Entry
• Returns Trx Entry
• Assembly Entry
• Transaction Entry (Inventory)
• Transfer Entry
• Manual Checks (Payroll)
• Project Accounting Transaction windows except Project Closing

To enable post through for transactions, open the Posting Setup window (Administration area page » Setup » Posting » Posting), and mark the Post Through General Ledger checkbox below the Allow Transaction Posting one:

In theory this is a great addition to Dynamics GP, as many clients want to do transaction level posting, although more these days are wanting to use workflow for approvals which still requires batches.

However, in my testing so far, all Sales transactions which I post using post through work fine, but nothing on Payables posts through at transaction level regardless of the settings.

I need to do additional testing, but so far this feature isn’t looking good.