#MSDYNGP Extender View Involving Extender Window/Form – Strange “Add Link” Issue & Reason.


Firstly, I am not sure whether I should categorise this as an issue. Let me explain this with an example.

For illustrative purpose, my requirement is to assign an additional information to customers. In addition to Country Code, I would like to assign from which continent a customer is from.

First step; to create an Extender Form named Continent Maintenance in which I will maintain list of continents. I do not need anything information other than an ID (Continent ID) and a name (Name); as shown below:

Snip20140114_1

Note that there are no fields apart from ID and Description.

Second step; I am going to create an Extender Window for Customer Maintenance (Cards -> Sales -> Customer -> Additional -> Continent) to assign a continent to a customer. Extender Window definition is as follows:

Snip20140114_2

Third step; is to check whether things are properly done and confirm. Let me open Customer Maintenance and see if I can access this new Extender information:

Snip20140114_3

Perfect. Let’s now get into the actual issue.

I would like to create a view to retrieve customer continent information. To achieve this, I would like to link Assign Continent (Extender Window) with Continent Maintenance (Extender Form) to get the continent name. Ideally, my view should retrieve following:

Customer ID, Continent ID, Continent Name

Now, when I try to create an Extender View linking my Extender Window and Form, I end up facing below issue:

Snip20140114_4

Snip20140114_6

Did you see that? I do not have my Extender Form fields shown here. I have two fields; Continent ID and Name. Where are they? Why are they not shown here? Shouldn’t it be available for me to link with my Extender Window’s Continent ID?

REASON: If your Extender Form DOES NOT have any other field than an ID and a Description (in my case, Continent ID and Name), ADD LINK To Field will not list out the ID and Description fields.

Is that the actual reason? Let’s confirm by adding another field to Extender Form as follows:

Snip20140114_7

After adding above field, Additional Info., look at my Extender View Add Link now:

Snip20140114_8

Did you see that? They are available now. AFTER adding a field in addition to default ID and Description fields.

And I am not sure how many have ever noticed this. I am noticing it for the first time now. I haven’t created any form with only ID and Description till now. I had to spend 4 hours to identify this reason, honestly. Had no idea whatsoever.

Those who are going to deal with Extender views with form(s) having ONLY ID and Description fields, save your 4 hours. :-)

VAIDY

Delete a Company in Microsoft Dynamics GP – Compatible With GP 2013


We have a SQL script named ClearCompanies.sql, which is available on Customer Source or Partner Source. This script removes all references to those companies that are not available in SQL Server, but pretty much exist in GP records.

It’s an all important script for all implementers, developers and consultants. Now this script has been updated to cater for also GP 2013. I had not used this script for a long time, so never realised it till today. This is particularly important as GP 2013 now support multi-tenant architecture (multiple GP System DB on same SQL instance).

You can download this script from here (provided you have a Customer Source / Partner Source account): ClearCompanies.sql.

VAIDY

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

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