Missing Navigation Nodes

JavaScript is disabled. Strange things can happen.

Answered

Hello!

I recently upgraded to the latest version of the sdk (2.305.0), and I am trying to test some of our extensions. When I run the command q2 add_to_nav, I'm not seeing all the expected navigation nodes. This is the output I'm getting:

Which Navigation Tree would you like to use?

1) UUX
2) UUX_NavLandingPages

Please make a selection and press Return [1]: 1
UUX

Which menu should this nav node live under? (Leave blank to insert at top level nav)
--Online Top Level Navigation Menu--

1) Transactions
2) Commercial
3) Services
4) Settings

I am expecting quite a few more especially with developer names. I did try running q2 setup_db, which completed successfully. Am I missing another step? I did also run q2 db get_nav_nodes and I can see the correct nodes there.

		
				0
				
Posted 
	9 months ago

					⠿More
				  		
			 Report
		
					Jenny Johns
				
					13
 × 3

Votes Newest

Answers 3

Hello Jenny,

We recently made a change to try and prevent you from adding an extension under a nav node that is not intended to be one used as a drop down. Maybe that is what you are experiencing? I would also double check your q2 inspect details to see if that looks correct.

What are you trying to accomplish that you can't?

-Trey

		
				0
				
Posted 
	9 months ago

					⠿More
				  		
			 Report
		
					Trey Teter
				
					489
 × 4
					Administrator

Hi Trey! Thanks for the response back! In the sandbox env I have a Navigation Node with my name, I wanted to add the extension I've installed under that node. But when I do the add_to_nav command, the navigation node with my name is not present. q2 inspect all looks correct to me.

— Jenny Johns 9 months ago

Hi @<1549423964604862464|Paden Rose> we spoke at the office hours yesterday, but the meeting got cut off before I could completely read what the solution was. I think it was just that "Route" for that navigation node should be set to <null> is that correct? A few follow-up questions, is this new to the upgrade? And should I be concerned about it as we move this change from dev to master and prod? Will this affect navigation there as well? Thanks again for your help!

		
				0
				
Posted 
	9 months ago

								Edited 
	9 months ago

					⠿More
				  		
			 Report
		
					Jenny Johns
				
					13
 × 3

Hi Jenny,

As confirmed with Paden Rose, after aproximately release v2.277 of the SDK, navigation nodes in your sandbox environment work as follows:

ParentNavigationNodeID in the Q2_NavigationNode table determines where a node appears in the heirarchy of the navigation tree. This means that if ParentNavigationNodeID is Null it will appear as a top level node.

Next, the Route attribute also in the Q2_NavigationNode table is what determines where that navigation node routes to.

If the Route attribute is set for a top level node, that node will effectively function as a button which navigates to that Route.
If Route is NULL then the top level node may act as a parent to other navigation nodes and manifest as a dropdown.

When you use q2 add_to_nav and are asked "Which menu should this nav node live under?", the list of menus it presents is actually just other nodes which have ParentNavigationNodeID = NULL and Route = NULL.

To allow your navigation nodes to be used as parent nodes, find the Q2_NavigationNode record corresponding to that node and set the Route attribute to NULL.

In your case you can do this for each of the developer names that should have their own navigable section.

-Ash

		
				0
				
Posted 
	9 months ago

					⠿More
				  		
			 Report
		
					Ash Mitchell
				
					50
 × 1

Write your answer

103 Views

3 Answers

9 months ago