Microsoft Dynamics GP

Troubleshooting Dexterity Issues – “function trigger registration failed” messages

Posted by dynamicsnick on May 04, 2015
Dexterity, Microsoft Dynamics GP / Comments Off on Troubleshooting Dexterity Issues – “function trigger registration failed” messages

So I get the following error message from a 3rd party module that is registered into Microsoft Dynamics GP 2013 R2 deployment. So now I need to troubleshoot the culprit and find what is causing this issue. There are a few places I can look to get started and I have attached an image below to show the issue I am having.

 

dexterity error message

In this case the 3rd party is pretty easy to spot as the vendor Sabrix named the triggers as SBX which makes things a bit easier determining which module the issue exists in. And the naming convention also tells me in which module POP and what action “Save” that the problem exists in.

Anyway to be sure that this is the module that is causing the issue I can turn off the customization triggers in Dynamics GP to see if the message goes away when attempting to save. To do this you can visit the following location in GP to see all the currently registered modules and their customization scripts.

Tools -> customize-> Customization Status

customizationstatus

 

From this screen I can choose to disable the module I suspect is giving me the problem which should be the module named Sabrix MTS. I choose the module and then select to disable it (temporarily) to test this theory.

customization disable

Sure enough the next time I went to save with the MTS disabled I did not receive an error.

But lets say you get the error right when you startup Dynamics GP. You could not prove the culprit in this manner. Instead you would update the Dynamics.set file and remove the suspect module until is starts without an error then you know you have the right one. Luckily most of the vendors I have worked with over the years name their scripts pretty well so it is easy to spot a clash if you know your GP system and the modules on it.

To do that I would save a copy of the Dynamics.set file, then and take out Sabrix module and the dictionaries and update the module count of the system by 1. Next I would start Dynamics GP Sure enough I do not receive an error so I know that this is the module that is causing the issue.

Note: It is also important to remember that sometimes your 3rd party will have other items installed. These files might be in the /addins directory as well in dynamics GP and might cause an error on startup if they are there and the module is disabled. You would have to remove these as well to prove out the module that is causing issues.

Once you have found the target module it is usually a call to the product vendor. In my case the situation was different. I just needed to make sure that another module in my Dynamics.Set file was loaded before I registered the Sabrix MTS.

This was done by just moving the product up in the Dynamics Set file and all was good.

 

 

 

Tags:

New Features in Dynamics GP 2015

Posted by dynamicsnick on April 21, 2015
Microsoft Dynamics GP / No Comments

Microsoft Dynamics GP 2015 System Wide New Features

This video describes the new system wide features in the Microsoft Dynamics GP 2015 http://community.dynamics.com/gp/default.aspx.

Read more …

Tags:

Microsoft Dynamics GP 2013 R2 Upgrade Prep Tips

Posted by dynamicsnick on April 11, 2015
Microsoft Dynamics GP / Comments Off on Microsoft Dynamics GP 2013 R2 Upgrade Prep Tips

When getting ready to upgrade to Microsoft Dynamics GP 2013 R2 or any GP upgrade for that matter there are always the normal items that you will want to investigate. Firstly all installed modules, 3rd party vendor support, System requirements, unsupported system modifications that may be a blocking upgrade issue, and data prep and mock upgrade in a test environment.

I am always surprised at the number of customers that choose the option to not go through a mock data upgrade at least to verify that there are no issues with the data migration scripts, custom windows, and 3rd party vendors. The user acceptance testing should be the largest part of the upgrade to verify that everything is correct before you attempt the production upgrade. It is well worth the process every time.

Here are a few key items to review before upgrading to 2013 R2 from a previous GP Release.

1. Account Framework Table Conversion:  We convert several tables that have account framework information in them.  If the account framework tables in the company database, do not match the SY003001 and SY00302 tables in the DYNAMICS database, the upgrade will fail.  Please run the Account_Framework_Validation.txt script from the Upgrade Guide to validate your tables prior to the upgrade.  If results are returned, please work with your Partner or contact Technical Support to talk about the options for those tables.  Here are the tables we convert:

GL10110
GL10111
GL70500
GL70501
GL00100
GL00201
IV70500

2. Human Resources and Payroll Suite (10.0 only): If you currently use the following Human Resources and Payroll Suite modules and are on Microsoft Dynamics GP 10.0, the January 2013 hotfix is required for the upgrade to Microsoft Dynamics GP 2013.  The January 2013 hotfix or any later patch release must be installed prior to launching Microsoft Dynamics GP 2013 Utilities.  Click HERE to go to the service pack/hotfix page for Microsoft Dynamics GP 2013.

Product ID 1911 – HRM Solution Series
Product ID 4522 – Payroll Integration to Payable
Product ID 4933 – Certification Manager
Product ID 4955 – Employee Health and Wellness

3. Collections Management: If you currently use Collections Management with Microsoft Dynamics GP 2010 and are on version 11.00.2164, a new MSI is required for the upgrade to Collections Management for Microsoft Dynamics GP 2013.  The new Collections Management MSI, must be installed prior to launching Microsoft Dynamics GP 2013 Utilities.  Click HERE to go to the service pack/hotfix page for Microsoft Dynamics GP 2013.  Please refer to the Notes section to obtain the new MSI for Collections Management.

4. Database Compatibility:  If you are moving to a new SQL Server in addition to the upgrade to Microsoft Dynamics GP 2013, you can restore your databases to the new SQL Server and start your upgrade.  Please refer to KnowledgeBase Article 878449 for the steps to move to a new SQL Server.  Once the databases are restored to the new SQL Server, you must change the database compatibility.

a. In the SQL Server Management Studio. right-click your database and click Properties.
b. Under Select a Page on the left, click Options.
c. Change the Compatibility Level to match the version of SQL Server you are running.  SQL 2005 = 90, SQL 20082008 R2 = 100, SQL 2012 = 110.

5. Purchase Order Tables: If there are detail records in the POP10110 and the POP30110 that do not have a matching header record in the POP10100 and the POP30100, the upgrade may fail on those tables.  Run the Invalid_Records_POTables.txt script from the Upgrade Guide to validate all detail records have a header record.  If results are returned, you can either remove the detail records or run checklinks in the current version you are running.

6. Server Drop Down List Blank: When launching Microsoft Dynamics GP 2013, the Server drop down list may be blank.  The Server drop down is the OBDC DSN that Microsoft Dynamics GP needs to connect to your SQL Server databases.  If the ODBC DSN is an older version or an x64 DSN, it will not show up in the list.  Please make sure you have a 32-bit ODBC DSN created using either the Native Client 10.0 or Native Client 11.0 driver. ClickHERE for the steps to setup an ODBC DSN.

7. Payroll Work Tables (10.0 only): If upgrading from Microsoft Dynamics GP 10.0 and you use payroll, run the Payroll_Work_Tables.txt from the known issues script library to clear the Payroll Work Tables.  If records exist in those tables, the upgrade will fail on the UPR10*** tables.

8. Workflow Documents Must be Final Approved: If you use our Workflow for GL/PM/RM batches, Purchase Orders, Vendor Approvals, Credit Limit Overrides, Sales Quotes. Employee Onboarding, etc., all Workflow Documents must be final approved prior to the upgrade.  No documents can be pending.  The upgrade does check for this and will stop Utilities and provide a report showing what documents need to be approved.

9. Microsoft Dynamics Adapter Service: If you use the CRM Connector for Microsoft Dynamics GP and the Microsoft Dynamics Adapter Service is running on the server where you are performing the upgrade, please stop the service temporarily.  Once the upgrade is complete, the Microsoft Dynamics Adapter Service can be restarted.

10. General Ledger Transaction History Record Count (10.0 only): If you are upgrading from Microsoft Dynamics GP 10.0, run the following script to get a feel for the record count in the GL30000 table.

