GP Web Client: Rendering Issue – Some Facts


Almost a month back, I had posted my GP web client test drive results on how the client is rendered on Mac based browsers and possible issue with Silverlight plugin. I am probably wrong.

Everything works other than pictures; that’s what I had found. Upon drilling down further, what I realised is that it sounds obvious that it doesn’t work on Mac based browsers. Reason: Native Pictures.

Definition of Native Picture says following:

Snip20131230_12

Consider, for instance, the following snapshot of GP login window on a web client rendered on Mac Safari:

Snip20131230_10

It’s not shown. Initially I thought it was something to do with Silverlight rendering. But not exactly. It’s because, this picture is a Native Picture. And by definition, it’s specific to Windows OS. Look at this picture definition below:

Snip20131230_9

Apparently, by nature, it’s NOT supposed to show up on any OS other than Windows.

It’s not just this picture. Lookup Button icons, Note icons are all Native Picture types. And due to that, they are not going to render on any other OS. And if I am not mistaken, this will remain as it is at least till next major version of GP.

Those who implement GP web client MUST be aware of this.

VAIDY

Advertisements

GP 2013 Web Client – Cross Domain Error


This probably would be a common error faced by many of us across the GP world, while trying to access GP 2013 Web Client.

Upon launching GP web client on my browser, it asked me to enter my domain credentials and once I did that, I was greeted with following error:

Snip20131209_5

 

Complete error message is as follows:

Severity: Critical
Summary: An error occurred while initializing communication with the server.
Details: [CrossDomainError]
Arguments: https://<machine name>.<domain name>:48652/RuntimeService/5652
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20913.00&File=System.ServiceModel.dll&Key=CrossDomainError

Reason is quite trivial; I had entered the url on my browser as follows:

https://<machine name>/GP

Instead, I should have entered the url on my browser as follows:

https://<machine name>.<domain name>/GP

For instance, if my GP web client server name is GPDEV and my domain name is GPDOMAIN.COM, then I should enter my url as follows:

https://gpdev.gpdomain.com/GP

There could be several other reasons for this CrossDomainError issue, but above solution fixed mine.

VAIDY

GP 2013 Web Client Rendering on Mac OS Based Browsers


We all know GP 2013 Web Client is rendered on Silverlight. Though Silverlight plugin is available for Mac based browsers, rendering is not same as how it is rendered on Windows based browsers.

Below are some samples:

Windows IE:

Snip20131205_13

 

Mac OS X Safari:

Snip20131205_14

 

Windows IE:                                               Mac OS X Safari:

Snip20131205_15                     Snip20131205_16

Windows IE:

Snip20131205_17

 

Mac OS X Safari:

Snip20131205_18

Apparently, there seems to be a rendering issue on showing pictures (and ONLY that I guess).

On the surface, it seems like Silverlight doesn’t render properly on Mac based browsers, while it could work perfectly on Windows. Thinking on this further, it’s only related to images. There could be something that we have to tweak on Silverlight plugin. Not sure what it is exactly at the moment.

Those who have implemented Web Client for customers with Mac, would you please step forward and shed some light on this?

VAIDY

 

 

GP2013 Web Client – Test Drive #MSDYNGP


It’s been an awkwardly long time since I had written anything on this blog. Now is the time probably to break that jinx.

I have been working on testing GP2013 Web Client on our environment. I have been constantly keeping myself updated with GP Web Client by reading our community blogs and forums, but never had seen it on my own machine till today.

Below is the snapshot of GP2013 Web on my MacBook Pro; on Mac OS X Safari browser.

Snip20131202_4

All you need to do is to install Silverlight for Safari on Mac. If it’s not there, you would be prompted to download and install.

I am now excited to get my customisations work with it. Will post anything that’s interesting and worth to be shared in coming days.

VAIDY

GP2013 – Purchase Invoice Inquiry Zoom Bug (Change)


I received a strange support request today from one of my users that PO number is not shown fully on Purchase Invoice Inquiry Zoom window. Just tried to inquire some purchase invoices myself and I got what she mentioned:

Snip20130807_12

 

If you see above highlighted PO number, it’s not shown fully. This will be the case only if you use GP’s standard PO number sequence or used entire PO length of 17 characters.

When I checked it on Modifier, I found a nice little icon sitting right next to PO number field, but overlapping it by some millimeters.

Snip20130807_11

This icon denotes whether the PO line item is Drop-Ship or not.

And boy, isn’t that icon looks cute? But unintentionally, it is overlapping on PO number field. Not sure how folks at GP dev team skipped this.

Solution to this issue? Modifier. Use modifier to resize the field, till we get this fixed by GP dev team.

VAIDY

syExcelReports Table & SQL Server Native Client 10.0 – Thanks Aaron Berquist


While upgrading our GP from GP2010 SP3 to GP2013 SP1, DYNAMICS database upgrade stopped unexpectedly with GP crashing without any information for me to debug.

But it stopped exactly at table syExcelReports and crashed. Without spending anymore time, I just went and checked my ODBC DSN setup, as explained by Aaron Berquist on his blog High Dynamics Range. Expectedly, the ODBC DSN driver was not pointing to SQL Server Native Client 10.0.

For some reason, GP fails to process upgrade further if your DSN driver is NOT native client 10.0 or above.

Those who upgrade your GP to latest version, please check DSN before you start database upgrade using GP Utilities.

VAIDY

Quick Tip: Debugging Visual Studio Tools – Developing For Dynamics GP


Awesome tip up there on Developing For Dynamics GP blog on how to debug VS Tools For Dynamics GP.

I am late in blogging about this post. But NOW is the time, as this post just saved my 1/2 day. Seriously. Not kidding. I was stuck with one SQL query execution. There were records to be retrieved, but my code didn’t. After 5-10mins of frustrated troubleshooting, I remembered this post. I should have done that immediately then, but I didn’t.

I setup my VS Tools project to launch GP as instructed on this post and within 2 minutes I could find the issue.

This one deserves to be there on Microsoft Dynamics GP Cookbook (technical).

VAIDY