Microsoft Dynamics GP 2015 R2 will soon be released (due late May/early June and, as with previous releases, Microsoft have started a Feature of the Day series on the Inside Microsoft Dynamics GP Team blog. As I have done with the last three series, I’ll be reposting these blog posts here with a little commentary.

The fourteenth Feature of the Day is SmartList Designer View Workflow Type.

Within SmartList Designer a user can send a SmartList through workflow to create a SQL view based on the SmartList query. One active workflow will need to be setup in order for the SQL view to go through the approval process. SmartList workflows will be setup under the Administration series within the Workflow Maintenance window.

I’m interested in seeing this one in practice, but I am sceptical of the utility as there are not that many clients with technical users who would be able to do this type of thing who would also not be part of the IT Department with the ability and permissions just to create a view for SmartList.

Microsoft Dynamics GP 2015 R2 will soon be released (due late May/early June and, as with previous releases, Microsoft have started a Feature of the Day series on the Inside Microsoft Dynamics GP Team blog. As I have done with the last three series, I’ll be reposting these blog posts here with a little commentary.

The thirteenth Feature of the Day is SmartList Designer Create View .

Within SmartList Designer a user can send a SmartList through workflow to create a SQL view based on the SmartList query.

This SQL view can then be used outside of GP for such purposes as creating reports using SQL reporting services or Power BI reports in Excel.

The view will also allow the user to publish the SmartList as a refreshable excel report from inside of Dynamics GP.

Microsoft Dynamics GP 2015 R2 will soon be released (due late May/early June and, as with previous releases, Microsoft have started a Feature of the Day series on the Inside Microsoft Dynamics GP Team blog. As I have done with the last three series, I’ll be reposting these blog posts here with a little commentary.

The twelfth Feature of the Day is Self Service User Tasks and Roles.

In the Microsoft Dynamics GP 2015 R2 release a Self Service user type was added; this user type will enable users that only require very limited access to the system a less expensive option to perform tasks such as entering payroll time, entering project time and expenses, or creating a requisition.

This feature also includes Employee Self Service Security Roles and the ability to filter on security tasks available for each user type, which will make the task and role assignment more efficient.

Nice to see that the new user type is also getting some easing of the setup of the roles and tasks. This is one area that, despite the default roles and tasks available, seems to daunt a lot of new users to the system.

Microsoft Dynamics GP 2015 R2 will soon be released (due late May/early June and, as with previous releases, Microsoft have started a Feature of the Day series on the Inside Microsoft Dynamics GP Team blog. As I have done with the last three series, I’ll be reposting these blog posts here with a little commentary.

The eleventh Feature of the Day is Self Service User Type.

Microsoft Dynamics GP 2015 R2 sees a Self Service user type added.

This user type will enable users that only require very limited access to the system a less expensive option to perform tasks such as entering payroll time, entering project time and expenses, or creating a requisition.

This new user type is going to be a really useful addition. I have one client who has been looking for a POP add-on to allow online creation of orders for more than 400 users and all the old options were looking quite pricey.

This Self Service user type used in conjunction with the web client should give them the functionality they want, at a price point they can accept.

Microsoft Dynamics GP 2015 R2 will soon be released (due late May/early June and, as with previous releases, Microsoft have started a Feature of the Day series on the Inside Microsoft Dynamics GP Team blog. As I have done with the last three series, I’ll be reposting these blog posts here with a little commentary.

The tenth Feature of the Day is Workflow — Document Attachment.

When a document has been added to a transaction or record using the Microsoft Dynamics GP Document Attachment feature, these attachments can now be sent with the workflow task notification email.

This feature is available for PM Batch Approval, Purchase Order Approval, Purchase Requisition Approval, Vendor Maintenance, and the new workflow type, Payables Transaction Approval.

For example, you can now enter a payables invoice, scan in and attach the record from the vendor, then submit the invoice for approval. When the approver receives the email, they will get the invoice information and the attachment will show the scanned invoice from the vendor.

For a few of our clients this is the missing piece of the Workflow puzzle. An email action from Workflow can contain the detail lines of an order, but a few clients have been asking to be able to include the attachments, especially for invoices and quotes attached to POs, for the manager or budget holder to review before approving.

Microsoft Dynamics GP 2015 R2 will soon be released (due late May/early June and, as with previous releases, Microsoft have started a Feature of the Day series on the Inside Microsoft Dynamics GP Team blog. As I have done with the last three series, I’ll be reposting these blog posts here with a little commentary.

The ninth Feature of the Day is Combined General Ledger Inquiry.

In Microsoft Dynamics GP 2015 R2 in General Ledger, the inquiry windows have been consolidated. Now, you can view open and historical information in the same window for Summary Inquiry, Detail Inquiry and for Account Summary.

Any GoTos or drill backs will now go to the single window instead of the user picking open or history.

This particular feature is well overdue. It always feels a little embarrassing when doing user training for a new client and having to show them separate enquiry windows for open and history years.