Microsoft Dynamics GP 2013 Service Pack 2 is now available

Service Pack 2 for Microsoft Dynamics GP 2013 is now available for your consumption. Microsoft has released the product ahead of schedule – originally, September of 2013. I guess this will make for an even more exciting Microsoft Dynamics GP Technical Airlift 2013.
 
Service Pack 2 is probably the most comprehensive update so far to Microsoft Dynamics GP 2013 and includes a number of fixes and enhancements. Let’s take a quick look:
 
Modules activated for Web Client:
  • Field Service
    • Service Call Management
    • Depot Management
    • Preventative Maintenance
  • Project Accounting
  • Manufacturing
    • Bill of Materials
    • Manufacturing Order Processing
    • Master Production Scheduling
    • MRP
    • Manufacturing Suite
  • Fixed Assets Enhancements
  • Business Activity Statement (BAS) for Australian GST
  • Payment Document Management (PDM)
 
Features Exclusive to Web Client:
  • Visual Studio Tools for Web Client v1.0
  • Keyboard Shortcut enhancements
  • Change single machine configuration to support both the Web Client web site and runtime service using the same port  
  • Add styling to ribbon to show focus  
  • Web client messaging retry/refresh & Client Side error handling / notification improvements
  • Better scrollbars for standard reports 
 
New Desktop & Web Client Features:
  • GL – Roll down changes to Account Segment Description
  • Reconcile checkbook without marking transactions
  • Cash Receipts Inquiry display checkbook ID
  • Customer Combiner & Modifier
  • Vendor Combiner & Modifier
  • Payables Void Enhancements
  • AA Finance Charge assessment
  • AA and Sales order deposits
  • Payroll Inquiry Check Date Sort Options
  • Applicant E-mail in HR
  • Doc Attach 2.0:
    • Document Flow
    • Status Tracking
    • Delete Password
    • Attachment Properties
    • Attachment Email
    • Delete Utility
  • SmartList Splitter
  • SmartList Designer
Note: the SmartList Splitter was a cool piece of code made available with the Support Debugging Tool initially. If you are running Microsoft Dynamics GP 2010, you can take advantage of this via the Support Debugging Tool.
 
Service Pack 2 can be recognized by its new build number, 12.00.1482 and the Dexterity version is 12.00.0269. For more version details download the MDGP2013_MSPVersionList.xls file. For the install guide and a list of issues fixed, download the 12.0SP2_install_guide_ENUS.pdf file. Both files are available from the main Service Pack page (or from the links here).
 

Service pack 2 is available from the Service Pack 2 page or you can download the full updated DVD image:

PartnerSource
Product Release Downloads for Microsoft Dynamics GP 2013 Secure Link
Service Pack, Hotfix, and Compliance Update Patch Releases for Microsoft Dynamics GP 2013 Secure Link

CustomerSource
Product Release Downloads for Microsoft Dynamics GP 2013 Secure Link
Service Pack, Hotfix, and Compliance Update Patch Releases for Microsoft Dynamics GP 2013 Secure Link

The Microsoft Dynamics GP Support and Services Blog has more information related to Service Pack 2. Please visit their page for more information:

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

More:
Microsoft Dynamics GP 2013 Service Pack 2 is now available

August 30, 2013 · Mariano Gomez · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 239

Microsoft Dynamics GP 2013 Service Pack 2 … – MSDN Blogs

A blog dedicated to everything to enable Developing for Microsoft Dynamics GP by David Musgrave and the Microsoft Dynamics GP Developer Support Team.

Read More:
Microsoft Dynamics GP 2013 Service Pack 2 … – MSDN Blogs

August 30, 2013 · David Musgrave · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 115

GPUG Magazine – Fall 2013 edition is out … – MSDN Blogs

A blog dedicated to everything to enable Developing for Microsoft Dynamics GP by David Musgrave and the Microsoft Dynamics GP Developer Support Team. Search Form. Search this blog. Search all blogs. Options. Blog Home · About · Email Blog Author · Share this · RSS for posts · Atom · RSS for comments. Tags Developing for Dynamics GP on Facebook This blog at Dynamics GP Support Blog: http://aka.ms/DynamicsGP. SDT Portal: http://aka.ms/SDT

Read more here:
GPUG Magazine – Fall 2013 edition is out … – MSDN Blogs

August 29, 2013 · David Musgrave · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 136

GPUG Summit 2013 – Developing for Dynamics GP … – MSDN Blogs

A blog dedicated to everything to enable Developing for Microsoft Dynamics GP by David Musgrave and the Microsoft Dynamics GP Developer Support Team. GP Support Blog: http://aka.ms/DynamicsGP. SDT Portal: 

Visit link:
GPUG Summit 2013 – Developing for Dynamics GP … – MSDN Blogs

August 28, 2013 · David Musgrave · No Comments
Tags: , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 150

Accessing Microsoft Dynamics GP Default Settings from Visual Studio Tools

