Navigation List Builder not redeploying changes to a previously saved list

During the Drill-Down Builder and Navigation List Builder training session (for class materials, click here) I held at GPUG Academy Training Day 1 in Las Vegas, prior to the GPUG Summit, I found that Navigation List Builder had an issue redeploying changes done to a previously created and saved navigation list. In reality, this issue came up days before when I was preparing the class, but I really did not give it much thought and attributed the problem to an 'environmental' issue on my machine. The Microsoft Dynamics GP version is 2010 R2 (11.00.1752).

One of my students saved his navigation list to the wrong series and deployed the list. All things worked, except the navigation list was showing up under the Financial bar, instead of the Sales bar where it should have been saved to initially.

Navigation List Builder - list saved to the wrong series
Upon realizing the miscategorization of the list, the student returned to Navigation List Builder to make the proper adjustments and set the navigation list appear under the Sales bar. Easy feat, right? Sure was! After saving the changes to the navigation list, the typical deployment window flashed.

The student then proceeded to click on the Sales navigation bar and did not see the navigation list he had created. He then clicked on the Financial navigation bar and nothing showed up. In essence, the list was gone.

Returning to Navigation List Builder, we could retrieve the List ID we created. However, after adding a few new columns and saving to redeploy, we were not able to see the list on the Sales navigation bar. Finally, after a few trial with no success, we decided to delete the navigation list and recreated with the same name, this time, saving to the Sales navigation bar (as originally intended). This time, the new list displayed just fine.

There are a few more things we did not test, so consider this a limited scenario. Other things that could be tested include saving a navigation list to the correct bar, then return and add some changes after the initial deployment, though I suspect this problem would have manifested itself in the support archives pretty quick.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Comments

Kumar said…
Yes buddy... Looks like a bug. I was able to replicate the same too!
November 15, 2011 at 8:49 AM
Mariano Gomez said…
Thanks Siva for confirming!

MG.-
Mariano Gomez, MVP
November 15, 2011 at 9:37 AM
DTM Michael said…
Can you confirm there are still problems with the printing and email actions in nav list builder.
The Print Sales Document action is limited to calling the Print Sales Document window, not like the functionality in the 'canned' Sales Order Transactions nav list. I am also now finding that the print picking ticket and packing slip actions do not filter on my selections within the navigation list and prints all documents.

This is a bug along with the known Print Sales Documents and email functionality not working in the currect release of nav list builder?

Thanks for your feedback.

M. Smith
DTM System Corp.
Vancouver, Canada
April 5, 2012 at 7:13 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