Are you a Tab or Enter kind of person

Tab or Enter?

Navigation from field to field on a form in Microsoft Dynamics GP can be performed using the [Tab] key, or if the option has been set the [Return] key on the keyboard.

A quick internet search reveals this ability to change field navigation preference is a standard feature of software such as; Quickbooks, Xero, Quicken, and no doubt most of the other similar products too.

TabEnter

When creating an add-in form for Dynamics GP, don’t forget to support this unless you want user backlash.

Green screen, serial terminals

The first ERP system I used was literally a green screen application, you didn’t have a mouse, instead function keys allowed you to quickly jump around the screen functionality. Navigation from field to field was achieved by pressing the enter key repeatedly until you were at the field you wanted to edit. The field content is then changed and press enter again. When the windows operating system came along, the Tab key became the standard navigation field for moving between fields on forms. My thoughts are that, for those still hard wired in their heads to use Enter key from non –graphical user interface applications, software vendors still supported this, to help the user in the transition to the application running on windows. Perhaps green screen allowed the tab key back then too, I’m unsure, I, like others just used Enter!

Whatever the history is, in GP we can, in the user preferences set this. 

2018-09-13_16-41-12

I personally have not used Enter as an option since using GP, but curiosity got better of me…

If i query this preference for all users, to find what the users are using, i find,

SELECT COUNT(*)
,CASE
WHEN MDFRDENT = 0
THEN 'Tab'
ELSE 'Return'
END
FROM DYNAMICS..SY01400
GROUP BY MDFRDENT
 
Results:
Count Setting
122 Return
59 Tab

Looking at the figures, it seems users prefer to use the return key. This might not be the whole picture, many users may not even realise they can change this preference, the user default in our case set to Return. Tab is the windows default for navigation, so are we setting our users up for digital failure in their lives outside work, where they find they can’t use the Enter key? For example, on the internet, in browsers, we find that the Enter key will normally submit a form.

Behaviour

There is data saying that only 10% of regular (non geeks) tab between forms, the sad truth is the rest leave the keyboard, grab the mouse click, then return to the keyboard. [1] Even worse studies show that users arriving at a form, even though the cursor is blinking in the first form field that they want to fill, will still grab the mouse and set focus on that already focused field before typing -ugh!

It seems that the standard user just doesn’t value speed or ease in their interaction with the device they spend most of their day in front of. Most of us know users will rarely invest the time up front to learn how to use an operating system/application properly, even when it could vastly improve their efficiency, they just don’t value it.

The keyboard power user

While we are talking about this kind of thing, there is another kind of user worth mentioning, rare to find but amazing to watch in action. In my experience, they tend to be an older user, brought up on green screen technology. These users don’t leave the keyboard, in fact they raise a big sticking objection if the form tab order is not correct and if they can’t do everything without the mouse and with shortcut keys or key chords. These users use the application like they are playing a familiar song on the piano, using muscle memory to enter data a lightning speed, without taking a breath (grabbing the mouse).

Enter vs Return key

After all that we remind ourselves that the Enter key and Return Key are actually two different keys that once did different things, look at your numeric key pad for enter and big button for return…

GPUG Summit 2018 Phoenix Arizona–October 15-18th

If you are into Dynamics GP, Power BI, then head over to GPUG Summit summit this October in Arizona – even better, bring your “IT crowd” too!

 GPUG Summit Site Phoenix, October 15-18, 2018

This event has over 215 GP –specific sessions and a separate parallel conferences going on “under the same roof” for business central and Power BI. There will be lots of ISVs and networking opportunities in the expo hall and corridors.

Session listing can be found here for the four conferences:

(Power BI) PowerBIUG Power Summit

(D365UG) AXUG Summit

(Business Central) BCUG Summit

(Dynamics GP) GPUG Summit

CRMUG Summit

 

It is difficult to emphasise enough the value that can be found in attending this nature of event, with a world class concentration of expertise in the Microsoft Dynamics products housed in the same place for a week. There is a strong sense of community and endless opportunities to get the answers to long held questions, or discover new products and features that you never realised existed. This knowledge could be priceless when brought back to the workplace after the event.

Lots of practical sessions are available on how to better utilise the investment you have in your company systems. This includes discovering the tools you didn’t even realise you already had at your fingertips. Notably, this year there is a real growth in the developer and IT pro tracks – so not only will the accounting, purchasing, warehousing, sales, admin employees find value in attending, now the IT crowd can come along and there will be lots for them to get their teeth into too.