Rarely you will hear the Dex.ini file being called the Microsoft Dynamics GP defaults file. However, the Dex.ini contains keys (and their associated values) that define how Microsoft Dynamics GP behaves in some cases. For example, SQLLastUser=sa stores the login of the last user who accessed the system on that specific instance of Microsoft Dynamics GP, in this case, ‘sa’. Likewise, AutoInstallChunks=TRUE, allows Microsoft Dynamics GP to bypass prompting the user for new code (chunk file) to be installed at the time of launching the application. There are other settings controlling how certain features behave.

You can find a list of Dex.ini settings here.

Recently, I was helping a good friend of mine up in Maine who attended my Dexterity class in Boston and this time he wanted to know how to read the path for the Microsoft Dynamics GP help file. Of course, there’s a simple (predefined) method for this as my good friend Patrick Roth with the Escalation Engineering team in Fargo pointed out, if you are familiar with some of Microsoft Dynamics GP form procedures:

string strPath = “”;
strPath = Dynamics.Forms.MainMenu.Functions.GetDynamicsHelpPath.Invoke();
MessageBox.Show(strPath);

So, let’s assume you had no clue this function existed. How would you address this issue? Frankly, I can think of at least 3 ways to do this:

1) Using a hybrid method whereby you create a Dexterity dictionary to wrap the Defaults_Read() Dexterity sanScript function into a user-defined global function. This method presents a challenge as you need to use the Dictionary Assembly Generator (DAG.EXE) to create an assembly you can reference from your VST project. In addition, you may or may not want to add an entirely new dictionary into the picture, when delivering your final solution. However, in case you are interested, this is the implementation:

GetDexIniSetting function

For more information on developing hybrid applications with Dexterity and Visual Studio Tools take a look at my articles:

Developing Microsoft Dynamics GP hybrid integrating applications
Hybrid development for the Managed Code developer
Hybrid development for the Managed Code developer (cont.)

2) You could use the Continuum API from Visual Studio Tools to access the Defaults_Read() sanScript function. The Continuum API is the Component Object Model (COM) API that is available for Microsoft Dynamics GP. The Continuum API documentation is available for download here. In this method, all you have to do is add a reference to the interop.Dynamics.dll COM library, which hosts the Continuum API.

// Created by Mariano Gomez, MVP
// This code is licensed under the Creative Commons 
// Attribution-NonCommercial-ShareAlike 3.0 Unported License.
// http://creativecommons.org/licenses/by-nc-sa/3.0/legalcode

public string GetDexIniSetting(string searchKey)

   ParameterHandlerClass myParamHandler = new ParameterHandlerClass();
            
   try
    Dynamics.Application gpApp = (Dynamics.Application)Activator.CreateInstance(Type.GetTypeFromProgID("Dynamics.Application"));
     if (gpApp == null) 
       return "";
     else
     
       string passthrough_code = "";
       string compile_err;
       int error_code, result;

       result = gpApp.SetParamHandler(myParamHandler);
       myParamHandler.IN_Key = searchKey;

       passthrough_code += "local boolean err_val;";
       passthrough_code += "local string dex_key_val, dex_key;";
       passthrough_code += @"err_val = OLE_GetProperty(""IN_Key"", dex_key); "; 
       passthrough_code += "dex_key_val = Defaults_Read(dex_key);";
       passthrough_code += @"err_val = OLE_SetProperty(""OUT_KeyVal"", dex_key_val);";

       gpApp.CurrentProductID = 0; 

       error_code = gpApp.ExecuteSanscript(passthrough_code, out compile_err);
       return myParamHandler.OUT_KeyVal;
     
   }
   catch
    MessageBox.Show("Failed to initialize gpApp");
     return "";
   
 }

public class ParameterHandlerClass

  public string IN_Key  get; set; 
  public string OUT_KeyVal  get; set; 
}

In the above code, we define a parameter handler class
with couple properties for the key that will be read from the Dex.ini and the key value to be retrieved.

In our GetDexIniSettings method, we instantiate our class and use the Continuum SetParaHandler() method to load the IN_Key property value. We then setup our pass-through code and invoke sanScript’s OLE_GetProperty() function to retrieve the value of the IN_Key from our VST application via some old fashioned OLE automation. The OLE_SetProperty() function then returns the value to our class property, OUT_KeyVal.

That’s it!

3) The third method uses some classic C# reflection to get the path of the AddIns. It then converts this to the path of the Data folder and the dex.ini file, and then uses the Pinvoke() method to read the key in the dex.ini and return the value.

DllImport("kernel32.dll", CharSet = CharSet.Unicode)
 static extern uint GetPrivateProfileString(
 string lpAppName,
 string lpKeyName,
 string lpDefault,
 StringBuilder lpReturnedString,
 uint nSize,
 string lpFileName);

//get path which should be the addins folder
String strPath = System.IO.Path.GetDirectoryName(System.Reflection.Assembly.GetExecutingAssembly().Location);

