Microsoft Dynamics GP: Homepage Script Error

Hello everyone,

I've noticed a recent trend of environment with several different versions of Dynamics GP being installed on a single workstation/server, typically those wanting to test and explore newer version of Dynamics GP along side their older version production Dynamics GP.

Some may notice that user receiving an error message similar to the one below, when user logs in and being presented with their homepage; especially when two drastically different version of Dynamics GP (for example GP 2010 and GP 2018).

Given the broad changes between operating system and Dynamics GP dependencies, we no longer recommend having multiple version of Dynamics GP being installed on a single workstation/server.

This error in particular is due to the different versions of web content being loaded as part of the user home page and Internet Explorer Web Browser component utilized in Dynamics GP and the Web Browser component Browser Emulation settings.

Since the information I am providing is relevant beyond the user home page (Power BI script error on Dynamics GP user home page *1), I am providing a workaround for this issue.

As I have mentioned above, any web content loaded on the user's home page in Dynamics GP utilizes the Internet Explorer Web Browser component and therefore behaves mostly identical to Internet Explorer including browser document mode emulation/compatibility view mode.

This is to allow certain legacy web pages to load and display correctly on newer version of Internet Explorer. By default, this would be set to Internet Explorer 11 mode. 

For example, Web content loaded on Dynamics GP 2010 requires this to be set to IE 7 mode and one for Dynamics GP 2018 to be set to IE 10 or newer.

This can be changed and over ridden on Internet Explorer by pressing F12 and opening the Developer Tools and changing the settings in the Emulation tab.

However, user will not have access to this tool from within Dynamics GP. So instead, this is set using a registry key under:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION\

Entry is made based on the programs executable name, in Dynamics GP's case would be Dynamics.exe, and the value would set to one of the ones below.

This also means that a single value would be shared between multiple version of Dynamics GP.

Dynamics GP 2010 would have set the value to 0x1b58 during installation, since the web content loaded is meant to be loaded on IE 7 mode.

When a newer version of Dynamics GP is installed (for example Dynamics GP 2018), this is changed to 0x2710 for web content meant to be loaded on IE10 mode. This in place causes an issue with Dynamics GP 2010, since the web content is no longer loaded in the correct mode.

To work around this issue, you can perform the following steps:

1. Set the value back in the registry to 0x1b58.
2. Create a new entry for Dynamics2.exe and set the value to 0x2710.
3. Rename the executable in the newer version of Dynamics GP to Dynamics2.exe.
4. Update the shortcut to the newer version of Dynamics GP to Dynamics2.exe instead of Dynamics.exe.

This will allow the two version of Dynamics GP to have their own version emulation mode set.

*1 PowerBI encounters a script error on Dynamics GP homepage due to emulation mode being set to 0x2710. It should be set to 0x2AF8 instead. https://community.dynamics.com/gp/b/dynamicsgp/archive/2018/04/25/getting-started-with-power-bi-and-odata-in-dynamics-gp