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.
There are some feature of the days which I look at and think “so what?”. And then there are others I look at and know they are going to be very popular.
This feature is very much one of the latter (I have one client who would be willing to upgrade to just top get this one feature). It is the ability to have Cash Receipts automatically posted in Bank Reconciliation:.
The main features of are:
- When Automatically Post Cash Deposits is marked and you post a batch with cash receipts in it, one deposit will be created for all cash receipts in the batch.
- If you transaction level post, each transaction will create a separate deposit.
There is one downside to this feature; if you want your deposits to show as individual deposits in bank you have to post them separately in Receivables Management. Doing one transaction per batch (transaction level posting would result in manual posting being required of the resulting GL batches) will not be as time consuming as doing all of the deposits manually, but is moving an element of the work from one part of Dynamics GP to another (and possibly from one team to another).
The client I references at the start of this post runs a number of visitor centres so will have a lot of cash receipt transactions being imported into the system, but the majority of them would hit the bank as a single deposit. I’m onsite with them soon to help integrate their new EPOS system into GP so can work with them to make sure transactions are brought into Dynamics GP in the way necessary for them to benefit most from this feature.
Microsoft Dynamics GP 2013 R2 saw the introduction of the Workflow 2.0 (which was the subject of myfourth book. Workflow 2.0 was enhanced further in both Microsoft Dynamics 2015 R1 and R2, and is again being improved in Dynamics GP 2016 R1.
This time, the enhancement is a twofold one. Firstly, the Batch Edit lists have a default Word Template and, secondly, this can be emailed to the workflow approver:
The main features of are:
- Workflow Batch Approvals now have a default Word Template for the following edit lists:
- Gneeral Ledger Batches
- Payables Batches
- Receivables Batches
- Can be emailed to approver for complete information before approving
I think this feature will prove to be popular with those clietn using Workflow approvals as an approver will always want s much information before approving as possible. This will likely be of great interest when Workflow approvals are being used.
MDGP 2016 R1 Feature of the Day: Budget Import Exception Report
This feature of the day is the production of an exception report during the Budget import. This is going to be a very popular one:
The main features of are:
- When importing a budget from Excel, an exception report will print displaying accounts that aren’t setup in Dynamics GP
The Budget Wizard is a good tool, but it has always been problematic to identify accounts on the budget upload which didn’t exist. This new feature will make importing budgets far easier now any missing accounts are highlighted.
I have a couple of customers who might be tempted to upgrade just to get this one feature (including one who just upgrade to Dynamics GP 2015 R2.
Microsoft Dynamics GP
Error Registering Table GL_Account_MSTR
We are currently in the process of upgrading a large 20 site client from Microsoft Dynamics GP 9 to a later version (unfortunately not 2015 due to third party add-ons which are not supported on this version). The client previously had standalone implementations at each site, but we are aggregating them into one implementation for ease of maintenance and also to reduce licensing costs.
The first few we centralised went fine, but we then ran into problems when we did the head office companies. When they ran the GL Summary TB on the old and new systems there was a mismatch between them.
After investigating, the support team established that the problem was down to some corruption in the Account Index Master table (GL00105) where some of the accounts had segments separated with dots instead of dashes as defined in Account Format Setup ().
The solution they followed was fairly simple, and in three steps:
- Run a script to clear the Account Index Master table:
DELETE FROM GL00105
- Run Check Links ( ) on Account Master.
- Run the General Ledger Reconcile utility ( ) on all years starting with the oldest and working forward.
After this was done, the report produced from the upgraded system matched the old one.
We recently upgraded a client with well over a hundred companies from Microsoft Dynamics GP 10 to GP 2015; one of the new pieces of functionality they wanted to start using was the Budget Transactions.
One problem is that the keep history checkbox for Budget Transactions in General Ledger Setup () is unmarked.
Enabling it for this many companies was going to take a substantial amount of time (even if we generated a macro to do this in automatically) as the client has over 120 companies in Dynamics GP. It is a simple setting in one table which needs to be updated, so instead of using a macro I created a SQL script containing a cursor to loop through all of the databases attached to the system database and enable this setting.
As with all scripts which change data, please make sure you have a good backup of your database (or in this case all of your company databases) before running the script.
DECLARE @IntercompanyID VARCHAR(5) DECLARE @SQLStatement AS VARCHAR(2000) DECLARE cursor_InterID CURSOR FOR SELECT INTERID FROM DYNAMICS..SY01500 INNER JOIN master..sysdatabases ON name = INTERID OPEN cursor_InterID FETCH NEXT FROM cursor_InterID INTO @IntercompanyID WHILE (@@FETCH_STATUS <> -1) BEGIN IF (@@FETCH_STATUS <> -2) SET @SQLStatement = 'UPDATE ' + @IntercompanyID + '..GL40000 SET KPBUDTRXHIST = 1 WHERE KPBUDTRXHIST = 0' EXEC (@SQLStatement) FETCH NEXT FROM cursor_InterID INTO @IntercompanyID END CLOSE cursor_InterID DEALLOCATE cursor_InterID
You will need to amend the script if your System Database is not called DYNAMICS.
Microsoft Dynamics GP 2015 R2 has been released and, as with previous releases, Microsoft have started a Feature of the Day series on the Inside Microsoft Dynamics GP Team blog. As I have done with the last three series, I’ll be reposting these blog posts here with a little commentary.
The twenty second Feature of the Day is . A top suggestion on the MS Connect site, this feature moves the Debit column to display before the Credit column by default in account transaction reporting options in which the Credit column previously displayed before the Debit column.
This applies to SmartLists and Excel Reports, as well as the database tables and views on which the reports are based.
Dynamics GP includes a variety of tools and modules to assist in controlling processes and data; one of the major modules for this was the Dynamics Workflow module. However, this module had major flaws which very much limited its usefulness; it was slow, clunky and difficult to install, configure and maintain.
Microsoft Dynamics GP 2015 R2 will soon be released (due late May/early June and, as with previous releases, Microsoft have started a Feature of the Day series on the Inside Microsoft Dynamics GP Team blog. As I have done with the last three series, I’ll be reposting these blog posts here with a little commentary.
The ninth Feature of the Day is Combined General Ledger Inquiry.
In Microsoft Dynamics GP 2015 R2 in General Ledger, the inquiry windows have been consolidated. Now, you can view open and historical information in the same window for Summary Inquiry, Detail Inquiry and for Account Summary.
Any GoTos or drill backs will now go to the single window instead of the user picking open or history.
This particular feature is well overdue. It always feels a little embarrassing when doing user training for a new client and having to show them separate enquiry windows for open and history years.