Just a quick post on the new HTML5 Web Client date picker control. It’s visually pleasing and quite easy-to-use. IT’S AWESOME…
I’m simply enjoying the new GP, to say the least. 🙂
VAIDY
Just a quick post on the new HTML5 Web Client date picker control. It’s visually pleasing and quite easy-to-use. IT’S AWESOME…
I’m simply enjoying the new GP, to say the least. 🙂
VAIDY
Yesterday, 2nd May 2016, was a great day for the entire GP community. GP 2016 was released and needless to say, it’s awesome. Unexpectedly stable for an RTM release.
Gone are the days when people used to fear about the RTM version, anxiously waiting for someone to find bugs, for Microsoft to release hotfix or a service pack and then implement/upgrade.
After playing around for good amount of hours on both rich client (read as desktop client) and the newly developed web client, I can assure you that GP2016 is ready, raring to go and can be implemented right away. Well, that’s just my opinion.
There are some great things about the new web client:
When I click on that “Details” button, I get the following message that could be dismissed and I continue with my work without crashing GP:
So, as you can see, I have already got my first web client error in GP 2016 Web Client. However, I don’t think it is worrisome. I do believe I know why that error was popping up, so all good.
Now let’s talk about some issues, that in my opinion is a bit worrisome:
As you can see, the background to “Debtor Maintenance” window is greyed out. I cannot move the active form either. You would however be able to use the windows that originate from “Debtor Maintenance”, such as “Payment Terms Setup”, as shown below:
However, you won’t be able to open a totally different form/report, such as Smartlist. In fact, unless you close the “Payment Terms Setup” window, you won’t be able to use “Debtor Maintenance” back.
In a way, this is great. You would maintain the sequence of your tasks. But if you are someone who would love to enter a PO and an SO simultaneously, I am afraid you are gonna get pissed off with the new web client.
You cannot also move windows from “Top Centre” position. Even if you try to do that, it’s probably going to be like below:
Yeah, well, it’s just that the window looks like nothing more than a web page and when you try to drag the window, it considers that you want to select content and thereby above rendering.
I would probably not panic about this. Whole idea of this new web client is to provide an app client that would work well across all kind of devices. If I access GP on an iPad, I won’t be worried about rearranging the windows or multitasking. I would be more concerned about how quickly could I complete my tasks and how easily I can work on.
I still have to play around a lot, however, these are my first thoughts about the new GP2016 HTML5 Web Client.
GP Team has done an excellent job to rewrite the web client. Considering this being the first ever HTML5 web client version, I totally believe that this is only gonna get better with every release.
Hats off, GP Team. Keep up the good work and continue to amaze us.
VAIDY
Dynamics GP Support & Services team has posted a detailed article on GP 2016 Web Client Upgrade.
One of the important things that I noticed on this post is the instruction on Service Based Architecture (SBA) inclusion/exclusion. Though it’s not covered separately on this post, we are however cautioned on how to handle the options with regards to SBA.
Happy upgrading…
VAIDY
Excited to see the “All-In-One Viewer” being extended for all modules. After sales, inventory has got its own AIO viewer.
Perhaps the most important feature that I am excited about, in addition to HTML5 Web Client, is the ability to add a Project to Purchase Requisition Entry. This was sorely missed by many of the customers. I am glad this feature made it to GP2016.
Read the “feature of the day” posts here:
VAIDY
Continuing from the first feature, we have got Web Client Search & Sales AIO (All-In-One) Document Viewer.
I am quite interested in the second one; Sales AIO Document Viewer. This would be more helpful, in the lines of already available Purchasing AIO Document Viewer.
Web client search is another great feature that would help us a lot. It may not sound a great functionality, but how many times have you tried to find out where a window/report is? How many windows/reports that you know by heart, that you would not require a help to find one?
However, I am interested more to see if this would work for ALL windows/reports. Theoretically, it does sound like it would. I would love to see if that works for all resources; standard/ISV/customisation windows/reports.
Let’s wait for the release to know more.
VAIDY
Pam has started the GP2016 Feature of the Day series with the most anticipated feature: GP HTML5 Web Client.
Let’s prepare for the party time!
VAIDY
In my earlier post, I discussed about an issue that I came across while installing web client. This one’s while uninstalling the web client.
My VM is added to my work domain and when I installed web client, my VM was connected to my work network. Back at home, in my holidays, I was experimenting with various stuff. Got my VM web client corrupted and decided to uninstall it.
Running the web client uninstall started off properly but threw the following error soon after:
You may see the point in time at which the uninstall process stopped: ConfigureUsers.
Tried various things, as usual, but could not fix it. Every time I tried to uninstall, it stopped exactly at ConfigureUsers.
My instinct was telling me that it was something to do with domain network issue. As I was trying this at home, it could probably be something related to that.
I connected to my work VPN and then restarted the uninstall process. This time around, the process went on smoothly and completed.
Remember. If your machine (or a VM) is affiliated to your work domain when you installed the web client, make sure that your machine (or a VM) is connected to your work domain when you try to uninstall.
This makes a world of difference. You do know what that difference is, by now.
VAIDY
I have been doing some R&D with GP2015 (Desktop & Web Client) on my virtual machine for almost a week now. On that note, let me share with you one particular issue, that’s a bit silly, yet possible to be faced by many of you out there.
I had a working instance of GP 2015 Web Client on my VM (that’s connected to my work domain). I uninstalled it due to an SSL conflict with local web site. Uninstall went on smoothly.
I worked on that local web site stuff and decided to install web client back. When I began the installation, following error message happened:
I had no idea about this port, as this port number was never used while setting up the web client installation. I am not an expert in networking either. So googled this error and got this link on Microsoft Support KB: How to determine which program uses or blocks specific transmission control protocol ports in Windows.
I used the command netstat -ano to figure out which process is using the port 48665. Below is the list that I got:
Highlighted on RED box is the one that was using the port 48665. This process was System Process, as found through Task Manager:
Well, only to that extent could I proceed. My instinct asked me to restart the VM once and see if that clears this port. And it did.
And my web client installation went on well and completed without any issues.
Reason: After uninstalling my Web Client earlier, I did not restart my machine. I continued with the local web site task and tried to install Web Client again. Previous installation would have held that port (just my assumption) and did not release it till I restarted my VM.
Resolution: If you are going to install Web Client, just make sure that you restart the server.
On my next post, I shall discuss about an issue that I faced while uninstalling my web client and the resolution to the same.
VAIDY
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:
Consider, for instance, the following snapshot of GP login window on a web client rendered on Mac Safari:
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:
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
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:
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:
There could be several other reasons for this CrossDomainError issue, but above solution fixed mine.
VAIDY