Create SmartConnect Journal – Standard Map: Prerequisites

eOne SolutionsThis post is part of a series on creating a Journal – Standard integration using SmartConnect from eOne Solutions; I recently posted a series on Implementing SmartConnect.

The prerequisites for creating a new integration map are quite straight forward:

    Decide on the type of integration to be created.
  • Decide how the integration should work.
  • Create the source data template.

The integration I am creating as part of this series is one of the easiest which can be created; it is a standard General journal integration. I always create this map after implementing SmartConnect (and before starting to use SmartConnect, Integration Manager) as it is a quick and easy one to create and which will be useful to all clients.

The most useful way of creating this integration for clients, is to create an integration which polls a folder every few minutes on a schedule and which reads data from an Excel spreadsheet. This approach allows one integration to be set up and usuable by all users; as it is a folder being polled, the files dropped into the folder can have any name and, as long as the format matches the template, SmartConnect will attempt to integrate the data.

In the past when using Integration Manager, the source file would be a CSV or TXT file as Integration Manager couldn’t easily handle Excel spreadsheets; SmartConnect has no such limitation, so I am going to use the Excel version of the Integration Manager template:

Excel spreadsheet source with BatchID, TrxDate, Reference, Account, Debit, Credit and DistRef columns

With the above decided and in place, the next post, in this series, will start to cover the creation of the integration map in SmartConnect.

Create SmartConnect Journal – Standard Map: Series Index

eOne SolutionsI recently did a series on Implementing SmartConnect, from eOne Solutions; in this series I am going to create a simple integration map to show how SmartConnect can be used to integrate standard journals into Microsoft Dynamics GP from a predefined folder.

The series index below will update as each post in the series goes live (unless you’re reading a syndicated version of this post in which case check back to the original post).

Create SmartConnect Journal – Standard Map

Hands On With Microsoft Dynamics GP 2018 R2 New Features: Skip Displaying New POs When Generating a PO

Microsoft Dynamics GPThis 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.

This hands on new feature is, as far as I am aware, an unannounced one which I stumbled across when testing the partial purchase a purchase requisition new feature. When you click the Generate button on the Purchase Order Preview from Purchase Requisition Entry window, a prompt Skip displaying the new purchase orders? will be displayed:

Microsoft Dynamics GP - Skip displaying the new purchase orders?

This is a change of behaviour from the new functionality introduced in Microsoft Dynamics GP 2018 RTM; the purpose of this original new feature was to improve visibility of the created purchase orders.

This was, and remains, a laudable goal, but unfortunately the implementation was somewhat lacking. The new purchase orders were displayed by opening a navigation list, which could be ver slow to open (especially if the Reporting Services Reports had been deployed and the fact pane visible.

The 2018 R2 new feature, to hide Business Analyser for all users would go some way to mitigate this issue, by hiding the fact pane, but this new feature of prompting the user to decide if they want to see the navigation list will go the majority of the remaining way (a global option to disable would have gone all the way).

Click to show/hide the Hands On With Microsoft Dynamics GP 2018 R2 New Features Series Index

Hands On With Microsoft Dynamics GP 2018 R2 New Features: Purchase Requisition Partial Purchase

Microsoft Dynamics GPThis 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-second new feature is Purchase Requisition Partial Purchase. You’ve always been able to increase the quatity to purchase, but you were not able to reduce the quantity. This new feature, allows a smaller quantity to purchase to be specified in order to partial purchase the requisition; the remaining quantity will be cancelled:

Microsoft Dynamics GP - The remaining quantity ordered will be cancelled.

The flexibility this offers should be a good thing, but I have concerns around users being able to change the purchasing quantity here if an approval workflow is being used. That said, I already had these concerns about users being able to increase the quantity post approval.

Click to show/hide the Hands On With Microsoft Dynamics GP 2018 R2 New Features Series Index

Hands On With Microsoft Dynamics GP 2018 R2 New Features: Checkbook ID Defaults on Check Batch

Microsoft Dynamics GPThis 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 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:

Payables Batch Entry

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.

Click to show/hide the Hands On With Microsoft Dynamics GP 2018 R2 New Features Series Index

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

Microsoft Dynamics GPThis 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 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
Checkbook  Maintenance

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

Hands On With Microsoft Dynamics GP 2018 R2 New Features: Transaction Level Post Through General Ledger

Microsoft Dynamics GPThis 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 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:

Posting Setup

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.

Click to show/hide the Hands On With Microsoft Dynamics GP 2018 R2 New Features Series Index

Hands On With Microsoft Dynamics GP 2018 R2 New Features: Print Invoices in Functional Currency from SOP Navigation List

Microsoft Dynamics GPThis 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 sixth new feature is Print Invoices in Functional Currency from SOP Navigation List. This feature of the day is one I requested back in 2014 on behalf of a client; it is the ability to print an invoice in Functional, by changing the Currency to Print drop-down, from the navigation:

Sales Transactions navigation list

Continue reading “Hands On With Microsoft Dynamics GP 2018 R2 New Features: Print Invoices in Functional Currency from SOP Navigation List”

Hands On With Microsoft Dynamics GP 2018 R2 New Features: Print and E-mail Sales Order Processing Documents

Microsoft Dynamics GPThis 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 fifth new feature is Print and E-mail Sales Order Processing Documents. This feature changes the printing behaviour of the Sales Document Print Options window, accessible via Sales Transaction Entry (Sales area page » Transactions » Sales Transaction Entry) to both print and email the sales document:

Sales Document Print Options

When it was announced, I wondered if, in some way, this was related to the print remaining documents functionality, but I tested with 2018 RTM and that was how that version worked. This new feature goes against the 2013 R2 feature in that selecting both boxes will then both print and email the sales document.

I’m not sure what the use case for this feature is. If you have an email address, you’d want to email the document, otherwise you would want to print it. This is exactly what the previous versions would do.

Click to show/hide the Hands On With Microsoft Dynamics GP 2018 R2 New Features Series Index

Hands On With Microsoft Dynamics GP 2018 R2 New Features: Display Vendor Hold Status

Microsoft Dynamics GPThis 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 third new feature is Display Vendor Hold Status. This makes the vendor hold status more visible to users both by displaying an icon, but also by confirming with the user that the want to proceed with entering a transaction.

The red hold icon will display next to the Vendor ID field in the following windows:

  • Vendor Inquiry
  • Transactions by Vendor
  • Purchasing All-in-One View
  • Payables Transaction Entry Zoom
  • Purchase Order Entry
  • Receivings Transaction Entry
  • Enter/Match Invoice

When the user enters a transaction and the creditor is on hold, they will be prompted as to whether they want to proceed:

Vendor XXXX is currently on hold. Do you want to continue?

Continue reading “Hands On With Microsoft Dynamics GP 2018 R2 New Features: Display Vendor Hold Status”