GP Transaction Search: Installing the SQL Stored Proc for v1.0.0.4

Winthrop DCThis post is part of the series on the new, free, GP Transaction Search window from Steve Endow of Precipio Services.

When running through the installation of the GP Transaction Search the other day, I didn’t cover the deployment of the SQL stored proc.

In the downloaded zip file, there is a SQL script called csspGLTransactionSearch v1.1.sql which needs to bedeployed in each company database:

Windows Explorer

Once this is deployed, the PM Transaction Search window will be fully working.

GP Transaction Search: Configuration of v1.0.0.4

Winthrop DCThis post is part of the series on the new, free, GP Transaction Search window from Steve Endow of Precipio Services.

With GP Transaction Search installed, the next stage is to review the configuration and make any changes necessary.

To review the settings, open the GP.TransactionSearch.dll.config.

There are three settings under the GP.TransactionSearch.Properties.Settings. The only one I would advise changing is the SearchAsYouType one; if you have a small database, leaving this setting set to True is fine, but on larger databases may cause some lag:

One you’ve changed the settings, click Save and close the config file.

GP Transaction Search: Installation of v1.0.0.4

Winthrop DCThis post is part of the series on the new, free, GP Transaction Search window from Steve Endow of Precipio Services.

The installation of the GP Transaction Search window is a nice simple one.

First off, download the addin from the Precopio Services website.

The downloaded file is a zip which contains the four versions currently available:

GP Transaction Search zip

I am installing the Microsoft Dynamics GP 2018 version, so have opened the 2018 folder.

Copy the contents of the folder to the Dynamics GP addins folder which is a subfolder of the installation one (by default this is C:/Program Files (x86)/Microsoft Dynamics/GP2018/).

Depending on your security settings, you may need to Unblock the dlls. To check if this is necessary, right click each one in turn and click on Properties. If there is a checkbox called ,em>Unblock, mark this and click OK to save changes.

GP Transaction Search: Why?

Winthrop DCThis post is part of the series on the new, free, GP Transaction Search window from Steve Endow of Precipio Services.

I’ve been working with Microsoft Dynamics GP for 15 years now and I have always thought that one of the most useless inquiry/enquiry windows in the Purchasing series was the Transaction by Document (Purchasing area page » Enquiry/Inquiry » Transaction by Document) one. It turns out I am not alone in this assessment.

The window allows you to search only by Document Number. In most cases you also want to narrow the selected data down by vendor/creditor, but the window does not allow this.

Well, sharing my view of the window, MVP Steve Endow, of Precipio Services has decided to do something about it. Microsoft Dynamics GP has several options for making customizations, from minor tweaks using VBA (not supported in the web client), to .NET with VS Tools, to Dexterity. This is a huge benefit for GP customers as it allows them to pick the best technology for the customisation they want. There is always a cost to either making your own customisations, or having someone else do the work for you. However, by not making the customisation, you can really miss out on the benefits. This can lead to users who can struggle to quickly or easily find the information they need.

Steve decided to make the GP Transaction Search project as a very usable demonstration that a relatively small customization can produce significant benefits and efficiencies.

This new enquiry/inquiry window allows you to search by a Document Date range and/or the Vendor ID or Name and/or the Document Number and/or a Document Amount. This makes it a far better window for searching for documents than the standard Transaction by Document one. It is also very quick to return data.

The initial version of GP Transaction Search includes only the PM Transaction Search, but took only one day to develop the prototype, and an additional two to three days to finish, refine, test, and release. If you look at the actual .NET code, it’s surprisingly simple; there are actually very few lines of code in the project—it’s mostly basic .NET functionality, albeit, admittedly, with some clever construction and design and tricks to work with Dynamics GP.

As this shows, it doesn’t require a huge investment to produce really valuable customizations and, as I’ll show over the next few posts, deployment and updates are simple and low maintenance. This aligns with Steve’s view that customizations, when well designed, don’t have to be a burden for customers.

As well as being immediately useful to people using Dynamics GP, Steve has released the project as an open source project; this means that it can be a great learning tool and reference for other developers looking to use .NET with GP. As mentioned the initial project includes a replacement to the Transaction by Document enquiry/inquiry, it can easily be expanded to display any data from any module in Dynamics GP and, potentially, from any other database.

Since the project is quite literally just a simple window with a grid displaying the results of a stored procedure. It can easily be expanded to display any data in Dynamics GP, from any module (such as Receivables Management, Inventory Control, Fixed Asset Management), or in any other application database, for that matter.

The GP Transaction Search window is available for all version of Microsoft Dynamics GP starting with 2013. You can download the install files from Precipio Services; if you’re a developer, the GitHub project is here.

GP Transaction Search: Series Index

Winthrop DCSteve Endow of Precipio Services has recently launched a GP Transaction Search. The initial version is a PM Transaction Search which replaces the Transaction by Document window (Purchasing » Inquiry » Trx by Document) in the Purchasing series.

Over the next few posts, I’m going to be taking a look at the origins, installation, configuration, use and future of this add-on.

Dynamics GP Transaction Search v1.0 is Available! For FREE!

