SQL stored procedure to search an entire database

I don’t often re-post things from other blogs, but this is just too good not to share. David Musgrave recently published an update to his spSearchOnAllDB stored procedure on his blog, Developing for Dynamics GP.

Simply run the script to create the stored procedure and you can search all the tables in a database for a particular string or value. You might not need this frequently, but when you do – what an incredibly powerful tool to have.

Check out David’s post to download the script and see notes about usage. Thanks David!

You can see links to other helpful SQL Server tips on my SQL Server Coding Tips page.

 

Filed under: SQL Server Tagged: featured, SQL code, SQL Server

Read this article:
SQL stored procedure to search an entire database

July 22, 2013 · Victoria Yudin · No Comments
Tags: , , , , , , , , ,  Â· Posted in: Blogs I Follow Total Views: 487

Microsoft Dynamics GP 2013 H2 Release Info – Custom Information …

Read more here: http://blogs.msdn.com/b/gp/archive/2013/07/18/microsoft-dynamics-gp-2013-h2-release-announced.aspx. Nancy Phillippi, Sales and Marketing Manager at Custom Information Services (CIS) for Microsoft 

Read More:
Microsoft Dynamics GP 2013 H2 Release Info – Custom Information …

July 22, 2013 · nphillippi · No Comments
Tags: , , , , , ,  Â· Posted in: Blogs I Follow Total Views: 264

GP 2013 Cookbook

Just finished my first read of the GP 2013 Cookbook and have to say – well done Ian and Mark!  As usual, the content and quality of the material presented is just outstanding.  The writers have taken the original GP 2010 Cookbook, which is excellent in its own right, added GP 2013 new features to it, and offer an excellent resource of tips and tricks that every GP user should have on their bookshelf or in their e-reader.

*click image to enlarge

Regardless what GP version you’re using, this book should be required reading.  It offers golden nuggets that apply GP 2010/2013, and many versions previous.
Great job Mssrs. Grieve and Polino.

Get your copy at PACKT or at Amazon.

Excerpt from:
GP 2013 Cookbook

July 20, 2013 · Frank Hamelly MCP-GP MCT MVP · No Comments
Tags: , , , , , , , , , ,  Â· Posted in: Blogs I Follow Total Views: 320

Troubleshooting the Microsoft Dynamics GP 2013 Web Client – Part 2

Part 2 – Resolving Microsoft Dynamics GP 2013 Web Client Implementation Issues



Yesterday, in Part 1 of this series, I addressed the Microsoft Dynamics GP Support Team’s posture when addressing Web Client support cases, by cataloging each reported issue as either implementation- or functional-related. In this opportunity, I will look at the major processes involved in driving your implementation-related support case to a rapid and successful closure.

In the process of troubleshooting your Web Client implementation issue, there are two categories of data that need to be compiled to close a support case: installation information and application related exceptions.

Compiling the installation information typically involves gathering the following information:

  • Type of installation (Intranet/Extranet/both)
  • Information about certificates
  • Firewall and Ports information
  • Number of servers supporting the installation (Web Servers/Session Hosts/SQL Servers)
  • Information about load balancers (if exist)
  • Domain security groups and user accounts
  • Run the Web Client Diagnostic Tool available as an option when you open a support case.
  • Provide the XML output file created by the Web Client Implementation Tool, if available

Compiling the Web Client application related exceptions involves gathering the following information:

  • Dynamics application log events
  • Session Service logs (if enabled)
  • Session Central logs (if enabled)
  • Internet Information Services (IIS) logs
  • Web page exception messages
  • Tenant exception information (if using Multi-tenant Services)
  • Fiddler and Microsoft Network Monitor (Netmon) traces

Web Client implementation exceptions can usually be identified by an “Unexpected Error” message in the browser as shown below:

Web Client application exception

Traditionally a support case would be started with a screenshot of an issue. However, as it relates to Web Client, Microsoft Dynamics GP Support cannot determine what an exception really means other than the fact that you encountered an exception. As such, Web Client implementation cases will usually require running the Web Client Diagnostic Tool in addition to providing Event Viewer information related to the Correlation ID displayed in the browser.

Event Viewer: Dynamics application event log

In a future installment, I will be covering all the troubleshooting tools available at your disposal, including the Web Client Diagnostic Tool, Web Client Implementation Tool, Fiddler, and Netmon among others.

In Part 3 of this series, I will address functional exceptions and resolution of functional issues.

Until next post!

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

See more here:
Troubleshooting the Microsoft Dynamics GP 2013 Web Client – Part 2

July 19, 2013 · Mariano Gomez · No Comments
Tags: , , , , , , , , , ,  Â· Posted in: Blogs I Follow Total Views: 339

Microsoft Dynamics GP 2013 SP2 – Release Schedule Announced

Over at Microsoft Dynamics GP official blog, Errol sheds light on Microsoft Dynamics GP 2013 SP2 release schedule.

Along with that, he also lists on new features this release would have. Pretty interesting, especially on Web Client front.

I’m excited.

VAIDY

Filed under: #MSDYNGP, GP 2013, GP2013, GP2013 SP2, Microsoft Dynamics GP, Microsoft Dynamics GP 2013, Service Packs, Web Client

