Dynamics GP Excel Paste Now on Microsoft Pinpoint


The tool was approved for publishing yesterday, you can now find it by searching the applications directory:


I expect a small review from you all to support the tool Smile



Mohammad R. Daoud MVP – MCT
+962 – 79 – 999 65 85

Read the original:
Dynamics GP Excel Paste Now on Microsoft Pinpoint

July 10, 2012 ·  · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 340

Product Suggestion: eConnect POP Tax Engine

David Meego - Click for blog homepageOver the last few weeks, Mark Polino, MVP over at DynamicAccounting.net has been posting articles asking you to vote for Product Suggestions using the Microsoft Connect site.

Well now it is my turn….



To start with we need a little bit of history:

When the Purchase Order Processing module in Great Plains Dynamics was first written it did not support taxes. You could enter a tax amount manually, but there was no support for Tax Details and Tax Schedules and no automatic calculation of taxes.

When Australia introduced the GST (Goods and Services Tax) in July 2000, a tax engine was required so that taxes could be calculated automatically and included on Purchase Orders (and flow through to the Receivings Invoices). To make this happen by the July 2000 deadline, I was contracted my Great Plains Australia while I worked for Winthrop Dexterity Consultants to write support for POP Taxes into Dynamics v5.50 as well as support for the Business Activity Statement and PAYG Payment Summary reports. Some of the other features needed for Australian GST were coded by the development team in Fargo and between us we had a Dynamics v5.50 GST release ready in time to be deployed at customers before the new tax system went live.

When Great Plains Dynamics and eEnterprise v6.00 was released, the POP Tax engine had been updated and was now part of the core product for all countries.



So, now we come to eConnect.

When the eConnect SOP nodes were created there was no automated Tax Engine. The Tax data had to be calculated outside of eConnect and then passed in with the rest of the document. Later a SOP Tax Engine was created. This engine duplicates the functionality of the Dexterity tax engine and allows the tax to be calculated based on the Customer and Item Tax Schedules.

When POP Taxes functionality was added to the core product, it was never added to eConnect. The ability to integrate Tax data has been added, but to this day there is still no automatic POP Tax Engine.

I have seen numerous requests on support cases for a POP Tax Engine and the answer has always been the same:

  • There is no POP Tax Engine.
  • Calculate the Taxes yourself and integrate the resulting data.
  • Vote on the Product Suggestion on Microsoft Connect.

I have had two of these cases in the last couple of weeks. But when I look at the Product Suggestion there are only 5 votes logged for the suggestion.

Considering that I found 45 cases in the support database with a quick search, I find the low count really surprising. This is what prompted this article.



If you or anyone you know wants this functionality, get them to vote using the link below. Go to the link and click on the green up arrow: 

While I can’t make any promises that if you vote, we will get a POP Tax Engine at any time in the future. I can guarantee that if you don’t vote, we will never get a POP Tax Engine. At least it will show if this is worth pursuing at all.


If you need more information about using Microsoft Connect, please see Scott Stephenson’s article on the topic:


If you or anyone in your organisation or organisations you work with would like this functionality PLEASE make the effort and vote for the suggestion.



Read this article:
Product Suggestion: eConnect POP Tax Engine

July 9, 2012 · David Musgrave · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 448

Copy Paste JEs from Excel to Dynamics GP

Mohammad R. Daoud has built a fantastic utility (based on a suggestion by MVP Mark Polino)

His utility allows you to copy a JE from excel directly into the JE window in Dynamics GP, how cool is that ?!

Mail him for a copy

In the past Rubal had built a utility requested by one of our customers that allowed you paste JE’s with AA information into a custom JE entry window. However, having something that works with the default JE window is fantastic!

Also if you dig excel for data entry with Dynamics GP – you should check out – the excel data entry templates that ship with SmartConnect. SmartConnect has templates for GL, PM, PO, SOP, Inventory – and with excellent VBA validation, and SQL connection to check if an account/item exists and so on.


Continue reading here:
Copy Paste JEs from Excel to Dynamics GP

June 19, 2012 · Jivtesh Singh · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 1,094

