Import and Export for Office in GP 2013
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
A customer ran across an interesting issue with Excel Based Budgeting after they upgraded to GP 2013.
Tag: Development Tools
Display Specific Line in Sales Order Processing
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
This will be a 2-for-1 post today as the example given solves a frequently asked question and was used to solve a customer issue.
Dynamics GP Crashes After Installing Addin
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
One thing we’ve noticed recently is an uptick of cases involving Visual Studio Tools assemblies causing Dynamics GP to crash after being installed.
Developing with the Microsoft Dynamics GP 2013 Named System Database
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Microsoft Dynamics GP 2013 introduced another long sought after feature….
The Named System Database.
Instead of the System database being hardcoded to DYNAMICS, a different name can be selected when installing GP.
So what does that mean? Well, it means that more than one Dynamics GP system can reside on a single instance of SQL Server. Before when a second Dynamics GP system was needed, you would have to install a new instance of SQL Server. Now you can have multiple System Databases on a single server without needing additional instances of SQL Server.
How to create Dexterity Cross Dictionary Lookups
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
As you may know, I was one of the pioneers of Cross Dictionary Dexterity Development and have posted about it a number of times (also see Can I customise a 3rd party form with Dexterity? and Understanding Cross Dictionary Dexterity Development).
Quick Tip: Capturing the Save Event with Visual Studio Tools
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I recently responded to a community post which was asking how to ensure that all save events from the Item Maintenance window were captured using Visual Studio Tools. The aim was to make sure that the additional fields added to the window with Modifier were saved when the item data in the window was saved.
Using a GP Web Service Extension in the Connector for Microsoft Dynamics GP
This is a reposting of an article Chris Roehrich originally wrote on my Developing for Dynamics GP blog.
The Connector for Microsoft Dynamics provides a powerful integration platform that can be customized and extended with the CRM Connector SDK and Web Services for Microsoft Dynamics GP SDK tool sets. The CRM Connector for Microsoft Dynamics GP page in PartnerSource has various downloads to get you started with the CRM Connector including the SDK download. You can find the GP Web Services SDK download here. Additionally, the Dynamics GP Web Services SDK page on MSDN contains the same reference information found in the download page and is available to those without accessing PartnerSource or CustomerSource and can be helpful for quick access.
eConnect error – The stored procedure doesn’t exist
This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
I ran across an odd eConnect issue a while back that I thought I’d share today.
Quick Tip: Solving Dexterity Trigger Clashes
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
In a recent support case, I had the rare situation where Dexterity Triggers clashed. Dexterity allows third party developers to create triggers against various events and scripts in a Dexterity application (like Microsoft Dynamics GP).
Do not use the DEX_ROW_ID table column in your Customizations and Integrations
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Today, I responded on a post on the Partner Forum asking “Can the DEX_ROW_ID change for a record over time?“. In this case the partner had seen the values for DEX_ROW_ID change on the GL20000 (GL_YTD_TRX_OPEN) and GL30000 (GL_Account_TRX_HIST) tables. This caused problems for an integration to an external system that used the DEX_ROW_ID as a key field.