Have you ever considered how much more could be achieved in your company by growing a better understanding of the financial systems that drive the business,  by getting buy in and understanding from your IT support staff and developers? Trust me, once they see the kind of things that are possible from the exhibiting companies and from the technical sessions, they will return enthused and ready to help facilitate change, perhaps brining in improvements (great and small) for everyone! –my message is simple, BRING YOUR IT CROWD TO SUMMIT 2018!

  • Newly released Microsoft Dynamics G 2018 R2 (October 1st) will be in action on stage and within sessions
  • Meet new peers, reunite with existing friends and mentors within the GPUG community
  • GPUG Medics will be onsite and available all week to talk you through your unique GP challenges
  • BI track for Power BI you can attend Power Summit sessions at NO additional cost

See my write up of the 2016 Summit in Tampa for an example of what to expect.

As a bonus I will be presenting two sessions, so see you there!

Docker build and UilttiuyVM: The parameter is incorrect - Failed to regis error

The following error can occur when doing a Docker build.

Docker image

Docker . failed to register layer: re-exec error: exit status 1: output: processUtilityWImage

\\?\C:\ProgramData\docker\windowsfilter \UtilityVM: The parameter is incorrect.

At line: 2 char: 1

+ Docker build - -tag tw/gp2018 .

+ CategoryInfo :NotSpecified: (failed to regis…r is incorrect.:String) []. Remote Exception

+FullyQualifiedErrorId : NativeCommnadError

 

On a windows build, this is often due to the base image not being compatible with operating system of the Docker host machine.

For example, I moved my dockerfile and build directory from Windows 10 to Windows Server 2016 and experienced this error.

Turns out that the windowscore I was attempting to use was not compatible.

See here https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility for the guide on the windows container versions compatible with different hosts.

dockercompat

I was attempting to use microsoft/windowsservercore:1803, but the only version that is compatible on Server 2016, from the above table, without using Hyper-V isolation (where a small Linux machine is used to host container), is build 14393.

Thus in my dockerfile, changing the base image instruction to

FROM microsoft/windowsservercore:ltsc2016

solved the above error on the server host.

The reason is obvious really, Docker works by sharing the underlying kernel from the host with the containers, overlaying layers of files until you reach the image. Changes to the host operating system will adversely affect this layering, as expected components may not be present that were there when the image was created. The container my start but fail later.

Using Hyper-V isolation works, as the Hyper-V isolation introduces its own kernel instead of the host’s thus isolating the container from the host operating system. This still gives us benefits if multiple containers are ran, and the benefits of portability are still present, but less efficient on disk storage. Use the switch parameter –isolation=hyperv to enable this isolation.

Installing Docker onto Windows Server 2016

 

https://docs.docker.com/install/windows/docker-ee/

Docker comes in two editions, free community edition and enterprise edition.

The company Docker and Microsoft entered into a commercial agreement to bring Docker to windows server as a commercially supported container enterprise product.

Docker running containers on Windows is the result of a two-year collaboration between Microsoft that involved the Windows kernel growing containerization primitives, Docker and Microsoft collaborating on porting the Docker Engine and CLI to Windows to take advantage of those new primitives and Docker adding multi-arch image support to Docker Hub. (https://blog.docker.com/2016/09/dockerforws2016/)

 

 

As a result of the agreement Docker Enterprise is already licenced as part of Windows Server 2016. So you just need to install and use it!

 

There are two types of containers, Linux and Windows. To run Windows OS containers, you must install the windows provider. Choose the appropriate container type below and issue the relevant commands.

For Install for Windows containers:

Install-Module -Name DockerMsftProvider -Repository PSGallery -Force

Install-Package -Name docker -ProviderName DockerMsftProvider

For Install for Linux Containers:

Install-Module DockerProvider –Force

Install-Package Docker -ProviderName DockerProvider –Force

 

When installed there will be a Docker Service on the machine:

Docker Service

When the command has finished executing (can take some time), then powershell should be aware of Docker commands. Thus issuing the following command:

Docker version

will return information about the Docker version.

Docker Version

 

Uninstall docker from Windows Server 2016

Uninstall-Module dockerprovider

Uninstall-package docker

or for windows container:

Uninstall-Module DockerMsftProvider

Uninstall-package docker