One of the great things about D365 being browser based is that you can also use the browser’s hotkeys. In both Chrome and Edge, Ctrl+F can be used to search a website. I find this is especially useful when searching for menu items buried deep in a module.
Browser Search Power User Tips
Crtrl+F to find menu items (or other text on page)
On any D365 form, users have the ability to right-click and “View shortcuts”. This brings up a display of all the shortcuts available for that given form, as well as a link to the full list of D365 Keyboard shortcuts.
It’s faster to navigate computer systems with a keyboard than with a mouse. But while the point-and-click of a mouse is intuitive, keyboard navigation has to be memorized and internalized.
I’ve heard stories of managers ripping out the mouses of new investment bankers, forcing them to learn model building completely through excel hotkeys. But there’s no need to boil the ocean. Picking up a tip here and there can, like compounding interest, lead to significant improvement in the user experience over time. Also like compounding interest, we probably underestimate the cumulative value of all these small improvements.
With that in mind, I’m starting Hotkey Highlights* a series of blog posts on simple keyboard tricks that can improve the D365 navigation experience. I hope you enjoy! Subscribe if that’s content you’re interested in – and let me know you have any favorite navigation tips of your own.
*After some research, I realize that “hotkeys” are actually a very specific type of keyboard shortcut, and most of these shortcut tips will not in fact be “hotkeys” in that sense. I briefly considered renaming this series “Shortcut Showcase”, but after some soul-searching decided I did not love that alliteration as much. If this technicality somehow offends you, feel free to reach out and I will happily refund your blog subscription.
In D365, personalizations enable users to Hide, Add, or Move fields on a given form. A Saved View can best be thought of as a set of personalizations, and saved views allow users to toggle between multiple sets of personalizations.
New users of D365 are frequently overwhelmed by the volume of fields and buttons available on every form. Saved views provide a way for users to pare the number of fields displayed in their day-to-day tasks, while still giving them access to the extra functionality should the need arise.
Saved Views – How are they enabled?
As a preview feature, there is a line of SQL code needs to be run to enable their flighting. More information can be found here:
Saved Views – How do they work?
When enabled, all forms now start in a standard “Classic view”:
If a form is modified through a personalization, the Classic view gains a Barry-Bonds-like asterisk. The asterisk indicate the form has been enhanced:
By clicking on the view button, the user now has the ability to save this as a new view:
The user can now name this new view, as well as decide whether to make this the default view every time the form is accessed.
Clicking the view button, this new view is now a new option the user can select for how the form is presented. The user always has the option of clicking back to the Classic view to see the standard presentation of the form.
That’s Great! What Else?
Saved views can be used for personalizations (adding, moving, hiding fields). Saved views can also be used for the sorting/filtering of columns. This is a huge extension of the form personalization capabilities.
Additionally, saved views can be published and shared at the role level bringing the management of personalizations much more in light with security management. I’d like to do another post on the sharing of views, as well as a video digging deeper into applications for shared views, but those will have to wait for another day.
I just arrived home from this year’s User Group Summit, what a great experience! So many great presenters and amazing sessions. I especially want to thank those of you who attended my own session on workspaces and personalizations. It would have been significantly less fun had you not been there – and I think we all learned a lot!!!
There were several requests for the additional presentation slides, so I am posting them here. Please feel free to download them by clicking through to SlideShare, and do share them widely.
I plan to do a series of blog posts in the upcoming weeks that will dive deeper into some of the session’s topics, so enter your email address into the subscribe box on the right if that is content you’d find of interest.
Handling rejection can be tough. Understanding D365 workflows can be tough. So understanding how rejection is handled in D365 Workflows can be, well, trickier than a freshman getting a date to senior prom.
My high school guidance counselor taught me experiencing
rejection makes us more complete people.
When setting up Dynamics AX workflows, it is important to test the approval process. But testing is not complete until the rejection process has also been examined. Testing rejections can be much more complex because workflow behavior needs to be examined for rejection and resubmission at each stage of the workflow. Below is an example of why this is important.
Let’s consider two expense report workflows below. Each uses a multi-level approval where an accounting reviewer approves for correctness (eg “Is the math right?”), and then an Expense reviewer approves for appropriateness (eg “Should this have been expensed?”). The workflows look similar, the rejection behaviors have an important distinction.
Dynamics 365 for Finance and Operations has powerful enhancements to the task recorder functionality. Particularly the ability to save task recordings specific processes in the Business Process Modeler of Lifecycle Services.
Task Recording Setup
Saving task recordings to LCS is a great
way to confirm testing of business processes, as well as create clear
documentation that is easily available to all system users through Task
recorder’s “Open from Lifecycle Services” playing functionality
To do this, however, it is first
necessary for each user’s system to be linked to LCS.