I want to be on Doug Pitcher’s list! Vote for me!

I know the fervor of the DynamicsWorld “top” 100 list is everywhere, but there is a far more prestigious list to aspire to. I am of course talking about the 2013 version of Doug Pitcher’s OFFICIAL 100 most famous, awesome and totally influential Dynamics people for 2012.

The list is so funny and honest, I don’t know how he comes up with this stuff, remarkable!. You will laugh out loud reading it, it’s that good.

I’ve been proud to be on it, and I hope I can cut the muster again this year.  And, dah, David Musgrave is on the list! That tells me for sure that Doug’s list is the best!

I don’t think Doug has an official ‘voting’ poll, but should you have the chance to talk, e-mail, text, twitter, Facebook, Linked in . . .  him, put in a good word for me Smile

Keep up the good work Doug!

Until next post!


Visit link:
I want to be on Doug Pitcher’s list! Vote for me!

April 12, 2013 · Leslie Vail · No Comments
Tags: , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 312

SSRS data specific report drill through to Bing Maps – Microsoft …

Using Sparklines & Data Bars to Visualize Data in SQL Server Reporting Services Reports | Dynamics GP Insights. by mpolino. on 28 May 2013. 0 comments. View More 

View original post here:
SSRS data specific report drill through to Bing Maps – Microsoft …

April 10, 2013 · mpolino · No Comments
Tags: , , , , , ,  · Posted in: Blogs I Follow Total Views: 299

Microsoft Dynamics GP 2013 Web Client First Run On … – azurecurve

View azurecurve’s Feed on Twitter View azurecurve’s pheed View azurecurve’s facebook page · View azurecurve’s Google+ View azurecurve.co.uk · azurecurve.com · Browse… Browse Categories · Browse Tags

Read more here:
Microsoft Dynamics GP 2013 Web Client First Run On … – azurecurve

April 10, 2013 · Ian Grieve · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 339

Dynamics GP 2013 Service Pack error


The Problem

Here’s the scenario. You have just installed a service pack. When you launch GP 2013, you are told you need to run Utilities. You launch Utilities, but oddly, it doesn’t find an existing instance of GP 2013. So, you just hit next and it moves along. Suddenly, the error pop’s up telling you:

“A system database name was not supplied. Run a repair of the Microsoft Dynamics GP installation”

system database not found

The fact that it was trying to create a new system database makes a little more sense now. Next, you dutifully launch Control Panel and begin to run the Repair routine. Right at the beginning of the Repair process you get another error:

“Object reference not set to an instance of an object”

object reference not set

Fabulous, you’ve seen this error before and it’s never pretty. We used to see it using Integration Manager and it was sometimes hard to fix. You’ll be delighted to know that this is a known error with an easy fix.

This situation comes up if you install the same service pack twice. The first time you install it, everything works perfectly, when you re-install, it you have the above problems.

The Fix

The fix for this is explained by Sara Purdy on the Microsoft Dynamics GP Support and Services Blog. Always go there first if you have any problems in Dynamics GP, there you will find some really exceptional advice. The actual posting is called (deep breath here) Microsoft Dynamics GP 2013 .MSP Patch Files Removing Information from Dex.ini and Registry.

All of the meaty solution information below was lifted directly from Sara’s  post. I’ve added some editorial comments for those of us (like me) who may need just a little more information to pull this off.

The culprit, as identified by Sara Purdy.

We have identified an issue with Microsoft Dynamics GP 2013 where the .msp files are removing registry entries and part of the Pathname= line in the Dex.ini when you RE-APPLY a patch. The first install of the patch works fine. The issue comes into play if you reapply the patch again on either a single instance or multi-instance. The Country and System Database Name get blanked out in the registry. The Pathname= line in the Dex.ini gets modified.

Bad: The Registry is caused to look like this:


Good: The Fixed Registry looks more like this:

fixed registry

Bad: The Dex.ini file is caused to look like this:


Good: The fixed Dex.ini file looks more like this:

fixed ini

Of course, you will use the name of your system database, whatever it is. Mine is named DYN131.

After you fix the registry and your Dex.ini file, you will need to re-apply the service pack. This, you have to do from the command line (what fun!).

The workaround:

These are the instructions from Sarah Purdy’s post:

The current workaround when re-applying the .msp to a specific instance of GP 2013 is to do the following:

1. Click Start, click Run, type regedit, and then click OK.