select count(*) from GL30000

The GL30000 is the GL Transaction History table and can be very large.  If you have millions and millions of transactions in the GL30000, please make sure to run a test upgrade to Microsoft Dynamics GP 2013.  We do have a big conversion on the GL30000 that may slow down the upgrade.  Running a test upgrade will allow you to benchmark the upgrade for your environment.  Some tips!!!  Make sure you have enough disk space on the drives where the MDF and LDF are located.  Also, manually grow the size of your LDF to accommodate the size of the largest table.  Grow the LDF of your company database and TEMPDB.

11. Microsoft Dynamics GP Utilities Stops Responding: When you launch Utilities for the upgrade, most of the processing is done on the SQL Server.  If you happen to client away, Utilities may appear to stay white and show “not responding”.  Please do not close out of Utilities, the upgrade is still running.  Please give the upgrade time to continue working.  If you feel the upgrade is hanging or locked up, please start a SQL Server Profiler trace to review activity.

Please review the known issues above prior to your Microsoft Dynamics GP 2013 R2 upgrade!  Running the scripts above will for sure eliminate issues in the long run!  Remember to always run a test upgrade first!

GP 2015 New Features Applications

Posted by dynamicsnick on December 25, 2014
Microsoft Dynamics GP / No Comments

Microsoft Dynamics GP 2015 New Features- Applications

This video describes the new features in the Microsoft Dynamics GP 2015 Application http://community.dynamics.com/gp/default.aspx.

Read more …

Tags:

Smartlist templates for Microsoft Dynamics GP and Smartlist Builder

Posted by dynamicsnick on September 15, 2013
Microsoft Dynamics GP / Comments Off on Smartlist templates for Microsoft Dynamics GP and Smartlist Builder

So I never knew that there were templates for the default smartlists that are in Microsoft Dynamics GP. I have actually rebuilt some of these in the past and looking for something not even related I stumbled upon them in Partnersource.

I thought I would share these as apparently they have existed there since Dynamics GP 10! Here is the link, however you will need a Microsoft Customer or Partner Source account login to download.

Smartlist Templates – Microsoft Dynamics GP

 

Control ID is missing or invalid

Posted by dynamicsnick on April 16, 2013
Microsoft Dynamics GP / Comments Off on Control ID is missing or invalid

If you see this issue in Microsoft Dynamics GP it usually means that something has happened to the control number on the Batch. No worries as there is an easy non-technical fix. Most likely your batch has ended up in batch recovery so choose to continue.

You should see the batch back with some error message as to why it failed such as “control total and actual totals do not match.”

Just create a new batch ID and move your transactions into that batch and then re-post the batch and it should work again as you would typically expect. Then remove the offending batch id.

Microsoft Dynamics GP – Customer Aging Buckets SQL Query

Posted by dynamicsnick on February 16, 2013
Microsoft Dynamics GP / Comments Off on Microsoft Dynamics GP – Customer Aging Buckets SQL Query

There is a lot of great data from smartlist, smartlist builder, excel builder as well but sometimes you just want to get to the raw data so you can take a closer look.

Here is a query I put together for getting the customers and aging bucket details out of Microsoft Dynamics GP. This works in all releases of Dynamics GP back to version 10 as it is primarily based on the customer master and master summary in GP. You can then use this data to generate customized SSRS statements to customers after the aging process is completed, to send alerts or notification reports to administrative staff, or for your collections dashboards for your accounting departments.

One thing to note is that this might require slight adjustments depending on your buckets setup. This will reflect data in buckets from the GP customer aging located in Dynamics GP under Tools–> Routines -> Sales -> Aging. Choose the date in GP that you want to age as of and then you can run the query attached to get right at the data.

The Script is saved as a .txt file, just copy and paste it into sql management studio or rename to .sql.

GP2013_CustomerAgingDetailsFile