Microsoft Dynamics GP2013 Partner Training Rundown: Updated

We have three classroom training opportunities for partners.  Microsoft Dynamics GP 2013 will be a game changer in the market.  Get ready and be part of making the future. 

Microsoft Dynamics GP 2013 Technical Airlift


This training is targeted toward Consultants and Developers.  Registration numbers are growing and we are limited to 400 attendees, so register soon.  Also there is another event happening in Fargo, so book your hotel ASAP.


JumpStart Training for Microsoft Dynamics GP 2013

This training is targeted toward Consultants.  With the new web client, consultants need to understand implementing in a web environment.  This one day training will get you up to speed on topics like IIS, web services, firewalls and many other topics.

Space is limited to 80 and filling fast.  Register ASAP.

Microsoft Dynamics GP 2013 Presales Readiness

Times have changed and the way we sell has to change as well.  This one day training will get you ready to tell the Microsoft Dynamics GP story and show the product off.  After attending this training you will be able to close more deals and will have guidence of changes you can make in your organization to grow.

On September 11th we have this free day class in Fargo and October 16th in Seattle.  I would recommend going to one of these if possible.  We are working on 4 other cities with the possibility of more.  Stay tuned for more locations.

All events are listed here.  http://gptechnicalairlift.com/

Visit link:
Microsoft Dynamics GP2013 Partner Training Rundown: Updated

June 18, 2012 · Pam Misialek · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 366

Errol Schoenfish: 25 years and still loving it

I read attentively Errol’s recent post, 25 years and still loving it!, from beginning to end. Frankly, it reminded me of my own start in the industry and how I have evolved personally and professionally over the last 18 years.

So much was my interest in the article that I asked Errol to provide some additional insight into his early days working for Great Plains Software, how he’s got here today, and what made those early days special. After all, we all have dealth with that one support case we will always remember.

“This is the group of 11 support people that I started with. A great group. Still with Microsoft are Sue (Ewing) Larson, Lynne Stockstad, Randy Gerhold, Cheri (Whelan) Schoenfish, and myself. Both Randy and I left Great Plains and returned later. Randy came back through the acquisition of Real World and I left the company for 3 ½ years to work for a reselling partner of GP in Fargo and came back 16 ½ years ago. I’ve been a support technician, quality assurance manager in Development, a reselling partner, a Fargo-based partner account manager, Regional Sales manager, National and Global Accounts Sales Manager, Director of Sales and Marketing of Australasia, CRM evangelist, and Director of Product Management for Dynamics GP and SL.

1987 Great Plains Support Team – From left to right
First row: Sue (Ewing) Larson, Barb Bradner and Linda Warner
Second row: Cheri (Whelan) Schoenfish, Joe Steffan, Lynne Stockstad, Mitch Ruud, Glen Altringer, Errol Schoenfish, Randy Gerhold, Tom Eide

In 1987, As a recent college grad your initial impressions of such a young and vibrant company are “Man, what a great place to work”. The average age of Great Plains Software in 1987 was around 24 years old, so you can imagine the type of culture that was perpetuated. We worked long hours and spent all of our waking hours together as a group because most of us were young and single and on our first jobs. I really did love my first job, there was a certain sense of pride in helping someone solve a situation with their software. I remember one call in particular; A lady had called in because she was having problems with a payroll check run and she had 50 migrant workers waiting outside her trailer office for their checks. After a few minutes and getting the check run going she said “You’ve literally saved my life today, thank you sooo much”. There were always challenging times doing phone support for a software company also, but we built a reputation of being the best software support in the industry and won many awards along the way.”

You will agree with me that nothing beats the hairdos of the 80’s… ahhh!

Big thank you to Errol Schoenfish and we DO expect you to be around for another 25 years, indeed.

Until next post!

Mariano Gomez, MVP
IntellPartners, LLC

Read More:
Errol Schoenfish: 25 years and still loving it

June 18, 2012 · Mariano Gomez · No Comments
Tags: , , , , , , ,  · Posted in: Blogs I Follow Total Views: 388

