Day: November 11, 2016

The Inside Microsoft Dynamics GP blog has started a series Feature of the Day posts for Microsoft Dynamics GP 2016 R2; as the most recent versions have been, these posts are in the form of PowerPoint slides; I am reposting them here so they can be read more easily.

The series index for this series of posts is here

The sixth Feature of the Day is Display Tax Percent for Historical Sales Transactions.

When drilling into the Sales Tax Summary Enquiry, the tax percent used at time of transaction displays instead of the percent that is setup on the tax detail maintenance window.

The Inside Microsoft Dynamics GP blog has started a series Feature of the Day posts for Microsoft Dynamics GP 2016 R2; as the most recent versions have been, these posts are in the form of PowerPoint slides; I am reposting them here so they can be read more easily.

The series index for this series of posts is here

The fifth Feature of the Day is Requisition Inquiry Icon:

This Feature of the Day is a fairly simple one. The Purchase Requisition Entry Inquiry window will show a different icon if the purchase order created from the requisition has been updated so the requisition quantity will not be fully updated. The usual chain link icon is replaced with one which has a line striking through it.

The Inside Microsoft Dynamics GP blog has started a series Feature of the Day posts for Microsoft Dynamics GP 2016 R2; as the most recent versions have been, these posts are in the form of PowerPoint slides; I am reposting them here so they can be read more easily.

The series index for this series of posts is here

The fourth Feature of the Day is Batch Edited Message:

This is a simple, but oh so welcome, enhancement to Microsoft Dynamics GP 2016 R2; when a user tries to interact with a batch which is being edited by another user, the message will no longer simply say it is being edited by another user, but will now name the other user who is editing the batch.

No longer will I need to write, or deploy, SmartLists to users allowing them to see who is locking batches (I still might so the administrator can take a global view of their system) to simply see which user is preventing a batch from being posted.