View post:
Microsoft Dynamics GP 2013 SP2 – Release Schedule Announced

July 18, 2013 · Vaidyanathan Mohan · No Comments
Tags: , , , , , , ,  Â· Posted in: Blogs I Follow Total Views: 312

Microsoft Dynamics GP 2013 H2 Release Announced

Last week at Microsoft’s Worldwide Partner Conference we shared plans for updating Microsoft Dynamics GP 2013 in Q4 of this calendar year with enhancements to both the core software and to Business Analyzer, our Windows 8 companion app.

The software updates in this release will be delivered through Microsoft Dynamics GP 2013 SP2 via PartnerSource. The Business Analyzer update will be delivered for download through the Windows Store.

Here’s a quick preview of some of the enhancements we’re working on:

– Web Client releases for the Project Series,Manufacturing Series, and Field Service Series.

– ISV Extensibility  for WC – Enables customers and ISVs that build forms and controls in Visual Studio to make that functionality available in the web client.

– Doc Attach  – additional functionality that enables attached documents on cards to roll down to transactions while also adding the ability to include attached documents in Emails.

– Smartlists – enables users to hide the navigation tree giving them a full screen of data.

–  Functional features – including Default Sort Order AP Checks and the ability to Assign Items to All Sites and more.

For Business Analyzer:

– Re-writing the app into HTML5 & JavaScript

– Support connections through the Azure Service bus

– Support for Management Reporter Reports

– Ability to pin reports to the Windows 8 Start Screen

– Windows 8 Phone App

Beginning in September we will deliver our world famous “Feature of the Day” through this blog site.  We will also talk extensively about this update at our Technical Airlift in September along with our future roadmap.  The Microsoft
Dynamics GP Statement of Direction document will be updated in conjunction with the timing of the Technical Airlift and its availability will be communicated via this blog.

Technical Airlift Event Details

Dates: September
18 – 20, 2013

Where: Microsoft Campus – Fargo, ND

Visit http://gptechnicalairlift.com for moredetails or to register!

See the original article here:
Microsoft Dynamics GP 2013 H2 Release Announced

July 18, 2013 · Errol Schoenfish · No Comments
Tags: ,  Â· Posted in: Blogs I Follow Total Views: 284

Troubleshooting the Microsoft Dynamics GP 2013 Web Client – Part 1

Part 1 – Microsoft Dynamics GP Support Team’s Posture



With the introduction of the Microsoft Dynamics GP 2013 Web Client, system administrators now face additional challenges when troubleshooting errors produced while accessing the Web Client all the way to using the Microsoft Dynamics GP application itself over the browser.

To understand the troubleshooting process, it’s best to explain the Microsoft Dynamics GP Support team’s posture when addressing a support case: any error event that occur before the Microsoft Dynamics GP login window is presented to the end-user will be treated as a Web Client implementation support issue.

Issues in this category involve everything from the deployment planning of the Web Client up to the point where you obtain the Microsoft Dynamics GP Login window. Items such as issues during the installation of the Web Client, network configuration, certificates, routers, firewall configuration, DNS resolution issues, issues preventing access to the web client Sign In window are all considered issues that prevent an end user from using the Web Client and therefore access Microsoft Dynamics GP.

Web Client Sign In window (Windows Authentication)

Any error event that occurs after the Microsoft Dynamics GP application Login window is presented, and during the normal use of Microsoft Dynamics GP is considered a functional support issue.

Microsoft Dynamics GP Login Window (SQL authentication)

Functional support issues involve everything from issues accessing Microsoft Dynamics GP all the way through using all the application functions within the Web Client: data entry, printing problems, posting issues, Report Writer reporting, SSRS reports, Excel reports, and all issues that may happen within the Microsoft Dynamics GP application while using the Web Client.

Having a clear cut definition between problems will allow you to reach the right support engineer at Microsoft. In addition, implementation issues may require the use of specialized diagnostic tools to collect information about the Web Client installation environment that will allow the support engineer or escalation engineer to better understand how your environment is configured.

In contrast, functional issues would typically follow the standard support protocols you have come to know over the years.

There are some clear benefits to this posturing:

1. A reported problem can be routed to the right support team the first time around. After all, an issue with a certificate may require someone technical from within the support team to address the problem, as opposed to a problem printing a report.

2. Having the right team addressing the issue will allow Support to issue whitepapers, videos, or even training content on how to address the most frequent issues that come to them.

3. Diagnostic information can be served up to the right support engineer at the time a case is created. This is only possible if a problem is tagged as an implementation issue versus a functional issue.

4. It allows both technical and functional support teams at Microsoft to keep stats on product quality, which may result in targeted hotfix or service packs.

Tomorrow I will address the steps involved in resolving an implementation problem and how you can take advantage of some of the latest tools available from Microsoft to assist in the process.

Until next post!

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

Read the article:
Troubleshooting the Microsoft Dynamics GP 2013 Web Client – Part 1

July 18, 2013 · Mariano Gomez · No Comments
Tags: , , , , , , ,  Â· Posted in: Blogs I Follow Total Views: 399