I’m currently doing some work for a client where we’re modifying some of the reports in Microsoft Dynamics GP and I’m trying to avoid using Report Writer as a) I don’t like it, b) Word template reports look better and c) I don’t want to spend time training a client on a module which can be avoiding and is being retired in the near future.
For some of the reports such as the Sales Orders and Invoices and the Purchase Order reports, there are Word templates already available for customising, but for some of the reports such as the Sales Picking Ticket or Dispatch Notes there are no Word templates available by default.
In Microsoft Dynamics GP 2010 this meant starting a template from scratch. In Microsoft Dynamics GP 2010 R2 you can use the Word Template Generator to convert a saved xml report into a Word template.
The only problem is, I can’t find it. None of the blog posts I read announcing the feature said where it would be; just that it would be available with 2010 R2. My first port of call was within GP itself. The I tried the installation media but no luck. I then tried a couple of Internet searches and came up dry. I asked a colleague but they hadn’t used it before.
I finally searched on PartnerSource (I don’t like the PartnerSource search so usually try general Internet searches first) and finally found the download link for the Word template Generator.
During a recent implementation I was using Integration Manager to load data into GP and on one occasion I got the following message in the progress window;
Continue reading “Integration Manager Error – ADO Field Is Nothing”
I’ve recently been doing some work for a client where we’ve upgraded them from Microsoft Dynamics GP 10 to 2010 R2. Alongside this, we also migrated them from FRx to Management Reporter.
All looked fine after the upgrade until I opened one of the rows for editing and got the following warning message;
Continue reading “Missing Font Causes Crash In Management Reporter”
If you’re using the Financial Statements ( ) in Microsoft Dynamics GP you may see a messagesililar to the following after doing a year end;
Continue reading “Changing Open-Year In Financial Statement Reports”
I am in the process of implementing Microsoft Dynamics GP for a new client and am currently testing the static data integrations (chart of accounts, suppliers, customers, stock and so on) using Integration Manager.
I’d successfully run an integration of the chart of accounts which threw out a couple of warnings. After amending the file I realised that GP was no longer showing in the task bar and assumed that I had accidentally closed it. I restarted it and logged into the test company and tried to run the COA integration again and got the following error message;
Continue reading “Integration Manager Error – You Must Close All Microsoft Dynamics GP Windows”
As I mentioned in a previous post, I’ve been taking a look at the Visual Studio Tools for Microsoft Dynamics GP. I started creating a form to store some additional details against a Creditor but wanted the form available in a similar way to the Creditor Addresses; available from both the Creditor form and from the Cards menu.
Getting the form to display a menu option on the Additional tab of the Creditor window was easy enough but I had trouble finding out how to make it display on the Cards menu.
After struggling with it for a while, I remembered reading a discussion between Mariano Gomez and David Musgrave about long module names and how Visual Studio Tools for Microsoft Dynamics GP 2010 wasn’t the longest but instead Menus for Visual Studio Tools for Microsoft Dynamics GP 2010 was the longest.
A quick search found the module, in the very obvious location, of David Musgrave’s Developing for Dynamics GP blog; Menus for Visual Studio Tools Build 9 Released which can be downloaded from either PartnerSource (login required) or CustomerSource (login required).
The module comes with full instructions on how to install and use it.
Last week Mariano Gomez posted details of the roadmap for Microsoft Dynamics GP through to GP “15” which were announced by Microsoft at the GPUGSummit 2011 in Las Vegas, Nevada;
Back in the early years of my career, before I became involved with Microsoft Dynamics GP, I was a trainee developer (admittedly on PICK Databasic) before moving on and learning a little VB6 and then into Microsoft Dynamics GP consultancy.
I’ve kept my hand in enough that I can still do some coding and last weekend, after chatting with a developer in the office who is creating some new screens for GP, I decided to have a little dabble with the Visual Studio Tools for Microsoft Dynamics GP myself. Continue reading “Error During Build in Visual Studio Tools For Microsoft Dynamics GP”
Well, after assuming it was a bad idea to rely on DEX_ROW_ID never changing, it is now officially a bad idea; David Musgrave has spoken on the Developing for Dynamics GP blog.
As David explains, DEX_ROW_ID was added when support for SQL Server was added to Microsoft Dynamics GP but is not guaranteed to always remain the same. For example, a change to the table structure during an upgrade could result in the DEX_ROW_ID changing. As it isn’t a fixed value, it should never by relied upon in customisations, integrations or custom code.
Like some other posts recently, this one is the result of a conversation with a colleague at my new company, where I found they were unaware of something I took for granted; the ability to easily rename a comuter which has a stand alone instance of SQL Server installed.
I do this fairly often as I use quite a lot of Virtual Machines for testing different configurations, but I don’t want to have to build a new one every time, so I make copies of a base VM and rename it each time I want a new one (there is often more than one running at any one time and I want to avoid conflicts).
As well as renaming the machine inside the VM, I also rename the SQL Server to make sure it matches the name of the machine; I’ve had problems before with Microsoft Dynamics GP when I’ve not done so.
Doing this is actually very simple. Continue reading “How To Rename A SQL Server”