25 years and still loving it!

It’s incredibly hard to believe but exactly 25 years ago today I started at a little known software company of 150 people called Great Plains Software.  Fargo wasn’t exactly the Silicon Valley, but I certainly was excited to start my new job in tech-support.  With a six-week training schedule in front of me, the thought of getting paid for learning, to this recent college graduate, seemed too good to be true.

On a more personal note, June 15, 1987 also serves as the day that I met my wife.  And I claim we had the first 100% Great Plains baby;  We met at Great Plains, started dating, got engaged and married and had a child all while working for a very young and vibrant company.

There’s been much learning for me personally and professionally and an incredible amount of change in the industry.  One of Great Plains Software’s claim to fame was being one of the first Hardisk Accounting Software packages in the market, as it ran on a 5 MB Bernoulli box.  The “original” Dynamics, with it’s ability to run on both Mac and Windows OS and the upcoming Web/Cloud capabilities of Microsoft Dynamics GP 2013 highlight the largest technologies changes that I’ve seen.

It’s often been said that change is the constant in our industry and I’d have to agree.  Since software comes from the minds of people, there will always be the next great technology changes.  Zach Nelson of Netsuite was quoted as saying “I think the cloud is the last great technology architecture”.  Well, I couldn’t DISAGREE with him more.  In fact, it bodes of arrogance in my view.  Today’s world of mobiletablet devices with a “there’s an app for that” thinking is directly contrary to having ALL your software in the cloud.  You see, the point is not “I sell hammers, therefore the best solution for driving in a screw is obviously a hammer”.  The value that software plus a partners’ domain expertise provides is the ability to listen to customers and deliver a compelling solution based on their needs.  That has also been a constant.

With all the change, the best thing about my time in the industry, however, has definately been the opportunity to travel and meet so many wonderful people.  It’s the reason I get up everyday and think about how we can be better at what’s important to our customers.  Convergence and our Partner Conferences continue to invigorate me as we applaud our past accomplishments and look towards the future.

Well, here’s to the future . . . perhaps not another 25 years for me personally, but the not too distant future looks equally as enjoyable as the past 25 years.


Taken from:
25 years and still loving it!

June 15, 2012 · Errol Schoenfish · No Comments
Tags: , ,  · Posted in: Blogs I Follow Total Views: 287

Understanding Support Debugging Tool Logging Modes

David Meego - Click for blog homepageThis is the first in a series of articles that are designed to help you understand how the Support Debugging Tool works and how you can leverage its different features. In the past, I have described features without explaining how these features can be used and what the differences between different modes is. With this series I hope to remedy that situation.



The Support Debugging Tool was originally created for Microsoft Business Solutions – Great Plains version 8.0 in September 2006 to solve a particular case. That case had a situation which could not be reproduced on demand, but the resulting incorrect data could be seen in the tables. The basic concept of the tool was to combine logging with triggers and scripts. Below is the high level flow:

  • Start Logging after logging in.
  • Register triggers on event, such as table being saved.
  • When trigger event occurs run a script which looks for the error.
  • If error has occurred, keep logs and notify user.
  • If error has not occurred, delete logs and start logging again.

When the tool was deployed on site, it took 4 days before the error occurred. The tool provided the support team with the logs leading up to the error occurring. This allowed the script to be identified and the cause of the error to be found and fixed.


Types of Logging

Most consultants know that Microsoft Dynamics GP can create a log of all communication between a Dexterity based application and SQL Server. This is the DEXSQL.LOG file which can be enabled using settings in the Dex.ini configuration file (KB 850996).

If you are a Dexterity developer, you will know that the Dexterity Script Debugger can create a log of all scripts executed with their parameters and hierarchy. Also Dexterity can create a profiler document containing all scripts executed and table access performed, with performance statistics such as number of times executed and length of time taken. These files have the default names of Script.log and Profile.txt. The Script Debugger can be enabled in runtime to make these logging features available (KB 850487).

The Support Debugging Tool takes advantage of the fact that all three of these types of logging can be enabled programmatically without changing the Dex.ini file or using the Debug menu (KB 850498). These three types of logging have been available since the Support Debugging Tool was first created.

