Windows 10 Creator Update & Dynamics GP


An interesting issue/question was posted on our community forum regarding an error message popping up while exiting GP2015 R2 & GP2016 R2.

Specifically, GP2015/2016 R2 on Windows 10 Creator Update is what seems to be throwing this error while exiting.

Link to original forum post: Windows 10 Creator and GP2015 R2

One member, Ron Koendrink, figured out that it’s Mekorma MICR that’s causing this issue on his environment. Per his update, Mekorma had confirmed that it’s an issue for which a fix was available.

Anyone out there who use Mekorma MICR and planning to upgrade your OS to Windows 10 Creator Update, please contact them and get the fix.

A note of thanks to Ron.

Vaidy

GP2016 DAG Issue


I am wondering whether someone has already faced this issue and has shared his/her knowledge on this.

My issue is with GP2016 VS Tools Dictionary Assembly Generator (DAG), where it takes more than 10 mins to complete generating DYNAMICS.DIC assemblies. Not only that, it also doesn’t generate Application.MicrosoftDynamicsGp.dll in the first attempt itself.

Look at the following screenshot:

Screen Shot 2017-04-28 at 01.29.38 pm.png

First two “successful” attempts of running DAG created only the metadata files and not the actual DLL. I’m running the DAG for the third time, as I write this post.

UPDATE: Third time’s the charm. I am baffled, though.

I have no clue, whatsoever, about why this is happening.

My question(s) to all you guys:

  1. Have you faced this issue?
  2. If so, what did you do to resolve it?
  3. If you have not found any solution (other than running DAG till it creates the DLL), have you already reported this to GP dev team?

Please shed some light on this by sharing your thoughts on the comments section.

Vaidy

Install/Upgrade Error: Input string was not in a correct format


I had to apply GP 2016 YE2016 (16.00.0579) on my GP2016 R2 environment. I had several customisations deployed and wanted to remove them before applying the YE2016 patch.

Obviously, I’d upgrade my customisations to 16.00.0579 once my GP is upgraded. However, while trying to apply YE2016, following error message popped up out of nowhere.

Screen Shot 2017-04-27 at 03.32.02 pm

I had never seen this error before. It was certainly a bit baffling. Not even Google is good compared to our GP community forum to find answers. I came up with this: Installation error ‘Input string was not in a correct format’

Apparently, it was my DYNAMICS.SET that was causing this issue. I removed my customisation dictionaries from GP folder, removed all necessary entries from my SET file. However, I totally forgot to reduce the number of dictionaries at the top of my SET file. Silly me!

Once I corrected my SET file, I was able to apply the YE2016 patch. All was well.

One thing I would like to emphasise here: Those who post questions on our GP forum, please mark the response as “answer” without fail. You would help others who search for an answer. You’d also give due credit to the person who shared his/her knowledge.

Vaidy

GP 2016 Web Client – New Date Picker


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

This slideshow requires JavaScript.

I’m simply enjoying the new GP, to say the least. 🙂

VAIDY

GP 2016 Web Client First Impression – Excellent, yet WIP


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:

  • It’s Fast & Responsive: HTML5 indeed has an extraordinary impact on the web client. It took less than 10 minutes to install and configure the web client (single machine configuration). And it took less than a minute to log on to a company. Absolutely NO PLUGIN dependency. Login was smooth, fast & hassle-free.

Screen Shot 2016-05-02 at 9.17.57 PM

  • Major UI & Accessibility Changes: All the windows have retained the good old GP UI. However, the home page has changed drastically.
    • We have got the new (in)famous hamburger menu. Some people hate it to life. However, I did feel like it’s quite handy. That’s just me. Please don’t ban me from the community for liking it.
    • There is a new way of expanding and shrinking the Navigation Pane. It is quite easy and intuitive to use. If I use GP on a small screen, like a tablet, this would come handy. That’s where the new hamburger menu scores well.Screen Shot 2016-05-03 at 9.17.59 AM
    • That famous pencil button on the home page widgets, that’s used to edit the content of the widget, is no more. It’s been replaced with a “…”, as shown below. It’s probably going to take some time to get used to this. However it’s in the best interest of GP to perform well.Screen Shot 2016-05-03 at 9.21.34 AM
    • All windows are now aligned to “Top-Center” on the browser. I could think of one reason for this behaviour: to ensure that it’s rendered uniformly across all kind of devices. I could see the way GP behaves on the browser, resizing itself quite happily to whatever the size the browser window takes. Below are some rendering:Screen Shot 2016-05-03 at 9.26.07 AM.pngScreen Shot 2016-05-03 at 9.29.31 AM
  • Overall UI Rendering: UI (Home Page and other modules’ home page) responds exceptionally to the browser size. Even the fonts become smaller or bigger depending on how you resize your browser. Below are snapshots:
  • Application Notifications: This one’s brilliant, in my opinion. All application related notifications (such as app errors, warnings, etc) are now shown to users in a non-intrusive manner as shown below:

Screen Shot 2016-05-03 at 8.49.09 AM

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:

Screen Shot 2016-05-03 at 8.49.53 AM

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:

  • Rearranging/moving Windows: This one’s kind of big, however I am not sure if it would be a deal breaker. Remember how we can open multiple windows in GP, arrange them side ways, do some multitasking, etc.? Now that’s probably not possible with the new web client. As you can see below, once a form is opened, you cannot access the home page or module page, until you close the active form:

Screen Shot 2016-05-03 at 9.26.07 AM

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:

Screen Shot 2016-05-03 at 10.00.36 AM

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:

Screen Shot 2016-05-03 at 10.07.08 AM

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

GP 2016 – Upgrading Web Client


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

Time to say Good Bye to OLE Notes


With Dynamics GP 2016, some of the conventional features are going away. One such major feature is OLE Notes. From Dynamics GP 2013 R2, Microsoft made it clear that they wanted to do away with OLE Notes. We got Document Attachment feature.

With GP2015 R2, Documents Attachment cemented its position firmly. We also got a utility namely “OLE Note Migration Utility” that would help us migrate OLE Notes to Document Attachment.

We now have the official word that OLE Note Migration Utility would no longer be provided with Dynamics GP 2016.

Anybody who is using OLE Notes must first migrate to Document Attachment while they are still on current version and then upgrade to Dynamics GP 2016.

More details are posted on the link above.

Good bye, OLE Notes!

VAIDY