Each time we have brought someone new into the ERP Practice at Perfect Image I have challenged them to write a blog about what they learn, and what they already know. I’ve not had any takers until now, but Jamie Harris, who was promoted to my team from the service desk in July last year, has taken up the gauntlet.
His blog, Get Interfaced, has been live for a while now and he is managing a few posts each month. Because he works for me and does a similar role, his blog will likely cover a lot of the same areas as I do, but he will cover them in different ways because we do have different backgrounds.
I started as a software developer and moved into support and then consultancy; Jamie worked for in support and then moved into consultancy (we both did other jobs before moving into IT, but as with most people Jamie had a more diverse set of jobs than I).
New additions to the list of Dynamics GP bloggers are always welcome, especially when they’re one of my team.
However, Mark and I were able to proceed a tad ahead of schedule, meaning the Cookbook is now slated for release in August:
That’s right; scheduled for release this month. Five months ahead of schedule. Don’t worry though, the quality is as high, if not higher, than previous versions as this book is a genuine collaboration between Mark and I. By splitting the work in this way, we were each able to focus on particular areas in which we had strengths.
We also received good feedback, to guide improvements, from fellow MVPS Leslie Vail and Jivtesh Singh.
You can pre-order the book from Packt Publishing, and very soon your pre-orders will be shipped. From what I gather the book should be available to order, as opposed to pre-order, in the next week or so, so you won’t need to wait long to receive your copy.
To remedy this, Terry Heley on the Dynamics GP Support and Services Blog has shared some macros, for Dynamics GP 2016, which add sample data into the Fabrikam sample data.
The new sample data focuses on a few modules:
- Advanced Human Resources
- Analytical Accounting
- Workflow for HRP
- Project Accounting Time and Expense
- PTO Manager
- Employee Self Service
Terry points out that this is a run at your own risk macro built on GP 2016, although it would probably be usable on Dynamics GP 2015 as well.
There are instruction documents with each macro as macros can crash based on the menu bar selected in user Preferences.
Also note that there is no support for these macros so no cases can be logged if issues are found.
The download link is available at the end of the post.
Pam Misialek did a post at the end of last month about the type of content content although exact details of sessions aren’t available yet.
She followed up a few days ago with a post pointing out, despite what many appear to think, that reIMAGINE is not the same as Amplify.
Amplify is a customer orientated conference, whereas reIMAGINE is aimed at partners and will therefore have content aimed at partners.
Key points from Pam’s post are:
- The new US Sales team dedicated to helping partners sell more GP will be at reIMAGINE. They are not order takers. They were strategically hired to help partners sell more.
- We will talk about the future of Dynamics GP with an updated roadmap.
- The consultant track has more advanced sessions that go into troubleshooting.
- The developer track will have new content plus content on PowerApps and PowerFlow.
One final point about this reIMAGINE, is that it will be the first Microsoft conference to which I have been. I don’t know if this will be a selling point to anyone, but it’ll be nice to meet the people I have been talking to online over the last few years.
You can book your place at the reIMAGINE home page.
While implementing Microsoft Dynamics GP for a new client a while ago, we used Integration Manager to import over 100,000 Inventory items and then a SQL script to insert the 80,000 bill of materials (BOMs).
This worked well, in that it got all of the information loaded, but found that if we inserted the BOMs in this way, they could not be viewed in the BOM Inquiry window.
I used a SQL query to change the status from Active to Pending and then looked at the best way of changing them to Active through the Dynamics GP.
The only way to bulk change the data was by using a GP Macro; the usual way we do this is to do an extract of the data and then mailmerge this into a prerecorded macro in Microsoft Excel.
However, this can be avoided, by using the SQL select to not only get the data, but to output the macro at the same time:
/* Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (http://www.azurecurve.co.uk) This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 2.0 UK: England & Wales (CC BY-NC-SA 2.0 UK). */ SELECT DISTINCT '# DEXVERSION=11.00.0364.000 2 2 CheckActiveWin dictionary ''default'' form bmBillMaintenance window bmBillMaintenance TypeTo field ''Item Number'' , ''' + RTRIM(BMH.ITEMNMBR) + ''' MoveTo field ''Bill Status'' item 0 ClickHit field ''Bill Status'' item 2 # ''Pending'' MoveTo field ''Expansion Button 1'' ClickHit field ''Expansion Button 1'' NewActiveWin dictionary ''default'' form bmBillMaintenance window ChangeStatus ClickHit field ''Bill Status'' item 1 # ''Active'' MoveTo field ''Process Button P'' ClickHit field ''Process Button P'' NewActiveWin dictionary ''default'' form bmBillMaintenance window bmBillMaintenance MoveTo field ''Save Button'' ClickHit field ''Save Button'' ' FROM BM00101 AS BMH INNER JOIN BM00111 AS BMC ON BMC.ITEMNMBR = BMH.ITEMNMBR WHERE BMH.Bill_Status = 2
I needed to make sure that SSMS was configured to return the data into text and that the data returned was more than the default 256 characters.
Once you have the returned macros, save the file, open Bill of Materials Maintenance and then run the macro.
The problem reported, was the same as the problem always is; the budget template was not in the correct format.
The first image is the header of the one they were trying to import and the second is the Master budget I exported from GP to show them:
As you can see the former budget template has an extra row in the header; this is sufficient to stop the import working.
Everytime we have had this error reported we have found that something was changed in the budget template: a new header row, a header row being deleted, a column being added (the latter is the most common.
The client removed the extra row and was then able to import the budget.
This particular integration is an Account one, which has been extended with VB Script which checks to see if the segments exist, and if not, it inserts them. When a user tried to run the integration, they get the following error:
Opening source query... Establishing source record count... Beginning integration... DOC 1 ERROR: System.Data.SqlClient.SqlError: Cannot open database "GPLIV" requested by the login. The login failed. DOC 2 ERROR: System.Data.SqlClient.SqlError: Cannot open database "GPLIV" requested by the login. The login failed. DOC 3 ERROR: System.Data.SqlClient.SqlError: Cannot open database "GPLIV" requested by the login. The login failed. Integration Failed Integration Results 3 documents were read from the source query. 3 documents were attempted: 0 integrated without warnings. 0 integrated with warnings. 3 failed to integrate.
I did some double checking and it turned out that the user who was doing the testing had two Domain accounts (one with full name and one with initial and surname) and were not using the one I had configured originally.
All of the other users I had worked with had been using Domain accounts of initial and surname, which was the one I had configured, but this particular user was using the account with their full name.
Adding this Domain user account to the database with the DYNGRP role resolved the problem.
/* Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (http://www.azurecurve.co.uk) This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0 Int). */ Set objShell = CreateObject("WScript.Shell") Set objExec = objShell.Exec("B:\IM.bat")
I’m posting it here so I don’t lose it for when I remember why I write it, and perhaps it may be useful to others.
We have been doing a number of upgrades for clients recently, the majority of which went fine. However, we did have one, being done by one of my team, where there was an error produced on the table List View Action Pane when upgrading to Microsoft Dynamics GP 2015 R2:
We have a client who will be loading payables transactions into Microsoft Dynamics GP and need secondary postings created into the General Ledgers of other company databases. The idea is to use the AfterDocument script to create and submit an eConnect document, which is in XML format.
The below code is a small proof of concept which creates an XML file with child and parent nodes and saves it to the T:\:
/* Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (http://www.azurecurve.co.uk) This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 2.0 UK: England & Wales (CC BY-NC-SA 2.0 UK). */ Set xmlDoc = CreateObject("Microsoft.XMLDOM") Set objRoot = xmlDoc.createElement("RootElement") xmlDoc.appendChild objRoot Set objRecord = xmlDoc.createElement("SubLevel1") objRoot.appendChild objRecord Set objName = xmlDoc.createElement("Element1") objName.Text = "AAAAAAA" objRecord.appendChild objName Set objDate = xmlDoc.createElement("Element2") objDate.Text = "BBBBBBB" objRecord.appendChild objDate Set objIntro = xmlDoc.createProcessingInstruction ("xml","version='1.0'") xmlDoc.insertBefore objIntro,xmlDoc.childNodes(0) xmlDoc.Save "T:\Test.xml"