Microsoft Dynamics GPMVP Steve Endow, on the Dynamics GP Land blog, has announced the release of a new Dynamics GP Transaction Search window for all versions of Microsoft Dynamics GP from version 2013 onwards.

The intention of the new window is that it replaces the Transaction by Document (Purchasing >> Enquiry >> Transaction by Document) window; the default version can be very slow and only allows you to search by one criteria (Document Number).

In contrast, Steve’s new PM Transaction Search window allows you to search on a date range, Vendor ID, Vendor Name, Document Number and range of values, all at the same time:

PM Transaction Search

The new window is also available from Additional menus on several windows including Vendor Maintenance (Purchasing >> Enquiry >> Vendor)

The initial release includes the PM Transaction Search, but Steve has intentions that more search windows are added to other modules and series in Dynamics GP.

Best of all, this new search is absolutely free.

Steve also plans to open source the window so that other people in the Dynamics GP community can contribute.

The Precipio Services website will be updated, but, until then, you can download it from Steve’s blog.

Sample SQL Views for SmartLists (by Jen Kuntz)

Microsoft Dynamics GPI occasionally link to blog posts that other people have done and todays post is one of these.

Jen Kuntz is running a TIP Tuesday series of posts at the moment and her tip this week is looking at a set of SQL views from Microsoft (originally posted by Isaac Olson).

As Jen points out, while Microsoft bill these as for use with SmartList Designer, they will work with SmartList Builder or any other reporting tool (Excel Reports, Reporting Services Reports and so on).

To make use of these SQL views, you do need to have a CustomerSource login to download them and knowledge of creating views and granting permissions.

My addition to this would be a reminder that there are lots of other resources available from the wider community which can be freely amended and used in reporting, such as from Victoria Yudin.

You can read Jen’s full post here.

I try to keep up-to-date with blog posts about Dynamics GP, but the post from Isaac apparently went by without me seeing it, so it was good to get a second chance at reading about it from Jen.

** updated due to wrong name

MS Connect Suggestion: Include Multicurrency Vouchers in Select Checks Window

Microsoft Dynamics GPThis suggestion is one from MVP Mariano Gomez to improve the payment run process by allowing multicurrency invoices to be included.

Currently, the payment selection process only allows vouchers issued in the batch currency to be selected and added to the check run. If the user wants to add foreign currency vouchers, he/she needs to use the Edit Checks window to add such vouchers. It would be nice to be able to have an option to include functional currency vouchers in the case of a foreign currency batch, or foreign currency vouchers in the case of a functional currency batch.

This is the use case:

Vendor A Invoice 1 CA$10.00
Vendor A Invoice 2 US$20.00
Vendor A Invoice 3 US$30.00

If a payment selection is performed and the batch currency is CA$, only the first voucher will be selected. To add Invoice 2 and 3, you would have to use the Edit Checks window to include both vouchers.

Conversely, if the batch currency is US$ and the payment selection for vendor A is performed, only invoices 2 and 3 would be selected and you would have to use the Edit Checks window to include Invoice 1.

What Mariano would like to see is all invoices selected (based on selection rules) and let the user deal with the exceptions, as it should be.

As mentioned, all the logic is already there via the Edit Checks window and it would be nice to incorporate as part of the payment selection process. As others have mentioned, having multicurrency vouchers included could be a payables configuration item or simply an additional option in the Select Payments (Select Checks) window.

Mark Polino has also suggested that this functionality be optioned with Rod O’Connor further suggesting the option be on the Select Checks window itself to allow maximum flexibility. Both of these seem like a good addition to Mariano’s idea.

The suggestion can be voted on here.

Does Project Green Dynamics 365 Mean The Death Of Dynamics GP?

Microsoft Dynamics GPNewly anointed MVP Jen Kuntz, of Kuntz Consulting Inc. has a new blog post up where she discusses what the launch of Dynamics 365 means for Microsoft Dynamics GP and the rumours which have been springing up.

Unfortunately, some of these rumours seem to be coming from Microsoft partners themselves.

I was at the reIMAGINE Dynamics GP partner conference earlier this year, where Errol Schoenfish, the Director of Product Marketing at Microsoft, reiterated, and got us to stand up and repeat along with him that “Microsoft Dynamics GP is going nowhere.

Microsoft then displayed a slide showing the continuing development of Dynamics GP (and NAV and AX and SL alongside Dynamics 365):

RoadmapMicrosoft Dynamics GP roadmap

That was followed up more recently with a roadmap for Dynamics GP with the release of 2016 R2 at the start of December this year and GP 2018 at the start of December next year, with GP “NExt” following a year later:

RoadmapMicrosoft Dynamics GP roadmap

My reference to Project Green in the post title, was slightly tongue in cheek. Back in 2008, a merger of the Dynamics ERP was looked into briefly be Microsoft, before being discarded. That was Project Green.

It still comes up in conversations now; last year we had a prospect in who mentioned a competitor selling another ERP mentioning that GP would be merged with NAV. He stopped at that point when he saw my huge roll eyes, and confirmed it as Project Green when I asked. I then explained what it was and when it ended.

That’s the problem with rumours. When they start they can be difficult to stop. The message on Dynamics 365 from Microsoft hasn’t been great and needs to improve.