2. Locate and then click the following registry subkey:
Microsoft Dynamics GP 10.0 and later versions
32-bit environment
HKEY_LOCAL_MACHINESoftwareMicrosoftBusiness SolutionsGreat Plains1033

64-bit environment
HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftBusiness SolutionsGreat Plains1033

3. Expand the folder for the instance of Microsoft Dynamics GP you want to patch.

Note The DEFAULT folder is for the default installation. The Inst01 folder is for the second instance of Microsoft Dynamics GP. For example, if you want to patch the second installation, expand the Inst01 folder.

4. Click the SETUP folder, double-click the Product Code, and then copy the code.
5. Exit Registry Editor.
6. Open up a Command Prompt by right-clicking on it and selecting Run As Administrator.
7. To install the .MSP file, type the following, and then click OK:

C:updatename.msp /n E979C594-95F9-4E3A-985D-A1DFDF403227

(You can ‘Paste’ in the command line screen by right clicking next to where you want the data, and then choose ‘Paste’)

Note: Replace “C:updatename.msp” with the path to the .MSP file and the name of the .MSP patch file. Replace “E979C594-95F9-4E3A-985D-A1DFDF403227″ with the Product Code that you copied in step 4.

The current workaround when re-applying the .msp to all instances of GP 2013 on a machine is to do the following:

1. Open up a Command Prompt by right-clicking on it and selecting Run As Administrator, type in the following:
msiexec.exe /p C:updatename.msp
(Example: msiexec.exe /p C: MicrosoftDynamicsgp12-kb2799678-enu.msp)

Note: Replace “C:updatename.msp” with the path to the .MSP file and the name of the .MSP patch file.

2. Click OK.

Until next post!


See original article:
Dynamics GP 2013 Service Pack error

April 8, 2013 · Leslie Vail · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 671

Full vs Light User licenses

This is short and sweet – as I don’t usually post “sales” types of things and don’t intend to start now!

It’s somewhat of a tale of two client scenarios, and advice to those who hear certain things from their clients, and are in a position to recommend license options.

I’ve got two clients right now both of whom have expressed a need for additional user licenses in the near future.  Both of them have decent user bases right now (12 and 16 user licenses respectively). Both of them are running into issues with the maximum number of concurrent users being logged in, at various times of the day or week or month.

Client #1

Client number 1 has been a Dynamics GP client for 10 years, and their accounting department has grown probably double in size since they first implemented GP.  They keep hiring and have more and more users using GP every year.  Right now they have approximately 25-30 actual GP users set up in the system, and at least half of them are daily, transactional users which need GP open all day long to do their jobs.  The other half range from people that do a lot of analysis and reporting, to people who perform tasks more at certain times of the month – monthly expense report entry, for instance.  So far a 16 user base has been ok, but over the last few months, as they’ve hired one or two or three more bodies, they are using all 16 licenses nearly every hour of every day.

With this client, there is very little that can entirely offset the use of Dynamics GP outside of the application via reporting tools, as most of the users in the “non-day-to-day” camp still need in GP to do lots of inquiries, not all of which are easily replaced outside of GP.  This client is a perfect example of when they simply need to consider purchasing additional full user licenses to relieve some of the pressure – as well as the inevitable “Can someone log out of GP for a minute please?” cries around the office!

Client #2

Client number 2 has also been a GP client for a number of years. Their 12 user license has served them well for many years but over the years, they added more and more users to GP to allow more non-accounting staff to run their own reports and do their own inquiries.  This seemed innocent enough at the time, but now as their overall staff level has grown, they too are running into issues where there aren’t enough licenses for the users to log in when needed.  In this case, they often also have a couple of users who do tons of reporting and analysis opening both of their primary entities (companies) at the same time so they can easily flip back and forth at will, without stopping something they are doing in one company. That right there is 4 licenses taken up by 2 users most days of the week.

In contrast to the first client, they have a small accounting department and only about 30-35% of the user activity in GP is from users who I would define as “needing to be in GP”.  The vast majority of their user base do things that can easily be transitioned to other external methods – excel reports, sharepoint, SSRS reports etc. Some need in only to look up the next PO number to use; some only need to check inventory quantities on hand; some only run project accounting reports to check the status of their projects.

