Finding out the version of Office Web Components being used with your Microsoft Dynamics GP home page

Seriously, I wasn't planning on doing any more articles on the home page - at least not for now. But you have to admit this one is compelling. To find the version of the Microsoft Office Web Components running on your system,

1. Right-click on any metric graph currently being displayed on your home page.

Office Web Components options

Choose the About... option to continue.

2. You will now see the version number of the Office Web Components installed and being used with Microsoft Dynamics GP.

Office Web Components version
If you have any questions on a specific version, please see my article Microsoft Dynamics GP 2010 and Office Web Components for more information.

Until next post!

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

Comments

Post a Comment

Popular posts from this blog

Power Apps - Application Monitoring with Azure Application Insights

Image
In this video, learn to enable Power Apps Application Monitoring with Azure Application Insights.  The following topics are covered in this video:  ( 0:00 ) - Intro  ( 0:36 ) - What is Azure Application Insights  ( 1:32 ) - The timesheet app  ( 2:12 ) - Creating an Application Insight for the timesheet application  ( 3:55 ) - Identify and copy the application instrumentation key  ( 4:09 ) - Enabling the timesheet application with the instrumentation key  ( 5:32 ) - Working with Application Insights  ( 8:06 ) - Outro For additional information on Azure Application Insights, please follow these resources: Microsoft Docs - What is Azure Application Insights? here Adam Marczak - Azure for Everyone: Azure Application Insights Tutorial, here To check out my YouTube channel visit: https://youtube.com/user/mgomezb1 LIKE AND SUBSCRIBE!!! Until next post! MG.- Mariano Gomez, MVP
Read more

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics
Read more

eConnect Integration Service for Microsoft Dynamics GP 2010

Image
One of the biggest improvements in eConnect 2010 is the addition of the new eConnect Integration Service . The eConnect installer now creates a new Windows Service application named eConnect for Microsoft Dynamics GP 2010 integration Service . The eConnect Integration Service is a Windows Communication Foundation (WCF) service that replaces the (very unstable) eConnect COM+ object available in previous versions of eConnect. The eConnect Integration Service supports the operations of the eConnect .NET assemblies, the BizTalk adapter, and MSMQ interfaces. In addition, you can use the service directly from an application that adds a service reference to the eConnect Integration Service. If you add a service reference, you do not need to add the Microsoft.Dynamics.GP.eConnect assembly and namespace to your development project. To add the eConnect Integration Service to an application, you must first add a service reference to the Visual Studio project for that application. To add a servi
Read more