SOP Quick Print feature does not work when window ribbons are enabled

Happy New Year!! Hope all of you had a great time with family and friends and that you are back getting used to the daily grind once more.

Today, I want to kick off the year with an issue in Sales Transaction Entry window related to the cool ribbons implemented since Microsoft Dynamics GP 2013 R2. By now, you are probably getting used to the absolutely gorgeous user interface which features Microsoft Office style ribbons on every window. Furthermore, you probably already know that the use of such ribbons is actually customizable and in many ways optional - albeit being the default configuration - as described by fellow Microsoft Dynamics GP MVP, Leslie Vail in her article GP 2013 R2 Ribbons. As it turns out, there's a Dex.ini switch, EnableWCRibbons=FALSE, that controls whether ribbons are enabled within Microsoft Dynamics GP or not. When ribbons are enabled, users can further customize the appearance of the action pane or return to the traditional menu bar for each window.


User Preferences window

Yesteryear (2009), I wrote an article talking about The wonders of CTRL+Q: saving and printing SOP documents in one step and how the Quick Print feature made life easier to the poor souls out there who needed a quick shortcut to printing SOP documents from the Sales Transaction Entry window. In that article I detailed the mechanics behind the feature, written by my good friend David Musgrave.

As fortune would have it, when ribbons are enabled and you are either using the Action Pane or the Action Pane Strip layouts, the Quick Print feature does not work. However, if the User Preference is returned to Menu Bar (you will need to exit Dynamics GP and re-launch for the changes to take effect), the Quick Print option (and CTRL+Q keyboard combination) works just fine.

While clearly an inconvenience, this can hardly be labeled a bug since the feature is still present within the application when the Window Command Display setting is set to Menu Bar as part of the user preferences. It would be nice, however, to have this fixed for Dynamics GP in desktop client mode. I can see how this may or may not work under web client mode as the browser keyboard shortcut combinations take precedence over the application's shortcuts.

Until next post!

MG.-
Mariano Gomez, MVP
Intelligent Partnerships, LLC
http://www.intelligentpartnerships.com/

Comments

Mariano Gomez said…
UPDATE:

This issues has been written up as a Quality Report, # 78140 - GP 2013 R2 New Ribbon missing Quick Print Option in SOP. No resolution date has been set for this as of yet.

MG.-
Mariano Gomez, MVP
January 8, 2015 at 12:02 PM
tracey said…
We have just upgraded to GP 2015 last week. We have always used Quick Print. My quick print works and I am using Action Pane strip. Others are using Action pane and they are not working correctly. Changed one to Action pane strip and then to menu bar (getting out and back in)got the same result. They are printing the right form in the right quantity but to the windows default printer instead of the named printer. Have also imported my machine ID to both.
September 21, 2015 at 4:01 PM
Unknown said…
GP 2013 R2 - if you set the Window Command Display to anything but Menu Bar, you are not able to delete a row from the Purchasing Invoice Entry screen. There is no option on the window to delete a row. If you try to remove the contents of the ITEM field on a row, a popup indicates "you cannot change this item because the information has been save. To remove this item, select Delete Row form the Edit menu." BUT, the Action Pane and Action Pane Strip does not have this choice.
December 16, 2015 at 11:54 AM
Anonymous said…
I have an error that states "please select order or invoice first" when I have a back order pulled up and use the crl+Q command. Has anyone experienced this?

Thanks
February 16, 2018 at 12:27 PM
Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics...
Read more

Do I have to use those "Z-" currency IDs in GP?

Image
I know this seems like a trivia question, but recently I have come across a number of clients who have been using Microsoft Dynamics GP for a number of years and have been told by their former partners that they *must* use the predefined currency IDs created after adding the sample company, with no real explanation to support these claims. Case in point, my new client in Saudi Arabia, has been struggling for years to understand why they were told to prefix all currency IDs with the "Z-". So they went ahead and setup "Z-SR" for the Saudi Real. If you are familiar with Microsoft Dynamics GP and the sample company, Fabrikam, you may have noticed by now that after adding the sample company (which is not a requirement by any means), you will get a number of predefined currencies such as Z-US$ (US Dollars), Z-UK (British Pounds), Z-C$ (Canadian Dollars), Z-AUD (Australian Dollars), and so forth, accompanied by a number of exchange rate tables. If you are not familiar wi...
Read more

Microsoft Dynamics GP Scrolling Windows and Line Sequence Numbers

Image
I thought I would write about something meaningless that no one really thinks about. However, I realized that this is a compelling topic since it makes for some interesting discussion around the ability to insert line items withinin most transaction scrolling windows. Let’s take some time to understand where Line Sequence Numbers come from. A Line Sequence Number is auto generated by Dynamics GP and uses a seed value of 16,384 as a basis for the first line. Each subsequent line in the scrolling window is incremented by this number, so line number 2 would have a Line Sequence Number value of 32,768, line number 3 would have Line Sequence Number Value of 49,152, and so on. Since most GP transaction entry scrolling windows allow inserting rows in between line items, the newly inserted Line Sequence Number value is calculated as an average between the previous and the next line item sequences, i.e., if you were to insert an item in between row 1 and row 2 in the scrolling window -- keep in...
Read more