With this client, when they first asked me about an estimate to add new users, I immediately thought that in this case, it’s a complete waste of money for them. They originally purchased users for something they never ended up implementing, leaving them also with 50+ light user licenses, which to me means they shouldn’t spend a dime on licenses right now.  I’ll be working with them over the coming weeks to make a plan to transition as many of these users out of GP as possible, to external reporting and inquiry options.

The difference between Full & Light

Before I get into details, both of these clients are GP2010 users, not GP2013. Both of them are also on Business Ready Licensing so that is what I am really talking about in this post.  This information is also intentionally generic and general – specific questions on all the purposes and usages of each license should be a question for your partner if you are unsure.

In these examples, a full user is a license to log into GP itself; a light user is a license that allows you to access GP data externally to GP – Excel Reports, SSRS, Sharepoint etc. all come to mind as ways to access data and use its information.

Pricing varies depending on market and other factors, plus there are price breaks once you buy 11 or more users etc.  For simplicity, let’s just say the cost of a full user is $5,350 + enhancement. The cost of a light user is around $175 + enhancement. That’s a huge difference!

In my examples, client #2 was considering purchasing at least a couple more licenses which means an expenditure of over $10,000.  What I explained to them was for the same money, and likely for a lot less than that, it would be better for them in the long term to spend that money on the services to identify the reporting needs, utilize the out of the box report options already there in Excel Reports and SSRS, and if needed write a handful of specific reports to cover gaps that aren’t addressed. They have more than enough Light User licenses to cover their needs, and if they need more in the future, a couple hundred bucks is a no brainer.

If you are a consultant, and you notice your clients often at or near their maximum user capacity, look around at what users are keeping GP “full” and whether there are external solutions for them that have the option to provide more service to them and more inexpensively purchase licenses.

If you are a client and you’re in a situation like I have described above, take a look at what the users in GP are doing and identify any that don’t ‘really’ need GP to do what they are doing. Talk to your partner about options, and extend the reach of the information in GP to other users in your organization!

View post:
Full vs Light User licenses

April 5, 2013 · jen@kuntzconsulting.ca · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 380

T-SQL 2012: CHOOSE and IIF



We’ve been needing these two features for a long time. This post includes a couple of easy examples showing how these functions work.


I’ll start with CHOOSE. By using CHOOSE you can do away with many tedious CASE statements. CASE statement opportunities are everywhere in Dynamics GP. For instance, how many times have you needed to display the document type in your report and want a word, not a number. Prior to SQL 2012, we would have written a CASE statement that would look a lot like this:

    when 1 then ‘Quote’
    when 2 then ‘Order’
    when 3 then ‘Invoice’
    when 4 then ‘Return’
    when 5 then ‘Back Order’
    when 6 then ‘Fulfillment Order’
    ELSE ‘Undefined Document Type’
End as ‘ Doc Type’

CHOOSE will pick the value in your list according to the value of your data. It returns the expression at a specific index. So, instead of writing a case statement, you can simply write this:

CHOOSE (SOPTYPE, ‘Quote’, ‘Order’, ‘Invoice’, ‘Return’,
‘Back Order’, ‘Fulfillment Order’) AS DocType

If the value of your index is greater than the number choices, it will return NULL. It will also return NULL if the value is less than 1.


Next is IIF. Most of you probably already know how to use this and have wondered why you couldn’t do it in T-SQL. Flavors of this are in Excel formulas, Access calculations and even VBA, to name a few. It works with a Boolean expression and returns a value based on whether the expression is true or false. You set this up with three parameters. The first parameter is the expression you’re evaluating, the second parameter is the value if the expression is true, and the third parameter is the value if the expression is false. Yep, just like Excel.

So here’s what it looks like:

IIF(boolean_expression), value if true, value if false)

So much easier than CASE.

Until next post!


View original post here:
T-SQL 2012: CHOOSE and IIF

April 3, 2013 · Leslie Vail · No Comments
Tags: , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 411

Microsoft Dexterity Training Roadshow – Next Stop: Seattle

(C) Microsoft Corporation

The Microsoft Dexterity Training Roadshow rolls around the United States with its next stop in Seattle, Washington from April 22 – April 26, 2013.

We still have plenty of seats left, so if you want to learn some of the development techniques used by Microsoft Dynamics GP developers this is your chance. For registration information, click here.

Until next post!

Mariano Gomez, MVP
IntellPartners, LLC

Original post:
Microsoft Dexterity Training Roadshow – Next Stop: Seattle

April 3, 2013 · Mariano Gomez · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 320