This 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:
Once this is deployed, the PM Transaction Search window will be fully working.
This 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.
This 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:
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.
This 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 (
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.
Steve 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 (
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.
This post is part of a series of posts on implementing Jet Reports and is part of the Jet Enterprise sub-series.
No, the title is not a mistake. When you purchase Jet Enterprise, you also get a licence for Jet Professional. This ensures you get the full reporting capability available from Jet Reports. It also means that as well as following my series on Implementing Jet Enterprise, you should also follow the series on Implementing Jet Professional.
In the last post, on the Jet Enterprise sample reports, I said you could use the reports for both Jet Professional and Jet Enterprise, but forgot to say how. The how is because you have access to Jet Professional if you install it.
This post is part of a series of posts on implementing Jet Reports and is part of the Jet Enterprise sub-series.
As with the other versions of Jet Reports, there are sample reports available from Jet Reports. Back in May I posted about the sample reports for Jet Professional.
The download for Jet Professional and Jet Enterprise is the same one; with jet Enterprise all of the files in the download will be able to be used.
To download the use the reports, follow the instructions in the Jet Professional sample reports post.
I’ve been hosting adverts from Google Adsense for a while and, after my last site redesign, I started using responsive adverts which scale according to the size of the browser window (or device size).
Since then, I’ve had yellow background showing either side of the adverts:
The other day, I finally had time to track down and fix the issue. The html code for the adverts, which is supplied by Google, places the adverts within an ins tag and a class of adsbygoogle (see two highlighted sections):
...<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
<!-- azurecurve Responsive Leaderboard -->>
<ins class="adsbygoogle"
style="display:block"
data-ad-client="{adsense publisher id}"
data-ad-slot="5299901990"
data-ad-format="auto"></ins>
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script>...
The yellow background is the default colour used by WordPress for ins tags; so to remove it, all you need is a snippet of css in your stylesheet:
ins.adsbygoogle {
background: transparent;
}
With the css saved, the yellow background disappears:
Earlier in the year we added a new ERP Support Analyst to our support team and we’ve been doing training to bring him up to speed. While I was doing Integration Manager training, I was giving him some cuationary advice about error messages and tried to reproduce some of the annoying errors I’ve encountered in the past, only to find out that three of them have been fixed without me realising.
The fixes are:
MVP 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 () 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:
The new window is also available from Additional menus on several windows including Vendor Maintenance ()
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.