//look for Addins path
if (strPath.EndsWith(@"AddIns", true, System.Globalization.CultureInfo.InvariantCulture) == true)
 //and if we find one replace with the data folder
  strPath = strPath.Replace(@"Addins", @"DataDex.ini");

else
 //if not in addins then we must be in the root GP folder (like GP 2013 does with GP addins) so tack on Data
  strPath = strPath + @"DataDex.ini";

 
StringBuilder sb = new StringBuilder(100);
uint res = GetPrivateProfileString("General", "Pathname", "", sb, (uint)sb.Capacity, strPath);
MessageBox.Show(sb.ToString());

// Copyright © Microsoft Corporation.  All Rights Reserved.
// This code released under the terms of the 
// Microsoft Public License (MS-PL, http://opensource.org/licenses/ms-pl.html.)

The above method comes courtesy of my good friend Patrick Roth with the Escalation Engineering team at Microsoft.

All the above methods are generic in nature and can read more than just a specific key. It’s good to know that there’s more than one way to do things. If you are going all hybrid, there’s a code for that! If you want to be self-contained, there’s a code for that! If you want to deviate completely from sanScript because you hate it or don’t know it, there’s a code for that! Whatever route you choose it must work to your benefit.

As a good Australian friend of mine would say, “The right solution is the one that works!”.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More:
Accessing Microsoft Dynamics GP Default Settings from Visual Studio Tools

August 27, 2013 · Mariano Gomez · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 161

Reason of the Day to attend GP Technical Airlift #12

Microsoft and eOne Solutions are pleased to announce a one day only Extender training class, exclusively for partners on September 17th, 2013, prior to the Tech Airlift event. eOne, who has assumed  responsibility for sales and support (while continuing their testing and development efforts), is offering the class in order to give partners the skills needed to make GP fit their customers’ businesses, without writing code. In the training, eOne will cover every aspect of Extender 2013. Among the areas covered are:

  • Creating a basic window and form including the field types and options available.
  • Adding the Extender resource to SmartList.
  • Creating Templates on Windows and Forms.
  • Adding logic to your Windows and Forms using Actions.
  • Creating inquiries for Windows.
  • Adding extra Windows on Forms.
  • Adding your Forms to Menus.
  • Reporting on the Extender data using tools such as SmartList, Report Writer, and external sources.
  • Using tools such as SmartConnect and SmartView to access the Extender data.

There will be multiple exercises provided to help in the learning process.

Please note that there is limited seating available for the training, so we encourage you to sign up as soon as possible. You can sign up here or email abbey.cooper@eonesolutions.com for more information and details on the training.

Come to have fun, come to learn, just come to Fargo!

Are you signed up?
YES?  Great!  We’ll see you here!!

No?  What are you waiting for!!  Get signed up NOW!  And get your co-workers signed up for the other tracks!

http://gptechnicalairlift.com/

 

Jay Manley

See the original post:
Reason of the Day to attend GP Technical Airlift #12

August 26, 2013 · Jay Manley MSFT · No Comments
Tags: , , ,  · Posted in: Blogs I Follow Total Views: 122

Top 10 Reasons to use Extender

Extender is one of the most critical tools a company using GP can have in their tool belt. Here are the Top Ten Reasons to take a look at Extender:

1. Extender Makes GP Fit Your Business: Stop trying to make your business fit into GP, use the most flexible solution available to configure GP, just the way you want.
 
2. Extender Grows as You Do: Make changes to the data you capture when your business grows and changes.
 
3. Extender Lets You Eliminate Spreadsheets: Get rid of spreadsheets that duplicate GP data and track what you need, where you need it.
 
4. Extender Improves Your Data Quality: Never doubt your data again. Trust your data in GP.
 

5. Extender Saves You Money: Invest in the solution that is about 1/10th of the cost of customizations.
 
6. Extender Provides Easy Upgrades…and Less Expensive Ones, too!: Since you’re not spending time sorting through a developer’s code, you can update quickly & easily.
 
7. Extender Lets You Trigger Dex Code Anywhere, Anytime in GP: No other solution gives you so much flexibility with GP.
 
8. Extender Lets You Own Your Solution: You can switch partners, do all changes in house, whatever you want – you have the freedom!
 
9. Extender is Built by the ISV with the Most Customers Using Their Products in GP: With over 4,000 Extender customers to date, there are amazing Extender solutions out there and we can help add your solution to that list.
 
10. Extender is Supported By the Best: Highly experienced GP guru’s who can train, advise, review and support your Extender solution are the people you’ll be dealing with on the help desk.
 

Sound like a solution you want to add? Want to know more? Contact Abbey or Danielle by emailing sales@eonesolutions.com for more info!

Read more here:
Top 10 Reasons to use Extender

August 26, 2013 · Abbey · No Comments
Tags: , , , , , ,  · Posted in: Blogs I Follow Total Views: 109