I recently received an error message when trying to integrate some debtors:
Integration Log Integration: Debtors (ID: 1) Action: None Start Time: 09/10/2014 08:49:37 09/10/2014 08:49:37 Source: IIntegrationEngine_Run, Status Code: 0 Opening source query... 09/10/2014 08:49:38 Source: Microsoft.Dynamics.GP.IntegrationManager.IMProvider, Status Code: 33624151 ERROR: Unable to open source queries because Query 'Debtors' is not found in the database. - ADO Field is nothing. Unable to open source queries because Query 'Debtors' is not found in the database. - ADO Field is nothing. ADO Field is nothing. 09/10/2014 08:49:38 Source: FinishIntegration, Status Code: 3 Integration Failed 09/10/2014 08:49:38 Source: FinishIntegration, Status Code: 3 Integration Results 0 documents were read from the source query. 0 documents were attempted: 0 integrated without warnings. 0 integrated with warnings. 0 failed to integrate. Finish Time: 09/10/2014 08:49:38 Source Total: 0 Successfully Integrated: 0 Integrated With Warning: 0 Failed: 0 Completion Status: Incomplete Integration Status: No Documents Succeeded
Validation Messages - Database configuration: The master password could not be validated against the password policy
Since the introduction of the web client in Microsoft Dynamics GP 2013, I have tried to minimise the use of VBA as it is not supported by the web client. However, some clients don’t intend to use the web client and prefer to have a quick customisation to a window done using VBA rather than full development in Dexterity.
As such, I do still sometimes get work with Modifier and VBA. I recently did a change to a client where I added several fields to VBA on the Sales Transaction Entry window.
A little later I needed to add a new checkbox and add it to VBA. I customised the window in Modifier to add the field, but when I tried adding it to VBA I received an error I had not seen before:
Microsoft Dynamics GP
You are manipulating a modified window whose EventMode is set to EmOriginalOnly. You must change this window's EventMode to emModifiedOnly before you can add this field.
I have just recently finished the implementation of a new client on Microsoft Dynamics GP. While I was there during the go-live week, one of the finance team reported a problem whereby they opened the creditor (vendor to the American readers) record the EFT Bank details for a different creditor were displayed.
I immediately started investigating to see if I could find out why this was happening as it is not something I have seen before and was rather concerning.
Ten minutes later while I was still poking around the database, the user came back with further information. When they were originally entering the creditors whey had entered one of them under the wrong creditor ID (they were using the ones from their old system).
After entering the creditor and EFT details they had realised their mistake and deleted the creditor; they then entered the correct details, but this creditor did not have EFT details on record so the EFT details window wasn’t opened at that time.
A few days later, once the creditor supplied details they went to enter them and found the details from the original incorrectly entered creditor and reported the problem. It was only ten minutes later they remembered about the incorrect entry.
I have been able to reproduce this error with 100% success on several versions of Microsoft Dynamics GP. It appears that Dynamics GP is not deleting the creditor bank details when the creditor, or the address, are deleted.
A client recently logged an issue with Management Reporter producing an error when they tried generating a report. As is commonly the case, the error in the Queue Status window wasn’t terribly informative, but we did get a more detailed error when looking in the Windows Event Log:
Microsoft.Dynamics.Performance.DataProvider.Core.RequestException: The source system request did not complete successfully. ---> System.ArgumentOutOfRangeException: The length of the value is invalid. \r\nMinimum supported length: 1 \r\nMaximum supported length: 512
From the error message, we have an item which is the wrong length. I took a shot and guessed that the problem might be down to the budgets as I have seen corruption in client’s systems before which has caused problems with Management Reporter.
One quick select later confirmed that there was a corrupt record in the Budget Master (GL00200) table. I deleted this entry using the below code:
DELETE FROM GL00200 WHERE BUDGETID = ''
After which the client confirmed Management Reporter was able to generate the report successfully.
I recently assisted a client with an upgrade of Microsoft Dynamics GP 10 to GP 2013 R2. As part of the upgrade we assisted the client to create some Word Template versions of sales invoice, purchase order, and cheque remittance (or check remittance to the American readers).
Everything appeared fine during development and initial testing. Fine that is until we tried producing a batch of twenty remittances which produced the following two error messages:
I recently assisted a client with upgrading Microsoft Dynamics GP to 2013 R2; after the upgrade was complete we found that logging in was incredibly slow. It would take over two minutes to log in or change company.
We did a few things such as checking that all external shortcuts were valid, checking on the Quick Links and ensuring SSRS was functioning correctly (including removing Business Anlayzer from the homepage) without effect. After spending a little time investigating I remembered a blog post from the Dynamics GP Support and Services Blog where they discussed this as being a known problem with Dynamics GP 2013 R2.
The problem is caused by the navigation lists being duplicated during the upgrade. The areas you’ll see this is in the following:
- Under the Purchasing area page:
- Purchasing Requisition Transactions
- Purchase Order Transactions
- Under the HR & Payroll area page:
- Historical Timecards
- Current Timecards
A client reported an error to our service desk recently when they were working with an Account Transactions SmartList which they were trying to filter to exclude a particular Account Category. When they entered the search criteria they received a string of error messages.
Microsoft Dynamics GPGPS Error: 58
When you select a batch of checks to print in the Print Payables Checks window GP 2013 R2 shows 2 icons labeled “Print” in the center of the Action Pane. The left icon has a printer with a document behind it that resembles a report. The right icon displays a plain printer. It’s very confusing to users to decided which icon to pick to print checks.
The left most icon, the one with an apparent report behind it actually prints checks. The right icon, the one with a plain printer, prints reports. This is not intuitive at all. Neither the icon nor the label indicate which print icon does which. Since the primary function of this window is to print checks it needs to be very obvious to users what to do.
Please clarify both the icon and label to make this easier to use.
This suggestion can be found here; please take a look and add your vote.
This issue was discussed at some length on the Community Forum with Frank Hamelly supplying a SQL script to update the assets.
With my client I took a slightly different tack and used the Fixed Assets Modifier tool in the Professional Services Tools Library (PSTL). This tool works on a single asset at a time and, unlike some of the other modifiers, does not allow import of a spreadsheet.
However, PSTL is written in Dexterity and allows the use of Dynamics GP Macros; so after doing an extract of all Asset IDs I was able to use mail merge to generate a macro to update all fixed assets containing a hyphen in the Asset ID.
I have checked Microsoft Dynamics GP 2015 and a hyphen is still disallowed in the Asset ID field.