With the release of Build 16 of the Support Debugging Tool, SQL Profile Tracing (activity at the SQL Server, including statements inside stored procedures) and Macro Recording (user activity at the Graphical User Interface) were added as new types of logging. These extra types of logging need to be enabled before they can be used. Once the initial setup is completed, they work just like the other types of logging.

In summary: The Support Debugging Tool supports the following types of logging:

  1. DEXSQL.LOG – Communication between the application and SQL Server
  2. Script.log – Dexterity scripts executed with parameters
  3. Profile.txt – Dexterity script and table performance data
  4. Trace.trc – Activity at the SQL Server
  5. Macro.mac – Activity at the User Interface

Now that we have all the background information covered we can discuss the main topic of this article.


Logging Modes 

The Support Debugging Tool supports three logging modes:

  1. Individual Logging Control
  2. Manual Logging Mode
  3. Automatic Debugger Mode 

The following sections will explain the differences between the logging modes and when and how they should be used:


Individual Logging Control

Individual Logging Control provides the ability to turn on and off the individual logging types separately and to specify the paths for the logs. It was created as part of the development process towards the other logging modes and is really only still available as it is useful when developing and testing the Support Debugging Tool. With build 16 of the Support Debugging Tool, the controls for Individual Logging Control were moved into a secondary window (click Logging Options from the main Support Debugging Tool window) as this is not the recommended method of using logging within the tool.

Note: Individual Logging Control is only provided for development and testing purposes, and is not recommended for normal usage. This functionality might be hidden entirely in the future.


Manual Logging Mode

Manual Logging Mode expands on Individual Logging Control, by allowing the logging to be turned on and off with a single mouse click, menu selection or key press. The logs are automatically User, Company, date and time stamped and are stored in a central location. Manual Logging Mode can be turned on and off from the main Support Debugging Tool window (available from the application level or window level Tools menus, or by pressing Ctrl-D).

Manual Logging Mode can also be turned on and off from the application level or window level Tools menus or using Ctrl-Shift-F9 and Ctrl-Shift-F10.

Manual Logging Mode should be used when you wish to capture the logs for a specific event or process. Simply get to the point just before the process or event and start the logging, then turn off the logging as soon as possible after the process or event.

This mode of logging is great for capturing the events that cause an error message, performance problem or data error. It also has the additional benefits of not needing to exit the application to turn on logging, not needing any changes made to the Dex.ini file (so it works well on Terminal Server/Citrix environments) and only capturing the minimum amount of data to be analysed.

Note: Selection of which logging types are used with Manual Logging Mode is made from the General Tab of the Administrator Settings window. Advanced Mode Features must be enabled from the Dex.ini Settings window to access the Administrator Settings window.


Automatic Debugger Mode

So what happens when you don’t know what process or event is causing your issue? How do you know when to start and stop the logging? 

This is where Automatic Debugger Mode comes into the picture. Remember the basic concept from the start of this article? That concept is implemented in the Support Debugging Tool as Automatic Debugger Mode.

With Automatic Debugger Mode you create Triggers. These triggers can be based against almost any event in the application: Table events, Function, Procedure and Script events and more… 

The trigger has a Conditional Script (Dexterity sanScript) which is executed when the event occurs and the trigger fires. The script can perform whatever commands are needed to confirm if the error condition we are looking for has occurred.

If the error condition has occurred, the logs are stored and various actions can be selected.

If the error condition has not occurred, the logs are erased and the trigger waits for the next occurrence of the event. 

Automatic Debugger Mode is designed to help find those non-reproducible issues where you can see the result of something happening but are not sure of the steps to make it happen.



  • Use Manual Logging Mode when you want logging for a known event.
  • Use Automatic Debugger Mode when you want logging leading up to an unknown event.
  • Don’t use Individual Logging Control.


In the next article we will discuss the different ways to turn Manual Logging Mode and Automatic Debugger Mode on and off. 


Understanding Support Debugging Tool Logging Modes

June 14, 2012 · David Musgrave · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 422