SOLVED
Home

Structured Navigation (Publishing) not supported on "Modern" Sites/Pages/Lists/Libraries

%3CLINGO-SUB%20id%3D%22lingo-sub-8486%22%20slang%3D%22en-US%22%3EStructured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibraries%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-8486%22%20slang%3D%22en-US%22%3E%3CP%3ECreating%20a%20dedicated%20post%20to%20track%20this.%20%26nbsp%3BLots%20of%20discussion%20on%20this%20from%20Yammer%2C%20and%20havent%20really%20seen%20this%20anywhere%20here%20yet..%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EWhat%20is%20the%20status%20of%20new%20%22Modern%22%20capabilities%20to%20support%20structured%20navigation%3F%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20structured%20navigation%20gives%20us%20today%3A%3C%2FP%3E%3CUL%3E%3CLI%3EDedicated%20navigation%20page%3C%2FLI%3E%3CLI%3EMenu%20items%20can%20be%20permissions%20limited%20by%20groups%3C%2FLI%3E%3CLI%3EVisual%20interface%20to%20easily%20move%20up%20%2F%20move%20down%20%2F%20create%20folders%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20years%20we%20have%20had%20users%20leverage%20this%20navigation%20structure%2C%20because%20it%20was%20easier%20for%20them%20to%20%22grasp%22%20and%20the%20extra%20features%20that%20you%20dont%20get%20with%20just%20the%20regular%20navigation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERight%20now%2C%20we%20have%20almost%20500%2B%20sites%20that%20leverage%20structured%20navigation.%20%26nbsp%3BWe%20have%20also%20as%20an%20organization%20put%20real%20emphasis%20on%20the%20Top%20Global%20Navigation%20menu%2C%20and%20not%20as%20much%20on%20the%20Left%20Side%20Navigation%20menu%20(which%20%22Modern%22%20seems%20to%20really%20key%20off%20of).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20one%20of%20the%20items%20keeping%20us%20from%20moving%20toward%20the%20modern%20UI%2C%20so%20we%20dont%20have%20to%20go%20redesign%20the%20navigation%20of%20every%20site%20just%20to%20fit%20into%20the%20new%20modern%20world.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20we%20have%20to%20bite%20the%20bullet%20and%20just%20touch%20every%20site%20to%20make%20it%20fit%20in%20modern%2C%20it%20would%20also%20be%20nice%20to%20know%20that.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-200868%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-200868%22%20slang%3D%22en-US%22%3EYes%2C%20they%20are%20gone%20now%20this%20end%20too.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-200863%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-200863%22%20slang%3D%22en-US%22%3EYeah%2C%20had%20those%20boxes%20as%20well%20in%20the%20last%20couple%20of%20days%2C%20not%20sure%20why%2C%20but%20they're%20gone%20now.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-191826%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-191826%22%20slang%3D%22en-US%22%3E%3CP%3EPlus%20one%20for%20faster%20appearance%20of%20menu.%3C%2FP%3E%3CP%3EOr%20at%20least%20let%20the%20menu%20appear%20when%20the%20header%20is%20selected.%20Currently%20nothing%20happens%20and%20that%20confuses%20users.%20It%20is%20not%20intuitive%20to%20only%20select%20the%20little%20triangle.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20299px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F33801iCB2CECB2B9F93F75%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22MenuLook.PNG%22%20title%3D%22MenuLook.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20that%20note%2C%20our%20global%20nav%20currently%20has%20these%20boxes%20around%20the%20headers%3F%20Anyone%20else%20seeing%20this%3F%20This%20is%20only%20in%20modern%20UI%20not%20classic.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-191818%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-191818%22%20slang%3D%22en-US%22%3Eunclickable%20headers%20would%20be%20great%2C%20as%20I%20have%20many%20users%20that%20click%20on%20them%20before%20waiting.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-191579%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-191579%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20you%20make%20the%20top-level%20in%20global%20navigation%20not%20be%20a%20clickable%20link%3F%20For%20example%2C%20would%20like%20Departments%20to%20not%20be%20clickable.%20Appears%20to%20require%20a%20URL.%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20254px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F33765i831B1202EA164897%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22globalNav.jpg%22%20title%3D%22globalNav.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-140942%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-140942%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1016%22%20target%3D%22_blank%22%3E%40Richard%20Sharp%3C%2FA%3E%20-%20thanks%20for%20the%20detailed%20reply%2Ffeedback.%20Great%20to%20hear%20that%20the%20recent%20updates%20are%20enabling%20you%20to%20move%20forward%20with%20using%20modern%20library%20ux.%20I'll%20take%20a%20look%20at%20that%20behavior%20w%2F%20%22no%20url%22%20to%20evaluate%20whether%20there's%20more%20we%20should%20do%20there.%20I%20am%20keen%20to%20get%20this%20functionality%20working%20w%2F%20modern%20templates%20so%20we'll%20keep%20the%20community%20posted%20on%20our%20progress%20there.%20RE%3A%20other%20items%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%231%20-%20inconsistent%20status%26nbsp%3B%20toast%20of%20L2%20items%20-%20I've%20bugged%20so%20we%20can%20take%20a%20look%20at.%20Thanks%20for%20reporting.%3C%2FP%3E%0A%3CP%3E%232%20-%20interesting%3B%20I'd%20thought%20w%2F%20the%20client-side%20improvements%20we'd%20made%20here%20it%20was%20faster.%20We'll%20take%20a%20look%2C%20but%20let%20me%20know%20if%20this%20persists.%3C%2FP%3E%0A%3CP%3E%233%20-%20yes%2C%20I'm%20seeing%20that%20now%2C%20too%20-%20and%20agree%20the%20flyouts%20shouldn't%20persist%20when%20you%20move%20cursor%20focus%20away.%20I've%20bugged%20for%20investigation%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERe%3A%20your%20last%20comment%20on%20classic%20publishing%20template%20-%20there%20is%20likely%20more%20work%20to%20do%20there%20on%20our%20side.%20We%20haven't%20done%20much%20w%2F%20that%20template%20in%20favor%20of%20the%20new%20communication%20template.%20I'll%20note%20and%20forward%20feedback%20to%20the%20team.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20again!%3C%2FP%3E%0A%3CP%3ESean%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-138106%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-138106%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20very%20much%20for%20this%20follow-up.%20Based%20on%20your%20response%2C%20I%20spent%20several%20hours%20last%20week%20re-examining%20my%20configuration.%20I%20do%20use%20term-driven%20pages.I%20think%20the%20issue%20was%20that%2C%20while%20I%20had%20an%20entry%20for%20Level%200%20(site%20collection%20home)%2C%26nbsp%3BI%20did%20not%20have%20a%20URL%20specifically%20configured%20for%20it.%20It%20was%20never%20required%20for%20the%20link%20to%20work%20in%20classic%20managed%20navigation.%20Once%20I%20added%20that%20URL%20and%20let%20things%20sit%20overnight%2C%20all%20the%20child%20links%20fell%20into%20place.%20So%20that%20is%20a%20huge%20win%20for%20us%2C%20and%20will%20enable%20us%20to%20start%20to%20use%20modern%20libraries%20in%20our%20existing%20site%20collections.%20Also%2C%20the%20fact%20that%20the%26nbsp%3Btext%20in%20the%20drop-down%20and%20fly-out%26nbsp%3Bitems%20is%20no%20longer%20truncated%20is%20a%20great%20improvement.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI've%20noticed%20three%20other%20differences%20in%20managed%20navigation%20as%20deployed%20in%20modern%20libraries%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E1.%20If%20a%20level%202%20(drop-down)%20item%26nbsp%3Bdoes%20not%20have%20a%20level%203%20(fly-out)%20child%2C%20the%20URL%20%22preview%22%20appears%20as%20expected%20in%20the%20lower%20left%20corner%20of%20the%20browser%20when%20you%20hover%20over%20the%20level%202%20item.%20If%20it%20does%20have%20a%20level%203%20(fly-out)%20child%2C%20no%20URL%20%22preview%22%20appears%20when%20you%20hover%20over%20it.%20All%20level%26nbsp%3B0%2C%201%2C%20and%203%26nbsp%3B%22previews%22%20appear%20as%20expected.%20The%20links%20function%20correctly%2C%20but%20it%20would%20be%20nice%20if%20the%20level%202%20previews%20appeared%20consistently%2C%20as%20they%20do%20in%20classic%20mode.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E2.%20The%20response%20in%20the%20appearance%20of%20the%20navigation%20drop-downs%20and%20fly-outs%20is%20noticeably%20slower%20than%20in%20classic%20mode.%20Not%20bad%2C%20but%20not%20the%20lightning-fast%20feel%20we're%20used%20to.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E3.%20If%20one%20hovers%20over%20a%20level%201%20(global%20nav)%20item%20to%20display%20the%20level%202%20drop-down%20and%20then%20does%20not%20click%20on%20one%20of%20the%20level%202%20or%20level%203%20items%20but%20simply%20moves%20the%20cursor%20away%20from%20the%20navigation%20area%2C%20the%20drop-down%20(and%2C%20if%20chosen%2C%20the%20fly-out)%20menu%20remains%20open%20until%20one%20clicks%20elsewhere%20on%20the%20page.%20In%20classic%20mode%2C%20the%20drop-downs%20disappear%20immediately%20when%20the%20cursor%20is%20no%20longer%20hovering%20over%20the%20navigation%20item.%20This%20need%20for%20an%20extra%20click%20contributes%20to%20the%20feeling%20that%20the%20response%20is%20a%20bit%20more%20cumbersome%20than%20in%20classic%20navigation.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENonetheless%2C%20the%20fact%20that%20all%20levels%20of%20managed%20navigation%20now%20appear%20to%20lead%20to%20the%20correct%20URLs%26nbsp%3Bis%20a%20great%20breakthrough%20for%20us%2C%20and%20I%20very%20much%20appreciate%20your%20sticking%20with%20this!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMy%20next%20task%20is%20to%20get%20this%20to%20work%20in%20classic%20publishing%20sites%20that%20don't%20use%20managed%20navigation.%20Right%20now%2C%20when%20viewed%20from%20a%20modern%20library%20the%20drop-downs%20display%20all%20the%20contents%20of%20the%20level%201%20sites%20as%20well%20as%20the%20links%20to%20the%20level%202%20sites%2C%20which%20is%20not%20the%20desired%20behavior.%20Is%20that%20your%20experience%2C%20as%20well%2C%20or%20am%20I%20doing%20something%20wrong%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20again%20for%20all%20your%20help!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERichard%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137758%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137758%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20done%20that%2C%20but%20when%20selecting%20the%20link%20back%20to%20the%20homepage%2C%20the%20top%20navigation%20does%20not%20appear%20until%20I%20refresh%20the%20page.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135510%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135510%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1016%22%20target%3D%22_blank%22%3E%40Richard%20Sharp%3C%2FA%3E%20-%20I%20think%20we're%20there!%20But%20I%20want%20to%20make%20sure%20I%20understand%20your%20configuration.%20I'm%20not%20sure%20I%20understand%20how%20you%20have%20Leve%200%20implemented%20to%20render%20in%20the%20nav%20if%20your%20L1%20is%20the%20header%20node.%20I%20assume%20you%20are%20using%20term-driven%20pages%3F%20If%20I%20configure%20simple%20links%20for%20each%20child%20node%20each%20one%20works%3A%20that%20is%2C%20I%20create%20a%20global%20nav%20w%2F%20managed%20navigation%20and%20set%20up%20L1%20(global%20nav)%2C%20L2%20(drop-down)%2C%20and%20L3%20(fly-out)%20nodes%20(all%20w%2F%20hyperlinks)%20-%20they%20all%20work%20as%20expected.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20I%20set%20up%20the%20child%20nodes%20as%20term-driven%20pages%20I%20seem%20to%20get%20the%20correct%20URL%20path%20and%20behavior%3A%20%2FL1%2FL2%2FL3%20(which%20is%20relative%20to%20the%20parent%20site%20so%20the%20URL%20for%20the%20L3%20page%20would%20be%20%3CA%20href%3D%22https%3A%2F%2Fdomain.sharepoint.com%2Fteams%2Fssquires%2FL1%2FL2%2FL3%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdomain.sharepoint.com%2Fteams%2Fssquires%2FL1%2FL2%2FL3%3C%2FA%3E%20).%20I%20haven't%20configured%20any%20other%20target%20page%20settings%2C%20so%20let%20me%20know%20if%20you're%20doing%20something%20different.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20for%20collapse%20by%20default%20-%20yes%2C%20we%20are%20evaluating%20changing%20the%20home%20page%20behavior%20to%20default%20collapsed%20(which%20would%20also%20make%20it%20consistent%20w%2F%20the%20libraries).%20Thanks%20for%20the%20feedback%20here.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-133226%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-133226%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3B-%20I'm%20just%20wondering%20what%20the%20time%20line%20might%20be%20for%20supporting%20the%20use%20of%20Modern%20Document%20Libraries%20and%20Lists%20in%20long-existing%20classic%20sites%20that%20utilize%20the%20Publishing%20feature%20and%20Managed%20Navigation%20for%20the%20Global%20Navigation%20(structured%20for%20the%20Quick%20Launch).%20Here's%20what%20I%20see%20right%20now%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EConsider%20Level%200%20as%20the%20top%20of%20the%20site%20collection%2C%20Level%201%20as%20the%20link%20that%20appears%20across%20the%20top%20in%20the%20Global%20Navigation%2C%20Level%202%20as%20the%20drop-down%2C%20and%20Level%203%20as%20the%20fly-out%20to%20the%20right.%20In%20a%20Modern%20Document%20Library%20view%20of%20the%20navigation%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E*%20Level%200%20appears%20in%20the%20Global%20Nav%20but%20does%20nothing%20when%20you%20click%20on%20it%3C%2FP%3E%0A%3CP%3E*%20Level%201%20links%20work%3C%2FP%3E%0A%3CP%3E*%20Level%202%20links%20work%3C%2FP%3E%0A%3CP%3E*%20Level%203%20links%20are%20broken%2C%20as%20they%20omit%20Level%201%20from%20the%20URL.%20I.e.%2C%20the%20URL%20becomes%20...%2Fsites%2F0%2F2%2F3%20(no%20%221%22).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20seems%20we%20are%20so%20close.%20Is%20there%20hope%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAlso%2C%20any%20hope%20for%26nbsp%3Bbeing%20able%20to%20display%20the%20Quick%20Launch%20(structure%20navigation)%20in%20collapsed%20form%20by%20default%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERichard%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132314%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132314%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F98364%22%20target%3D%22_blank%22%3E%40Paul%20Martello%3C%2FA%3E%20-%20correct%2C%20I%20was%20referring%20to%20the%20classic%20publishing%20feature.%20No%2C%20unfortunately%20that%20scenario%20isn't%20supported%20at%20the%20moment%20as%20the%20communication%20site%20doesn't%20use%2Fdisplay%20the%20top%20link%20nav%20bar%20(which%20is%20what%20would%20be%20inherited%20down%20to%20the%20subsite).%20Even%20enabling%20classic%20publishing%20wouldn't%20fix%20this%20-%20and%20you%20can't%20activate%20it%20as%20it%20conflicts%20w%2F%20the%20new%20publishing%20model.%20We%20are%20evaluating%20how%20to%20best%20support%20sub%20sites%20in%20the%20new%20modern%20site%20templates%2C%20but%20nothing%20we%20can%20share%20at%20this%20time.%20Your%20best%20workaround%20is%20to%20manually%20add%20the%20reference%20links%20you%20need%20to%20the%20sub%20site.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132025%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132025%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F18690%22%20target%3D%22_blank%22%3E%40Robert%20Schouten%3C%2FA%3E%20-%20yes%2C%20it's%20currently%20using%20the%20same%20nav%20provider%20(the%20work%20we%20did%20earlier%20this%20year%20was%20effectively%20to%20ensure%20the%20modern%20control%20behaved%20similarly%20to%20classic%20one%20for%20consistency%20on%20those%20classic%20sites%20where%20publishing%20infra%20feature%20was%20enabled)%20-%20so%20it%20will%20be%20bound%20by%20the%20same%20functionality%20and%20limitations.%20As%20for%20support%20on%20modern%20sites%20-%20yes%2C%20something%20we%20are%20looking%20into%2C%20but%20no%20specifics%20I%20can%20share%20at%20this%20time.%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-131976%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-131976%22%20slang%3D%22en-US%22%3E%3CP%3ESean%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%22assuming%20you%20have%20enabled%20publishing%20feature%20on%20a%20classic%20team%20site%22%26nbsp%3B%20Are%20you%20referring%20to%20activating%26nbsp%3B%3C%2FSPAN%3ESharePoint%20Server%20Publishing%20Infrastructure%20and%26nbsp%3BSharePoint%20Server%20Publishing%3F%26nbsp%3B%20Currently%2C%20I%20am%20creating%20a%20Communication%20site%2C%20and%20I%20can%20create%20a%20sub%20site%2C%20but%20the%20sub%20site%20does%20not%20inherit%26nbsp%3Bnavigation%26nbsp%3Bfrom%20the%20parent%20site.%20%26nbsp%3B%20I%20believe%20activating%20the%20above%20would%20solve%20the%20issue%2C%20but%20I%20cannot%20even%20do%20that.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-126712%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-126712%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3Bdoes%20the%20structured%20navigation%20on%20a%20Classic%20site%20with%20modern%20pages%20and%20libraries%20uses%20the%20same%20techniques%20to%20retrieve%20the%20navigation%3F%20So%20does%20it%20use%20object%20cache%2C%20etc.%20and%20does%20not%20perform%20well%20with%20larger%20structures%3F%20Can%20we%20also%20expect%20this%20structured%20navigation%20on%20Modern%20sites%20too%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-73162%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-73162%22%20slang%3D%22en-US%22%3E%3CP%3EToday%20I%20noticed%20that%20the%20Quick%20Launch%20navigation%20is%20not%20security%20trimmed%20in%20the%20Modern%20UI.%26nbsp%3B%20Users%20see%20all%20the%20links%20instead%20of%20only%20those%20to%20which%20they%20should%20have%20access.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70586%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70586%22%20slang%3D%22en-US%22%3E%3CP%3EI%20believe%20I%20saw%20Metadata%20Columsn%20for%20Filter%20Pane%20on%20one%20of%20the%20customer%20showcasing%20videos%20(and%20the%20end%20of%20each%20video%20there%20is%20a%20short%20roadmap%20overview).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70580%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70580%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3377%22%20target%3D%22_blank%22%3E%40Abhimanyu%20Singh%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3E%3CP%3EThank%20you%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F32817%22%20target%3D%22_blank%22%3E%40Miceile%20Barrett%3C%2FA%3E.%20Yes%2C%20we%20can%20see%20the%20filter%20pane%2C%20but%20that%20includes%20only%20a%20limited%20number%20of%20the%20list%20fields%20and%20no%20metadata%20terms.%20We%20look%20forward%20for%20the%20full%20metadata%20filtering%20options.%20It%20is%20good%20to%20know%20that%20you%20are%20working%20on%20this.%26nbsp%3B%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F32817%22%20target%3D%22_blank%22%3E%40Miceile%20Barrett%3C%2FA%3E%26nbsp%3BAny%20update%20on%20this%20please%3F%20It's%20been%20a%20long%20time%20and%20we%20are%20yet%20to%20see%20comprehensive%20metadata%20filtering%20in%20the%20filter%20pane%20of%20the%20modern%20UX.%20Please%20undertand%20that%20this%20is%20one%20of%20the%20friction%20sources%20for%20us%20which%20is%20preventing%20us%20from%20switching%20to%20modern%20from%20classic.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPinging%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3Bagain.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68188%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68188%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%3CSPAN%3E%26nbsp%3BWould%20you%20or%20anyone%20else%20be%20able%20to%20help%20with%20this%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F6699%22%20target%3D%22_blank%22%3E%40Nikhil%20Nulkar%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3BI%20am%20using%20a%20modern%20site%20(connected%20to%20a%20group%2Fteam)%20and%20the%20custom%20links%20in%20quick%20launch%20on%20left%20nav%20do%20not%20work.%20They%20have%20same%20behavior%20as%20illustrated%20in%20this%20post%20here.%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F783%22%20target%3D%22_blank%22%3E%40Phil%20Duffy%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3E%3CP%3EOK%2C%20just%20did%20some%20more%20testing%20and%20here's%20what%20happens.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3EI%20create%20a%20custom%20view%20for%20a%20library%20(in%20classic%20mode)%20and%20put%20a%20link%20to%20that%20view%20on%20the%20quick%20launch%20(%2Fsites%2Ftraining%2Fphildemo%2FUpload%2520Test%2FForms%2FCustom.aspx)%3C%2FLI%3E%3CLI%3EIn%20classic%20mode%20when%20I%20click%20on%20the%20link%2C%20the%20view%20opens%20up%20as%20expected%20with%20different%20columns%2C%20etc%3C%2FLI%3E%3CLI%3EThe%20library%20is%20set%20to%20Modern%20mode%20so%20now%20my%20menu%20is%20in%20modern%20view%2C%20and%20if%20I%20now%20click%20on%20the%20same%20link%20the%20URL%20is%20still%20pointing%20to%20the%20custom%20view%20(%2Fsites%2Ftraining%2Fphildemo%2FUpload%2520Test%2FForms%2FCustom.aspx)%20BUT%20what%20I%20see%20on%20refresh%20is%20actually%20the%20default%20view%20(All%20Documents)%3C%2FLI%3E%3CLI%3EAnd%20then%20to%20make%20things%20stranger%2C%20I%20cannot%20select%20my%20custom%20view%20from%20the%20View%20drop%20down.%3C%2FLI%3E%3CLI%3EIf%20I%20then%20go%20to%20the%20site%20home%20(in%20classic%20mode)%20the%20link%20works%20as%20expected%20again%3C%2FLI%3E%3C%2FOL%3E%3CP%3EHope%20that%20helps%2C%20happy%20testing!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPhil.%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EFrom%20what%20I%20understand%20its%20the%20case%20because%20as%20per%20your%20msg%20in%20this%20thread%2C%20if%20the%20link%20is%20on%20same%20site%2C%20then%20it%20opens%20in%20same%20tab%20and%20auto%20populates%20the%20URL%20with%20%2Fsites%2F....%20in%20the%20process%2C%20the%20above%20point%20%233%20happens.%20the%20view%20defaults%20to%20the%20document%20library%20view.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20this%20fixed%3F%20We%20are%20still%20facing%20this%20issue%20though.%20Advice%3F%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66440%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66440%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F783%22%20target%3D%22_blank%22%3E%40Phil%20Duffy%3C%2FA%3E%26nbsp%3Bthanks..%20I%20guess%20I'll%20do%20that.%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F783%22%20target%3D%22_blank%22%3E%40Phil%20Duffy%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3E%3CP%3EThis%20sounds%20a%20bit%20different%20to%20our%20issue%20as%20we%20weren%E2%80%99t%20using%20folders%20but%20just%20a%20custom%20view%20(filtered%2Fsorted).%20Maybe%20worth%20posting%20as%20a%20separate%20request%20to%20the%20moderator!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPhil.%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66426%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66426%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20sounds%20a%20bit%20different%20to%20our%20issue%20as%20we%20weren%E2%80%99t%20using%20folders%20but%20just%20a%20custom%20view%20(filtered%2Fsorted).%20Maybe%20worth%20posting%20as%20a%20separate%20request%20to%20the%20moderator!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPhil.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66303%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66303%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F783%22%20target%3D%22_blank%22%3E%40Phil%20Duffy%3C%2FA%3E%26nbsp%3Bthanks%20for%20your%20response.%20I%20am%20unsure%20what's%20the%20issue%20then%2C%20we%20are%20still%20seeing%20this%20issue.%20It%20happens%20every%20time%20I%20try%20to%20add%20a%20custom%20URL%20as%20a%20new%20link%20on%20the%20left%20navigation%20in%20the%20modern%20sites.%20The%20links%20default%20to%20the%20main%20document%20library%20view%20and%20not%20the%20respective%20folders%20within%20it.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66147%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66147%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Nikhil%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20just%20checked%20and%20this%20issue%20has%20been%20resolved%20now.%20It%20was%20all%20about%20links%20to%20custom%20Views%20not%20displaying%20with%20the%20modern%20look%20and%20feel.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPhil.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-64772%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-64772%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3BI%20am%20using%20a%20modern%20site%20(connected%20to%20a%20group%2Fteam)%20and%20the%20custom%20links%20in%20quick%20launch%20on%20left%20nav%20do%20not%20work.%20They%20have%20same%20behavior%20as%20illustrated%20in%20this%20post%20here.%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F783%22%20target%3D%22_blank%22%3E%40Phil%20Duffy%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3E%3CP%3EOK%2C%20just%20did%20some%20more%20testing%20and%20here's%20what%20happens.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3EI%20create%20a%20custom%20view%20for%20a%20library%20(in%20classic%20mode)%20and%20put%20a%20link%20to%20that%20view%20on%20the%20quick%20launch%20(%2Fsites%2Ftraining%2Fphildemo%2FUpload%2520Test%2FForms%2FCustom.aspx)%3C%2FLI%3E%3CLI%3EIn%20classic%20mode%20when%20I%20click%20on%20the%20link%2C%20the%20view%20opens%20up%20as%20expected%20with%20different%20columns%2C%20etc%3C%2FLI%3E%3CLI%3EThe%20library%20is%20set%20to%20Modern%20mode%20so%20now%20my%20menu%20is%20in%20modern%20view%2C%20and%20if%20I%20now%20click%20on%20the%20same%20link%20the%20URL%20is%20still%20pointing%20to%20the%20custom%20view%20(%2Fsites%2Ftraining%2Fphildemo%2FUpload%2520Test%2FForms%2FCustom.aspx)%20BUT%20what%20I%20see%20on%20refresh%20is%20actually%20the%20default%20view%20(All%20Documents)%3C%2FLI%3E%3CLI%3EAnd%20then%20to%20make%20things%20stranger%2C%20I%20cannot%20select%20my%20custom%20view%20from%20the%20View%20drop%20down.%3C%2FLI%3E%3CLI%3EIf%20I%20then%20go%20to%20the%20site%20home%20(in%20classic%20mode)%20the%20link%20works%20as%20expected%20again%3C%2FLI%3E%3C%2FOL%3E%3CP%3EHope%20that%20helps%2C%20happy%20testing!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPhil.%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EFrom%20what%20I%20understand%20its%20the%20case%20because%20as%20per%20your%20msg%20in%20this%20thread%2C%20if%20the%20link%20is%20on%20same%20site%2C%20then%20it%20opens%20in%20same%20tab%20and%20auto%20populates%20the%20URL%20with%20%2Fsites%2F....%20in%20the%20process%2C%20the%20above%20point%20%233%20happens.%20the%20view%20defaults%20to%20the%20document%20library%20view.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20this%20fixed%3F%20We%20are%20still%20facing%20this%20issue%20though.%20Advice%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-58598%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-58598%22%20slang%3D%22en-US%22%3E%3CP%3EMS%20releases%20a%20fix%20for%20managed%20navigation%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint%2FUPDATE-Support-for-Structured-Managed-Navigation-enabled-on%2Fm-p%2F58387%23M5636%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint%2FUPDATE-Support-for-Structured-Managed-Navigation-enabled-on%2Fm-p%2F58387%23M5636%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-57387%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-57387%22%20slang%3D%22en-US%22%3E%3CP%3EMorning%20everyone%20-%20the%20related%20fixes%20we%20were%20waiting%20on%20have%20rolled%20out%20so%20we're%20able%20to%20resume%20release%20of%20this%20fix.%20It%26nbsp%3Bshould%20be%20fully%20deployed%20to%26nbsp%3Bproduction%20by%20end%20of%20this%20week.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI've%20posted%20a%20general%20note%20to%20the%20SharePoint%20community%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint%2FUPDATE-Support-for-Structured-Managed-Navigation-enabled-on%2Fm-p%2F57384%23M5528%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint%2FUPDATE-Support-for-Structured-Managed-Navigation-enabled-on%2Fm-p%2F57384%23M5528%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20you%20again%20for%20your%20patience%20and%20help%20w%2F%20this%20fix!%20Do%20let%20us%20know%20if%20you%20have%20any%20questions%20or%20issues.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E-Sean%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-57372%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-57372%22%20slang%3D%22en-US%22%3ESo%20you're%20using%20managed%20nav%20for%20both%20global%20and%20current%20and%20the%20links%20opening%20behavior%20is%20different%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-57370%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-57370%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2144%22%20target%3D%22_blank%22%3E%40Pooya%20Obbohat%3C%2FA%3E%26nbsp%3B-%20we%20had%20to%20pause%20the%20rollout%20due%20to%20an%20impacting%20regression%3B%20the%20fix%20is%20only%20just%20now%20resuming%20(I'm%20posting%20a%20separate%20notice%2Fupdate%20this%20morning).%20Can%20you%20give%20it%20another%20try%20later%20this%20week%20and%20let%20me%20know%20if%20you're%20still%20seeing%20any%20issue%3F%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-56000%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-56000%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20not%20using%20structured%20navigation%20but%20for%20me%20the%20top%20and%20left%20controls%26nbsp%3Bare%20not%20working%26nbsp%3Bsimilarly.%26nbsp%3B%20Left%20opens%20subsites%20in%20same%20tab%2C%20top%20menu%20opens%26nbsp%3Bsubsites%26nbsp%3Bin%20new%26nbsp%3Btab.%26nbsp%3B%20This%20only%20occurs%20when%20the%20top%20link%20is%20on%20a%20mordern%20team%20site%20or%20page.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-55070%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-55070%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EDid%20you%20manage%20to%20fix%20this%3F%20I'm%20having%20the%20same%20problem.%20The%20second%20level%20of%20Global%20Nav%20now%20only%20works%20for%20me%20on%20the%20top%20level%20Site%2C%20but%20the%20items%20aren't%20clickable%20on%20Subsites.%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWas%20able%20to%20fix%20it%20on%20the%20top%20level%20Site%20by%20going%20to%20_layouts%2F15%2Ftopnav.aspx%2C%20adding%20an%20item%20and%20then%20removing%20it.%20Tried%20fixing%20it%20for%20Subsites%20by%20going%20to%26nbsp%3B_layouts%2F15%2Ftopnav.aspx%20and%20disabling%2Fenabling%20inheritance%2C%20but%20no%20luck.%20Wouldn't%20mind%20rebuilding%20the%20Global%20Nav%2C%20but%20I%20don't%20see%20any%20way%20to%20add%20a%20submenu%2C%20this%20seems%20to%20only%20work%20for%20the%20new%20quicklaunch.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54912%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54912%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20feedback%2C%20Richard.%20I%20agree%20that%20it's%20easy%20enough%20to%20right-click%20to%20open%20in%20new%20tab%20-%20and%20we%20are%20trying%20to%20be%20thoughtful%20about%20the%20potential%20proliferation%20of%20tabs.%20I%20should%20have%20added%20that%20there%20is%20on-going%20work%20here%20-%20across%20the%20workloads%20-%20to%20ensure%20a%20more%20thoughtful%20and%20consistent%20experience.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54911%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54911%22%20slang%3D%22en-US%22%3EMakes%20sense.%20The%20current%20design%20should%20meet%20your%20needs%20as%20the%20top%20and%20left%20controls%20would%20work%20similarly%20and%20open%20subsites%20of%20the%20site%20in%20the%20same%20tab%3B%20but%20other%20workloads%20(like%20a%20group-connect%20site's%20shared%20mailbox)%20in%20a%20new%20tab.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54860%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54860%22%20slang%3D%22en-US%22%3E%3CP%3EPeople%20always%20have%20the%20simple%20option%20of%20right-clicking%20and%20opening%20a%20link%20in%20a%20new%20tab%20whenever%20they%20want.%20I%20would%20want%20to%20see%20the%20same%20default%20behavior%20as%20we%20see%20today%20in%20classic%20sites%3A%20any%20link%20in%20the%20global%20navigation%20should%20open%20in%20the%20same%20tab.%20Otherwise%20people%20will%20have%20the%20same%20maddening%20experience%20we%20see%20in%20O365%20Groups%2C%20where%20navigating%20back%20and%20forth%20between%20the%20various%20functional%20parts%20of%20the%20Group%20ends%20up%20in%20a%20screen%20full%20of%20duplicate%20tabs.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20behavior%20(opening%20in%20same%20tab)%20should%20be%20observed%20when%20just%20the%20Publishing%20feature%20is%20turned%20on%20and%20also%20when%20Publishing%20is%20turned%20on%20*and*%20Managed%20Navigation%20is%20in%20use.%20(I%20use%20Managed%20Navigation%20in%20the%20global%20nav%2C%20and%20structured%20navigation%20in%20the%20local%20nav.)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%2C%20in%20addition%2C%20you%20want%20to%20specify%20an%20option%20we%20can%20set%20to%20force%20opening%20in%20a%20new%20tab%20for%20a%20specific%20link%2C%20that%20would%20be%20fine%3B%20but%20the%20default%20should%20be%20as%20it%20is%20today%20-%20open%20in%20same%20tab%20for%20all%20links.%20It's%20easy%20for%20anyone%20to%20override%20and%20open%20in%20a%20new%20tab%20whenever%20they%20want%2C%20but%20there's%20no%20way%20for%20a%20person%20to%20override%20and%20open%20a%20link%20in%20the%20same%20tab.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERichard%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20I%20have%20every%20site%20use%20the%20same%20global%20nav%20as%20the%20parent%2C%20so%20every%20site%20shows%20the%20same%20global%20nav%20as%20the%20top%20of%20the%20site%20collection.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54855%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54855%22%20slang%3D%22en-US%22%3EMost%20often%20we%20want%20to%20provide%20easier%20navigation%20to%20subsites%20using%20top%20nav%20or%20quick%20launch.%20This%20enables%20us%20to%20highlight%20few%20sub%20sites%20out%20of%20several%20sub%20sites.%20It%20totally%20makes%20sense%20to%20open%20a%20lik%20from%20different%20domain%20in%20new%20tab.%20But%20I%20think%20it%20is%20kind%20of%20annoying%20to%20users%20to%20open%20subsite%20in%20a%20new%20tabs%20because%20in%20user's%20mind%20they%20are%20still%20in%20%22SharePoint%22.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54847%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54847%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3Bas%20of%20today%20I%20am%20still%20seeing%20it%20yes%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54822%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54822%22%20slang%3D%22en-US%22%3E%3CP%3EOK%2C%20just%20did%20some%20more%20testing%20and%20here's%20what%20happens.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3EI%20create%20a%20custom%20view%20for%20a%20library%20(in%20classic%20mode)%20and%20put%20a%20link%20to%20that%20view%20on%20the%20quick%20launch%20(%2Fsites%2Ftraining%2Fphildemo%2FUpload%2520Test%2FForms%2FCustom.aspx)%3C%2FLI%3E%3CLI%3EIn%20classic%20mode%20when%20I%20click%20on%20the%20link%2C%20the%20view%20opens%20up%20as%20expected%20with%20different%20columns%2C%20etc%3C%2FLI%3E%3CLI%3EThe%20library%20is%20set%20to%20Modern%20mode%20so%20now%20my%20menu%20is%20in%20modern%20view%2C%20and%20if%20I%20now%20click%20on%20the%20same%20link%20the%20URL%20is%20still%20pointing%20to%20the%20custom%20view%20(%2Fsites%2Ftraining%2Fphildemo%2FUpload%2520Test%2FForms%2FCustom.aspx)%20BUT%20what%20I%20see%20on%20refresh%20is%20actually%20the%20default%20view%20(All%20Documents)%3C%2FLI%3E%3CLI%3EAnd%20then%20to%20make%20things%20stranger%2C%20I%20cannot%20select%20my%20custom%20view%20from%20the%20View%20drop%20down.%3C%2FLI%3E%3CLI%3EIf%20I%20then%20go%20to%20the%20site%20home%20(in%20classic%20mode)%20the%20link%20works%20as%20expected%20again%3C%2FLI%3E%3C%2FOL%3E%3CP%3EHope%20that%20helps%2C%20happy%20testing!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPhil.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54810%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54810%22%20slang%3D%22en-US%22%3ECorrect%20-%20this%20is%20the%20fix%20we%20are%20implementing%20-%20which%20we%20paused%20to%20address%20a%20regression%20we%20found%20and%20some%20other%20scenario-specific%20issues%20you%20all%20found.%20We%20have%20most%20of%20the%20fixes%20in%20and%20will%20be%20resuming%20the%20rollout%20of%20the%20fix%20(to%20support%20navigation%20on%20modern%20pages%20in%20classic%20team%20sites%20where%20publishing%20feature%20is%20enabled)%20later%20this%20week.%20Thanks%20for%20your%20patience!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54807%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54807%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F783%22%20target%3D%22_blank%22%3E%40Phil%20Duffy%3C%2FA%3E%26nbsp%3B-%20I%20haven't%20heard%20of%20this%20issue%20before%20and%20I'm%20unable%20to%20repro%2C%20so%20I%20wanted%20to%20verify%20configuration%2Fsteps%3A%3C%2FP%3E%0A%3CP%3E1.%20I%20create%20a%20public%20view%20(not%20default)%20in%20document%20library%3C%2FP%3E%0A%3CP%3E2.%20Copy%20that%20link%20and%20manually%20paste%20into%20quick%20launch%20(left)%20navigation%20on%20a%20modern%20(or%20classic%3F)%20page%3C%2FP%3E%0A%3CP%3E3.%20Save%20my%20changes%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EExpected%3A%20I%20navigate%20to%20that%20specific%20library%20view%3C%2FP%3E%0A%3CP%3EActual%3A%20the%20link%20is%20taking%20me%20to%20the%20*default*%20library%20view%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'm%20getting%20the%20expected%20behavior%20in%20repro%20above%2C%20but%20let%20me%20know%20if%20I'm%20misinterpreting%20a%20step.%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54802%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54802%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F271%22%20target%3D%22_blank%22%3E%40Marc%20Wenning%3C%2FA%3E%26nbsp%3B-%20the%20page%20not%20found%20fix%20is%20rolling%20out%20-%20are%20you%20still%20seeing%20this%20issue%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54799%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54799%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3755%22%20target%3D%22_blank%22%3E%40kiran%20bellala%3C%2FA%3E%26nbsp%3B-%20I%20missed%20your%20follow-up%20question.%20We%20are%20evaluating%20providing%20an%20affordance%20to%20specify%26nbsp%3Bthe%20link%20opening%20behavior%20(yes%2C%20a%20departure%20from%20classic).%20Current%20design%20is%20links%20w%2Fin%20same%20site%20path%20will%20open%20in%20same%20tab%3B%20links%20in%20a%20different%20path%20will%20open%20in%20a%20new%20tab.%20We're%20trying%20to%20minimize%20friction%20here%2C%20but%20can%20you%20elaborate%20on%20the%20business%20scenario%20to%20have%20more%20control%20over%20this%20behavior%3F%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54209%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54209%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3755%22%20target%3D%22_blank%22%3E%40kiran%20bellala%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3E%3CP%3EAfter%20trying%20to%20get%26nbsp%3Bwith%20navigation%20consistent%20on%20modern%20pages%20here%20is%20what%20I%20concluded%20(as%20of%203%2F13%20and%20subject%20to%20change%20in%20future)%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20Quick%20launch%20links%20for%20modern%20pages%20are%20setup%20at%20%2F_layouts%2F15%2Fquiklnch.aspx.%20If%20publishing%20is%20turned%20on%2C%26nbsp%3B_layouts%2F15%2FAreaNavigationSettings.aspx%20nav%20does%20not%20apply%20to%20modern%20pages.%20It%20applies%20only%20to%20classic%20pages.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2.%20Top%20nav%20for%20modern%20pages%20is%20setup%20at%26nbsp%3B_layouts%2F15%2Ftopnav.aspx.%20For%20sub%20sites%2C%20top%20nav%20is%20inheritance%20settings%20are%20setup%20at%26nbsp%3B%3CSPAN%3E_layouts%2F15%2Ftopnav.aspx%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E3.%20Top%20nav%20links%20on%20modern%20pages%20open%20in%20new%20window.%20But%20quick%20launch%20opens%20in%20same%20window.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EThats%20the%20problem%20we%20need%20the%26nbsp%3B%3CSPAN%3E_layouts%2F15%2FAreaNavigationSettings.aspx%20to%20work%20on%20Modern%20Pages%20with%20publishing%20enabled.%20%26nbsp%3BHopefully%20that%20is%20where%20they%20are%20going%20with%20all%20this.%20%26nbsp%3BSo%20far%20everything%20in%20the%20navigation%20settings%20is%20working%20for%20me%2C%20except%20for%20the%20hidden%20pages%20are%20showing.%20%26nbsp%3BSo%20its%20getting%20better%20than%20it%20was.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54204%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54204%22%20slang%3D%22en-US%22%3EAgree..%20Able%20to%20reproduce%20same%20behaviour%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-53076%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-53076%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3BI%20haven't%20seen%20this%20issue%20mentioned%20so%20far%2C%20so%20here%20goes.%20When%20creating%20a%20manual%20link%20in%26nbsp%3Bquick%20launch%20navigation%26nbsp%3Bto%20a%20view%20that%20is%20NOT%20the%20default%20view%20in%20a%20library%20works%20as%20expected%20in%20classic%20mode.%20But%20then%20in%20the%20library%20in%20modern%20mode%20the%20link%20is%20auto%20converted%20to%20the%20DEFAULT%20view%20for%20that%20library!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52851%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52851%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20one%20problem%20I%20have%20run%20into%20is%20that%20links%20in%20global%20nav%20dropdowns%20(second%20level)%20just%20flat%20out%20don't%20work%20on%20modern%20document%20libraries.%20Click%2C%20nothing%2C%20click%2C%20nothing.......%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3B--%20you're%20killin%20us!%20%26nbsp%3BSo%20close.....%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52690%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52690%22%20slang%3D%22en-US%22%3E%3CP%3EAfter%20trying%20to%20get%26nbsp%3Bwith%20navigation%20consistent%20on%20modern%20pages%20here%20is%20what%20I%20concluded%20(as%20of%203%2F13%20and%20subject%20to%20change%20in%20future)%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20Quick%20launch%20links%20for%20modern%20pages%20are%20setup%20at%20%2F_layouts%2F15%2Fquiklnch.aspx.%20If%20publishing%20is%20turned%20on%2C%26nbsp%3B_layouts%2F15%2FAreaNavigationSettings.aspx%20nav%20does%20not%20apply%20to%20modern%20pages.%20It%20applies%20only%20to%20classic%20pages.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2.%20Top%20nav%20for%20modern%20pages%20is%20setup%20at%26nbsp%3B_layouts%2F15%2Ftopnav.aspx.%20For%20sub%20sites%2C%20top%20nav%20is%20inheritance%20settings%20are%20setup%20at%26nbsp%3B%3CSPAN%3E_layouts%2F15%2Ftopnav.aspx%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E3.%20Top%20nav%20links%20on%20modern%20pages%20open%20in%20new%20window.%20But%20quick%20launch%20opens%20in%20same%20window.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52648%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52648%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20one%20library%20in%20one%20subsite%20set-up%20as%20modern%20experience.%20It%20is%20showing%20all%20the%20correct%20navigation%20links%20in%20the%20top%2C%20global%2C%20navigation%20bar%2C%20yet%20they%20are%20not%20grouped%20into%20drop-down%20menus%20as%20per%20the%20rest%20of%20my%20site(s).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52083%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52083%22%20slang%3D%22en-US%22%3EI've%20seen%20the%20same%20thing%20happen%2C%20but%20only%20for%20links%20to%20Contents%20and%20Subsites%20on%20the%20Site%20Contents%20page%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51966%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51966%22%20slang%3D%22en-US%22%3E%3CP%3ELooks%20like%20they%20fixed%20the%20weird%20numbers%20in%20the%20global%20navigation%2C%20but%20Im%20still%20seeing%20the%20page%20not%20found%20links%20in%20both%20the%20quick%20links%20and%20global%20navigation.%20%26nbsp%3BThis%20should%20not%20show%20as%20it%20is%20a%20hidden%20page.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20793px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F11685i05A9CA19A78E0687%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22navigation.jpg%22%20title%3D%22navigation.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51960%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51960%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20job%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3Band%20MS%20team%20for%20monitoring%20this%20thread.%20Lots%20of%20good%20info.%3C%2FP%3E%3CP%3EI%20have%20set%20my%20tenant%20to%20first%20release.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20issue%3A%20top%20nav%20in%20modern%20pages%20always%20opens%20in%20new%20tab.%20Does%20anyone%20see%20similar%20behavior%3F%20Can%20we%20set%26nbsp%3Bthe%20top%20nav%26nbsp%3Blinks%20to%20open%20in%20same%20window%3F%3C%2FP%3E%3CP%3EThanks%20in%20advance%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51745%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51745%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3B--%20pleasantly%20surprised%20tonight%20as%20I%20tested%20to%20see%20if%20the%20by%20some%20change%20the%20navigation%20fix%20made%20it%20to%20our%20tenant%20already.%20%26nbsp%3BSure%20enough%2C%20it%20did%2C%20and.................%20it%20works%20perfectly!%20%26nbsp%3B%20Publishing%20enabled%20at%20the%20root%20site%20and%20navigation%20propogates%20perfectly%20to%20all%20subsites.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThat%20said%2C%20I%20needed%20to%20go%20into%26nbsp%3B%2F_layouts%2F15%2Ftopnav.aspx%20and%26nbsp%3B%2F_layouts%2F15%2Fquiklnch.aspx%20on%20the%20top%20level%20and%20clear%20up%20some%20of%20the%20old%20links%20from%20when%20things%20were%20broken.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENice%20to%20have%20this%20working....%20much%20better%20than%20running%20a%20powershell%20script%20to%20fix%20all%20sites%2Fsub-sites.....%20thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51646%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51646%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3BThat's%20great%2C%20thanks%20for%20the%20update%2C%20it%20felt%20like%20an%20issue%20with%20the%20latest%20patching%20for%20the%20navigation.%20And%20thanks%20for%20monitoring%20this%20thread%20too.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51332%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51332%22%20slang%3D%22en-US%22%3E%3CP%3EAdding%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F42188%22%20target%3D%22_blank%22%3E%40Jeremy%20Coleman%3C%2FA%3E%2C%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5042%22%20target%3D%22_blank%22%3E%40Matty%20Vasquez%3C%2FA%3E%2C%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F7187%22%20target%3D%22_blank%22%3E%40bart%20vermeersch%3C%2FA%3E%2C%20and%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F271%22%20target%3D%22_blank%22%3E%40Marc%20Wenning%3C%2FA%3E%26nbsp%3Bfor%20notice%20-%20thanks%20all%20for%20the%20prompt%20reports.%20We've%20identified%20the%20issue%20and%20have%20paused%2Frecalled%20the%20build%20to%20address%20before%20we%20roll%20any%20further.%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51329%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51329%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1256%22%20target%3D%22_blank%22%3E%40James%20Brennan%3C%2FA%3E%26nbsp%3B-%20a%20regression%20has%20resulted%20in%20several%20UI%20issues%20w%2F%20this%20build.%20We%20have%20postponed%20and%20rolled-back%20until%20we%20can%20get%20fixes%20in%20place.%20I'll%20keep%20this%20list%20apprised%20of%20that%20progress.%20Apologies%20for%20the%20inconvenience%20-%20and%20thanks%20for%20your%20patience!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51314%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51314%22%20slang%3D%22en-US%22%3EI've%20ended%20up%20creating%20a%20top%20level%20folder%20called%20Other%20and%20moved%20all%20of%20the%20problem%20pages%20and%20sites%20into%20it.%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20order%20to%20do%20so%20I%20first%20had%20to%20enable%20Show%20Subsites%20and%20Show%20Pages%20under%20the%20global%20navigation%20option%2C%20that's%20what%20allowed%20me%20to%20see%20the%20items%20that%20shouldn't%20be%20showing%20up.%20Even%20though%20they%20were%20marked%20as%20hidden%20they%20were%20still%20visible%2C%20so%20by%20putting%20them%20under%20the%20Other%20Heading%20they%20are%20at%20least%20out%20of%20site.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-50786%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-50786%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20same%20thing%20just%20happened%20on%20one%20of%20our%20Site%20Collections%20and%20all%20Sub%20Sites%2C%20Global%20Navigation%20links%20have%20all%20been%20replaced%20with%20links%20to%20local%20items%20and%20appended%20with%20a%20'0'%20when%20the%20modern%20experience%20appears...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F11549iA83E4917403BC7B5%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22docsnew.png%22%20title%3D%22docsnew.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20logged%20a%20ticket%20and%20Microsoft%20said%20they%20are%20aware.%20Not%20too%20happy%20as%20the%20issue%20is%20on%20our%20executive%20board's%20site%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-50739%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-50739%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20is%20going%20on%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F11544i609B58B2E6A276F3%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22menu.png%22%20title%3D%22menu.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-50550%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-50550%22%20slang%3D%22en-US%22%3E%3CP%3EYeah%20I%20am%20seeing%20it%20as%20well%2C%20I%20am%20still%20seeing%20the%20page%20not%20found%20link%20as%20well%20in%20my%20dev%20tenant.%20%26nbsp%3BHopefully%20the%20navigation%20will%20be%20sorted%20out%20soon%2C%20wouldn't%20mind%20using%20the%20new%20lists%20and%20libraries%20but%20wont%20roll%20it%20out%20until%20this%20works%20as%20it%20should%20in%20my%20dev%20tenant.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20783px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F11516i43B3000F481375AF%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22navigation.jpg%22%20title%3D%22navigation.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-50538%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-50538%22%20slang%3D%22en-US%22%3EIt%20seems%20that%20whilst%20latest%20fix%20has%20resolved%20a%20number%20of%20issues%20with%20the%20global%20navigation%2C%20including%20the%20%22Page%20not%20found%22%20link%20showing%2C%20it%20appears%20we%20are%20now%20seeing%20a%200%20character%20being%20added%20to%20the%20end%20of%20each%20global%20navigation%20node.%20Additionally%20our%20global%20navigation%20appears%20to%20have%20stopped%20working%20completely%20when%20a%20user%20clicks%20on%20the%20link.%3CBR%20%2F%3E%3CBR%20%2F%3EIs%20anyone%20else%20seeing%20this%3F%20We've%20raised%20a%20ticket%20with%20MS%20to%20investigate.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-50461%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-50461%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%2C%20I%20referred%20to%20the%20top%2Fglobal%20navigation%20on%20my%20previous%20post.%20This%20is%20currently%20set%26nbsp%3Bto%20managed%26nbsp%3Bnavigation%26nbsp%3Band%20as%20mentioned%20by%20someone%26nbsp%3Bhere%20in%20this%20thread%26nbsp%3Bsubsites%20are%20not%20available%20from%20the%20new%20top%20navigation.%20No%20little%20triangle%20pointing%20to%20more.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EI%20also%20noticed%20that%20headers%20eg%20Operations%20which%20do%20not%20have%20any%20URLs%20attached%20to%20them%20now%20have%26nbsp%3Ba%20URL%20attached%20to%20them.%20Which%20then%20point%20to%20a%20page%20not%20found.This%20should%20not%20happen%20as%20this%20is%20not%20happening%20in%20the%20classic%20mode%20either.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20addtion%2C%26nbsp%3Bsimilar%20to%26nbsp%3Babove%2C%26nbsp%3Bin%20the%20navigation%20on%20the%20left%20the%20%22recent%22%20header%20(which%20pretty%20much%20annoys%20everyone%20(can%20we%20remove%20this%20please!!))%20and%20all%20other%20headers%20who%20previously%20has%20no%20links%20attached%20to%20the%20them%2C%20now%20link%20to%20our%20root%20site.%20Again%20this%20should%20not%20be%20the%20case.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49835%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49835%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1016%22%20target%3D%22_blank%22%3E%40Richard%20Sharp%3C%2FA%3E%26nbsp%3B-%20thanks%20for%20reporting%20-%20definitely%20not%20the%20intended%20behavior...appears%20to%20be%20a%20regression.%20We%20think%20we%20have%20identified%20the%20issue%20and%20are%20working%20on%20a%20fix.%20I'll%20communicate%20back%20to%20this%20thread%20as%20soon%20as%20I%20have%20an%20update.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49568%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49568%22%20slang%3D%22en-US%22%3EThanks%20for%20reporting%2C%20Richard%20-%20we'll%20take%20a%20look.%20We%20validated%20this%20scenario%20as%20we%20intend%20to%20honor%20all%20existing%20settings%2Fbehaviors%20from%20classic.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49566%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49566%22%20slang%3D%22en-US%22%3E%3CP%3EThat's%20correct%20-%20thanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F406%22%20target%3D%22_blank%22%3E%40Clint%20Lechner%3C%2FA%3E%26nbsp%3Bfor%20posting.%20As%20noted%20in%20my%20other%20reply%2C%20we've%20identified%20the%20issue%20w%2F%20the%20REST%20API%20and%20are%20working%20on%20a%20fix.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49565%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49565%22%20slang%3D%22en-US%22%3ECorrect.%20We've%20identified%20the%20issue%20(specifically%20w%2F%20the%20REST%20API%20to%20get%20the%20Navigation%20Provider%20Type)%20and%20are%20working%20on%20a%20fix%20(the%20issue%20is%20specific%20to%20structural%20nav%20from%20parent%20web%20(it%20works%20fine%20w%2F%20managed%20nav).%20Thanks%20for%20reporting%20-%20and%20sorry%20for%20the%20inconvenience!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49415%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49415%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E-%20I've%20since%20found%20more%20problems%20with%20the%20managed%20navigation%20in%20Global.%20While%20the%20navigation%20looks%20fairly%20normal%20(except%20for%20the%20fact%20that%20the%20final%20level%20of%20navigation%2C%20the%20flyouts%20to%20the%20right%2C%20are%20missing)%2C%20all%20the%20links%20drop%20%22%2Fsites%2FSiteCollectionName%2F%22%20from%20the%20URL%20behind%20them%2C%20so%20none%20work.%20Also%2C%20for%20the%20links%20displayed%20across%20the%20top%2C%20I%20have%20to%20double%20click%20on%20them%20to%20go%20to%20the%20link%20(which%2C%20of%20course%2C%20has%20the%20wrong%20URL).%20The%20links%20in%20the%20drop-downs%20require%20only%20a%20single%20click%2C%20but%2C%20like%20the%20others%2C%20are%20missing%20the%20%22%2Fsites%2FSiteCollectionName%2F%22%20part%20in%20the%20middle%20of%20the%20URL.%20This%20is%20a%20normal%20tenant%20-%20nothing%20in%20first%20release.%20All%20using%20IE%2011.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFinallly%2C%20in%20classic%20mode%2C%20hovering%20over%20any%20of%20the%20links%20shows%20the%20URL%20at%20the%20bottom%20left%20of%20the%20browser.%20In%20modern%20mode%2C%20the%20URLs%20are%20not%20shown.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49354%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49354%22%20slang%3D%22en-US%22%3EAny%20idea%20%3Ca%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F103307%22%3E%40sean%3C%2Fa%3E%20on%20who%20to%20mention%20%2F%20ping%20for%20UI%2FUX%20(on%20modern%20lists)%20feedback%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49352%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49352%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F32817%22%20target%3D%22_blank%22%3E%40Miceile%20Barrett%3C%2FA%3E.%20Yes%2C%20we%20can%20see%20the%20filter%20pane%2C%20but%20that%20includes%20only%20a%20limited%20number%20of%20the%20list%20fields%20and%20no%20metadata%20terms.%20We%20look%20forward%20for%20the%20full%20metadata%20filtering%20options.%20It%20is%20good%20to%20know%20that%20you%20are%20working%20on%20this.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49351%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49351%22%20slang%3D%22en-US%22%3EThank%20you%20%3Ca%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F103307%22%3E%40sean%3C%2Fa%3E.%20Hope%20to%20see%20this%20fixed%20soon.%20And%20thank%20you%20for%20pinging%20%40Miceile%20on%20metadata%20filtering.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49350%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49350%22%20slang%3D%22en-US%22%3EThanks%20a%20lot%20%3Ca%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F103307%22%3E%40sean%3C%2Fa%3E.%20Much%20appreciated.%20Hope%20the%20fix%20lands%20soon.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49291%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49291%22%20slang%3D%22en-US%22%3EAlso%2C%20I%20have%20one%20term%20that%20is%20marked%20not%20to%20display%20in%20the%20navigation.%20This%20is%20obeyed%20in%20the%20classic%20view%2C%20but%20in%20the%20modern%20view%20it%20is%20displayed.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49288%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49288%22%20slang%3D%22en-US%22%3EI%20use%20managed%20navigation%20for%20Global%20in%20my%20production%20tenant.%20When%20I%20switch%20a%20single%20document%20library%20into%20Modern%20mode%20I%20am%20now%20correctly%20seeing%20the%20first%20level%20of%20drop-downs%20from%20each%20of%20the%20top%20level%20items%2C%20but%20not%20the%20second%20(normally%20displayed%20as%20fly-outs%20to%20the%20right%20of%20the%20drop-down%20items).%20Also%2C%20I%20have%20a%20very%20simple%20Alternate%20CSS%20that%20makes%20the%20width%20of%20the%20drop-downs%20a%20bit%20wider%2C%20adds%20a%20separation%20line%20between%20each%20drop-down%20item%2C%20and%20highlights%20in%20blue%20the%20drop-down%20item%20as%20you%20mouse%20over%20it%20-%20none%20of%20those%20effects%20are%20displayed%20when%20I%20put%20the%20document%20library%20into%20Modern%20mode.%20The%20drop-down%20items%20are%20highlighted%20in%20gray%20when%20I%20roll%20over%20them.%20Still%2C%20it%20is%20considerable%20progress!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49251%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49251%22%20slang%3D%22en-US%22%3E%3CP%3EFYI%2C%20for%20those%20people%20having%20issues%20where%20the%20global%20and%20current%20navigation%20is%20the%20same%2C%20an%20alternative%20is%20to%20use%20managed%20navigation%20for%20the%20top%20level%20for%20global%20navigation.%20%26nbsp%3BIt%20seems%20that%20modern%20pages%20DO%20seem%20to%20inherit%20the%20managed%20navigation%20correctly.%20%26nbsp%3BYes%2C%20I%20know%2C%20it's%20not%20perfect%20but%20things%20are%20inherited%20just%20fine%20that%20way.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHey%2C%20it's%20a%20step.............%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49235%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49235%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3B--%20to%20be%20clear%2C%20you're%20saying%20the%20intended%20functionality%20should%20have%20the%20modern%20pages%20duplicate%2Finherit%20the%20global%20navigation%20and%20current%20navigation%3F%20%26nbsp%3BMeaning%20the%20global%20and%20current%20navigation%20should%20not%20be%20the%20same%2C%20correct%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49229%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49229%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3377%22%20target%3D%22_blank%22%3E%40Abhimanyu%20Singh%3C%2FA%3E%2C%20I%20am%20working%20on%20creating%20the%26nbsp%3Bmodern%20list%2Flib%20metadata%20filtering%20experience%20and%20wanted%20to%20give%20you%20some%20updates%20on%20the%20progress.%20Currently%2C%20we%20have%20released%20a%20feature%20called%20%22filters%20pane%22%20%26nbsp%3B%3CA%20title%3D%22Filters%20Pane%22%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FUse-smart-filters-to-find-your-file-or-list-item-293561ed-fb2e-4fb2-9a9f-8a21e299e323%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EFilters%20Pane%20Help%20Article%3C%2FA%3E.%20%26nbsp%3BWe%20have%20just%20rolled%20out%20to%20PROD%20so%20you%20can%20expect%20to%20see%20it%20within%20the%20week%20if%20you%20don't%20already%20have%20it!%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20feature%20is%20the%20first%20iteration%20for%20replacing%20metadata%20nav.%20The%20next%20months%20will%20be%20focused%20on%20cleaning%20up%20the%20UI%2C%20supporting%20term%20set%20filtering%2C%20and%20making%20sure%20metadata%20nav%20will%20no%20longer%20force%20users%20to%20back%20to%20SP%20classic.%20%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%2C%3C%2FP%3E%0A%3CP%3EMiceile%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49201%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49201%22%20slang%3D%22en-US%22%3E%3CP%3Eyep%20still%20seeing%20the%20page%20not%20found%20in%20both%20the%20global%20and%20current%20navigation%20for%20site%20collections%20in%20my%20dev%20tenant%20which%20is%201st%20release.%20%26nbsp%3BI%20was%20testing%20the%20publishing%26nbsp%3Bnavigation%20in%20my%20dev%20tenant%20and%20it%20seems%20to%20still%20not%20be%20working%20correctly.%20%26nbsp%3BLet%20me%20know%20if%20you%20need%20more%20info%20to%20help%20troubleshoot%20this.%20%26nbsp%3BI%20have%20created%20a%20few%20new%20site%20collections%20and%20enabled%20publishing%20on%20them%20and%20seeing%20the%20same%20thing%20on%20all%20of%20them.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20512px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F11280iC209F3AC941506D8%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22pagenotfound.jpg%22%20title%3D%22pagenotfound.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49196%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49196%22%20slang%3D%22en-US%22%3EWe%20should%20be%20fully%20rolled%20out%20to%20First%20Release%20tenants...can%20you%20provide%20more%20detail%20on%20what%20you're%20seeing%20on%20your%20dev%20tenant%3F%20Thanks.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49195%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49195%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3377%22%20target%3D%22_blank%22%3E%40Abhimanyu%20Singh%3C%2FA%3E%26nbsp%3B-%20sounds%20like%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3786%22%20target%3D%22_blank%22%3E%40Rob%20O'Keefe%3C%2FA%3E%26nbsp%3Bis%20reporting%20same.%20We'll%20take%20a%20look%3B%20the%20intended%20design%20is%20the%20modern%20page%2Fcontrols%20use%20the%20same%20publishing%20provider%20navigation%20settings%20and%20render%20the%20data%20similarly.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20for%20metadata%20filtering%20on%20lists%2Flibraries%2C%20we%20are%20working%20on%20a%20new%20experience%20for%20this%20that%20should%20be%20rolling%20out%20soon.%20Adding%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F32817%22%20target%3D%22_blank%22%3E%40Miceile%20Barrett%3C%2FA%3E%26nbsp%3Bfor%20notice%2Fcomment%20on%20that%20feature.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49191%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49191%22%20slang%3D%22en-US%22%3EKnowing%20who%20to%20%40mention%20is%20challenging.%20I%20have%20learned%20a%20few%20peoples%20names%20over%20the%20years%2C%20but%20it%20is%20always%20just%20a%20guess%20on%20my%20part%2C%20if%20a%20list%20of%20contacts%20for%20topics%2Ffeatures%2Freleases%20could%20be%20shared%2C%20then%20we%20would%20be%20able%20to%20address%20our%20comments%20to%20the%20correct%20people.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49188%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49188%22%20slang%3D%22en-US%22%3EHi%20Paul%20-%20rolling%20out%20fully%20to%20PROD%20this%20week.%20Thanks%20for%20your%20patience!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49185%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49185%22%20slang%3D%22en-US%22%3EThanks%20for%20reporting%2C%20Rob%20-%20I'm%20seeing%20this%2C%20too%2C%20and%20this%20is%20definitely%20not%20as%20designed%3B%20you%20should%20be%20able%20to%20set%20%22Display%20the%20same%20navigation%20items%20as%20the%20parent%20site%22%20and%20render%20the%20parent%20node%20values%20in%20the%20subsite.%20We'll%20take%20a%20look.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49183%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49183%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2521%22%20target%3D%22_blank%22%3E%40Philine%20von%20Guretzky%3C%2FA%3E%26nbsp%3B-%20can%20you%20elaborate%20on%20your%20scenario%3F%20If%20you%20have%20enabled%20the%20publishing%20feature%20and%20wish%20to%20display%20subsites%20in%20the%20nav%20you'll%20need%20to%20set%20navigation%20to%20structural%20and%20select%20the%20option%20%22Show%20subsites%22.%20If%20you%20are%20referring%20to%20displaying%20sublinks%20in%20a%20managed%20nav%20term%20set%2C%20we%20do%20display%20up%20to%20two%20levels.%20HTH.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49180%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49180%22%20slang%3D%22en-US%22%3EYes%2C%20this%20week!%20Thanks%20for%20your%20patience!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49179%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49179%22%20slang%3D%22en-US%22%3EHi%20David%20-%20this%20week%20we%20will%20be%20fully%20rolled%20out%20to%20all%20of%20production.%20Let%20me%20follow-up%20on%20the%20notice%20on%20the%20fasttrack%20roadmap.%20Thanks.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49178%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49178%22%20slang%3D%22en-US%22%3EHi%20Rob%20-%20a%20related%20issue%2Fregression%20slowed%20the%20release%20of%20this%20fix.%20It%20will%20be%20fully%20deployed%20to%20all%20tenants%20this%20week.%20The%20easiest%20way%20to%20check%20is%20verify%20your%20navigation%20settings%20(assuming%20you%20have%20enabled%20publishing%20feature%20on%20a%20classic%20team%20site%20-%20it's%20the%20areanavigationsettings.aspx%20page%3A%20site%20settings%20%26gt%3B%20%5Blook%20and%20feel%5D%20navigation)%20and%20test%20structural%20or%20managed%20nav%20setting%20w%2F%20a%20modern%20page%20(i.e.%2C%20document%20library%2C%20site%20contents%2C%20etc.).%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49177%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49177%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20guessing%20my%20dev%20tenant%20which%20is%201st%20release%20still%20hasnt%20received%20it%20yet%2C%20because%20I%20am%20still%20seeing%20the%20page%20not%20found%20in%20the%20navigation%20which%20should%20be%20hidden.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20you%20say%20rollout%20is%20that%20to%201st%20release%20tenants%20or%20for%20all%20tenants%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49175%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49175%22%20slang%3D%22en-US%22%3EFair%20ask%20-%20let%20me%20follow-up%20w%2F%20our%20marketing%20partners%20and%20see%20what%20we%20can%20do%20for%20this%20feature%20fix.%20Appreciate%20the%20feedback!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49174%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49174%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3377%22%20target%3D%22_blank%22%3E%40Abhimanyu%20Singh%3C%2FA%3E%26nbsp%3B(and%20others%20on%20this%20thread!)%20-%20my%20apologies%20for%20the%20radio%20silence%20on%20our%20part.%20I%20was%20away%20on%20family%20business%20and%20inquries%20on%20this%20thread%20were%20missed%20by%20others.%20I%20will%20review%20w%2F%20the%20feature%20crew%20this%20morning%20and%20get%20back%20to%20everyone.%20We%20are%20trying%20to%20as%20attentive%20as%20we%20can%20to%20folks%20questions%20and%20feedback%20on%20this%20platform%20-%20so%20please%20do%20continue%20reaching%20out%20(and%20%40mentioning%20us%20to%20ensure%20we%20get%20the%20notification)!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EA%20quick%20summary%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThere%20was%20a%20related%20issue%20that%20delayed%20the%20rollout%20of%20this%20feature%20fix%20-%20so%20some%20of%20you%20may%20not%20have%20seen%20the%20fix%20in%20your%20tenant%20yet.%20It%20is%20currently%20at%2050%25%20WW%20and%20will%20be%20fully%20rolled%20out%20in%20the%20next%20two%20days%20to%20all%20of%20production%20(read%3A%20100%25%20WW%20this%20week).%20Thank%20you%20for%20your%20patience.%3C%2FLI%3E%0A%3CLI%3EFair%20ask%2Ffeedback%20about%20inclusion%20on%20the%20roadmap%20-%20we%20work%20closely%20w%2F%20our%20marketing%20partners%20to%20try%20and%20provide%20the%20right%20level%20of%20notice%2Fvisibility%20on%20feature%20announcements%20and%20major%20fixes%3B%20I%20will%20discuss%20w%2F%20them%20further%20about%20adding%20this%20one%20there.%3C%2FLI%3E%0A%3CLI%3EAs%20noted%2C%20this%20fix%20is%20specifically%20to%26nbsp%3Benable%20the%20modern%20page%20navigation%20controls%20to%20read%20from%20the%20same%20publishing%20provider%20as%20classic%20pages%20do%20(for%20team%20sites%20where%20publishing%20feature%26nbsp%3Bis%20enabled)%3B%20in%20other%20words%2C%20excepting%20functional%20differences%20between%20the%20classic%20(i.e.%2C%20%22recent%22%20node)%20and%20modern%20controls%20themselves%2C%20the%20rendered%20data%20should%20be%20the%20same%20(per%20the%20settings%20you%20designate%20on%20the%20areanavigationsettings%20page.%20Some%20of%20the%20discrepancies%20noted%20here%20sound%20like%20bugs%20-%20so%20thank%20you%20for%20reporting%20and%20we'll%20look%20into%20it%20immediately.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EThanks!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-49101%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-49101%22%20slang%3D%22en-US%22%3EThis%20is%20a%20major%20flaw.%20I'd%20even%20open%20a%20support%20ticket%20just%20to%20get%20this%20documented%2C%20not%20that%20there%20is%20a%20solution%20for%20it.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-48702%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-48702%22%20slang%3D%22en-US%22%3E%3CP%3EYup.%20Sad%20part%20is%20that%20Microsoft%20people%20aren't%20as%20active%20here%20as%20they%20had%20been%20on%20the%20older%20Yammer%20group.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3Bare%20you%20listening%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-48695%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-48695%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3377%22%20target%3D%22_blank%22%3E%40Abhimanyu%20Singh%3C%2FA%3E%26nbsp%3B--%20right%2C%20my%20point%20was%20that%20I%20hope%20that%20isn't%20what%20is%20supposed%20to%20be%20happening.%20%26nbsp%3BThat's%20what%20I%20see%20as%20well%20and%20it%20certainly%20isn't%20what%20I%20consider%20to%20be%20working%20correctly.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-48694%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-48694%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F406%22%20target%3D%22_blank%22%3E%40Clint%20Lechner%3C%2FA%3E%26nbsp%3Bsee%20the%20screenshots%20that%20I%20took%20for%20both%20the%20classic%20mode%20(what%20it%20is%20supposed%20to%20be)%20and%20the%20modern%20mode%20(what%20is%20messed%20up)%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F11217i5BBB946E5C8B8DB7%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22classic.png%22%20title%3D%22classic.png%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EClassic%3C%2FSPAN%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F11218i9F4635F0983BA293%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22modern.png%22%20title%3D%22modern.png%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3ESo-called%20Modern%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-48689%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-48689%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3377%22%20target%3D%22_blank%22%3E%40Abhimanyu%20Singh%3C%2FA%3E%26nbsp%3B--%20there's%20no%20way%20that%20what%20you're%20seeing%20with%20the%20global%20and%20quick%20launch%20being%20the%20same%20is%20how%20it%20is%20supposed%20to%20be%20(I%20hope).%20%26nbsp%3BAt%20least%2C%20I%20hope%20that's%20not%20what%20Microsoft%20thinks%20is%20%22fixed%22%20or%20reasonable.........%20if%20so%2C%20they%20have%20pretty%20much%20destroyed%20the%20global%20navigation%20and%20any%20hope%20that%20people%20will%20move%20to%20modern%20sites%20quickly.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-48688%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-48688%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%2C%20we%20are%20yet%20to%20see%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlthough%20the%20navigation%20is%20now%20settled%20up%20and%20the%20%22page%20not%20found%22%20link%20is%20gone%2C%20but%26nbsp%3Bthe%20global%20(top)%20and%20current%20(left-pane)%26nbsp%3Bnavigations%20are%20now%20the%20same.%20The%20actual%20global%20menu%20is%20now%20gone!!%20We%20have%20set%20it%20on%20our%20sub-sites%20to%20inherit%20from%20the%20parent%20site-collection%2C%20but%20somehow%20the%20new%20nav%20ignores%20that%20and%20makes%20the%20global%20navigation%20exactly%20same%20as%20the%20current%20(left)%20one.%20In%20our%20case%2C%20both%20are%20structural%20and%20not%20managed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFurther%2C%20the%20modern%20list%2Flibrary%20still%20does%20not%20allow%20metadata%20filtering!%20We%20have%20set%20filters%20on%26nbsp%3Bterm-sets%2C%20but%20in%20modern%20view%20that%20is%20not%20available.%20This%20new%20style%20is%20getting%20more%20furstating%20day%20by%20day.%20Our%20users%20still%20find%20the%20classic%20view%20more%20neat%20and%20clean.%20The%20new%20view%20looks%20very%20unpolished%20and%20unncessarily%20big.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-48362%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-48362%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20eagerly%20awaiting%20this%20as%20well.%20%26nbsp%3BSo%2C%20with%20this%20in%20place%2C%20will%20the%20navigation%20propogate%20to%20all%20sites%20and%20subsites%20on%20all%20pages%20and%20have%20both%2Fmulti-levels%20as%20well%3F%20Ultimately%2C%20I%20guess%20my%20question%20is%2C%20will%20the%20navigation%20exactly%20mirror%20what's%20on%20the%20top%20level%20publishing%20site%20(if%20settings%20are%20set%20that%20way)%3F%20%26nbsp%3BI'd%20also%20know%20if%20there's%20a%20way%20to%20check%20this%20as%20right%20now%20I%20basically%20script%20our%20navigation%20to%20pushed%20out%20everywhere%20and%20would%20love%20to%20stop%20doing%20that.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47971%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47971%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3Bany%20idea%20when%20this%20will%20hit%20all%20tenants%3F%20I'm%20having%20issues%20with%20Page%20not%20Found%20showing%20up%20in%20modern%20views%20even%20though%20it's%20tagged%20as%20hidden%20in%20the%20navigation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45903%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45903%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20I%20have%20only%20seen%20it%26nbsp%3Bworking%20in%20one%20test%20susbite%2C%20while%20it%20doesn't%20seem%20to%20show%26nbsp%3Bin%20another.%20Not%20too%20sure%20why%20this%20might%20be%2C%20but%20glad%20to%20hear%20I%20am%20not%20the%20only%20one%20confused.%20Good%20to%20seeing%20things%20move%20forward%20though.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45790%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45790%22%20slang%3D%22en-US%22%3EThat's%20what%20happens%20to%20us%20as%20well.%20I%20wrote%20a%20Powershell%20script%20that%20gets%20the%20root%20navigation%2C%20breaks%20the%20inheritance%2C%20and%20then%20updates%20the%20navigation%20in%20all%20sub-sites.%20Such%20a%20pain%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45786%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45786%22%20slang%3D%22en-US%22%3EWe%20are%20having%20trouble%20with%20this.%20We%20have%20a%20modern%20Document%20library%20in%20a%20Sub-Site%20under%20a%20Site%20that%20uses%20the%20traditional%20UI.%20The%20modern%20is%20a%20test%20site.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20set%20the%20modern%20to%20be%20%22Same%20as%20Parent%22%20for%20Global%2C%20and%20Structural%20for%20Current%20navigation%20on%20the%20side.%20The%20document%20library%20is%20showing%20the%20Current%20navigation%20menus%20BOTH%20on%20the%20side%20and%20in%20place%20of%20the%20Global.%20Our%20true%20global%20is%20not%20shown%20at%20all.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20am%20not%20sure%20if%20we%20have%20the%20new%20code%20or%20not%2C%20not%20sure%20how%20to%20tell.%3CBR%20%2F%3E%3CBR%20%2F%3ERob.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45780%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45780%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20noticed%20the%20update%20to%20the%20managed%20navigation%2C%20great%20news%20and%20definitely%26nbsp%3Bmore%20user%20friendly%20already.%3C%2FP%3E%3CP%3EHowever%20it%20doesn't%20seem%20show%26nbsp%3Bsub-links%20at%20the%20moment%2C%20is%20this%20feature%20still%20to%20come%3F%20Thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-44906%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-44906%22%20slang%3D%22en-US%22%3E%3CP%3EOooh%20ooh%2C%20me%20want!%20%26nbsp%3B%20Looking%20forward%20to%20having%20this%20show%20up.%20%26nbsp%3BAny%20rough%20timeline%3F%20%26nbsp%3BCouple%20weeks%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-44754%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-44754%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3B%2C%20i%20can't%20found%20anything%20on%20the%20fasttrack%20roadmap.%20When%20is%20this%20fix%20planned%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-43374%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-43374%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you!!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20something%20obvious%20we%20can%20see%20to%20know%20that%20our%20tenant%20has%20received%20this%20capablity%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERob.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-43250%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-43250%22%20slang%3D%22en-US%22%3E%3CP%3EThats%20awesome%2C%20cant%20wait%20for%20it%20to%20rollout%20so%20we%20can%20start%20using%20the%20new%20lists%20and%20libraries%20once%20the%20navigation%20is%20working%20as%20it%20should.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-42930%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-42930%22%20slang%3D%22en-US%22%3EThrilled%20to%20hear%20you%20are%20addressing%20this%2C%20thank%20you.%20A%20wish%20would%20be%20for%20MSFT%20to%20include%20updates%20like%20this%20one%20on%20the%20roadmap%20%E2%80%93%20making%20it%20a%20bit%20more%20detailed%20around%20the%20(post)%20rolllout%20of%20the%20modern%20experience.%20This%20would%20most%20likely%20reduce%20the%20confusion%20and%20number%20of%20posts%20here%2C%20all%20asking%20for%20the%20same%20thing.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-42920%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-42920%22%20slang%3D%22en-US%22%3E%3CP%3EStill%20a%20few%20more%20roadblocks%2C%20but%20this%20helps%20remove%20one%20of%20the%20major%20ones!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F10418iEC9D02EDFFAE52EB%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22achievementUnlocked.jpg%22%20title%3D%22achievementUnlocked.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-42845%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-42845%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F637%22%20target%3D%22_blank%22%3E%40Brent%20Ellis%3C%2FA%3E%26nbsp%3B(and%20others)%20-%20good%20news!%20We're%20finally%20pushing%20out%20a%20fix%20to%20support%20structured%20and%20managed%20navigation%20on%20modern%20pages%2Fapps%20in%20classic%20sites.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWith%20this%20update%2C%20if%20you%20have%20enabled%20publishing%20on%20a%20classic%20team%20site%2C%20your%20structured%20or%20managed%20navigation%20nodes%20will%20now%20render%20correctly%20in%20the%20modern%20pages%20(both%20global%20and%20current%20navigation)%2C%20including%20any%20scoped%20or%20audience-targeted%20links.%20We%20haven%E2%80%99t%20pulled%20all%20the%20classic%20settings%20into%20the%20modern%20panels%20yet%2C%20so%20when%20you%20need%20to%20edit%20the%20navigation%20nodes%20the%20edit%20link%20will%20direct%20you%20back%20to%20the%20classic%20settings%20page%20(%2Fareanavigationsettings.aspx).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20hope%20this%20unblocks%20folks%20who%20have%20been%20eager%20to%20move%20to%20the%20modern%20UX.%20Do%20try%20it%20out%20let%20us%20know%20if%20you%20have%20any%20questions.%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-41431%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-41431%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%2C%2B1%20here!%20Currently%20the%20only%20issue%20completely%20stopping%20us%20from%20moving%20the%20majority%20of%20libraries%20to%20modern.%20Would%20be%20nice%20to%20see%20this%20in%20the%20pipeline.%20I%20guess%20there%20are%20some%20major%20updates%20coming%20to%20managing%20navigation.%20Can't%20see%20why%20it%20would%20take%20so%20long%20to%20address%20this%20otherwise.%20Would%20at%20least%20be%20nice%20to%20have%20a%20temporary%20support%2C%20until%20something%20else%20is%20in%20place%2C%20so%20that%20we%20can%20start%20getting%20users%20up%20to%20speed%20on%20the%20modern%20libraries.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20a%20side%20note%3A%20I%20measured%20that%20the%20TTFB%20for%20opening%20our%26nbsp%3Blibraries%20is%20up%20to%2010-15%20seconds(!)%2C%20unlike%20the%20new%20ones%20which%20are%20max%201%20second.%20Yet%20another%20reason%20to%20move%20over.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-14656%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-14656%22%20slang%3D%22en-US%22%3E...and%20%2F_layouts%2F15%2Fquiklnch.aspx%20would%20be%20for%20the%20equivalent%20quick%2Fleft%20navigation%20section.%20In%20light%20of%20no%20information%20coming%20forward%20about%20when%20the%20navigation%20will%20be%20fixed%20in%20modern%20libraries%2C%20I'm%20going%20to%20have%20a%20look%20at%20cleaning%20these%20two%20areas%20up%20on%20one%20site%20and%20trying%20out%20the%20modern%20library%20experience%20with%20some%20users.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-13784%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-13784%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20posting%20this.%20We%20have%20turned%20off%20modern%20sites%20until%20the%20navigation%20is%20working%20more%20consistently.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20the%20Modern%20UI%20should%20give%20more%20tools%20for%20building%20navigation%20(tiles%2C%20menus%2C%20other%20controls).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20go%20to%20the%20URL%20for%20Top%20Menu%20and%20delete%20off%20the%20excess%20menu%20choices.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftentant_name.sharepoint.com%2F_layouts%2F15%2Ftopnav.aspx%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftentant_name.sharepoint.com%2F_layouts%2F15%2Ftopnav.aspx%26nbsp%3B%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20like%20the%20Top%20Menu%20has%20the%20Structured%20Navigation%20plus%20a%20bunch%20of%20random%20stuff.%20Even%20though%20you%20only%20see%20one%20level%20of%20navigation%2C%20the%20second%20level%20is%20in%20there%20too.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBe%20aware%20though%2C%20every%20time%20you%20edit%20the%20true%20Structured%20navigation%2C%20the%20%22extra%20junk%22%20links%20all%20get%20added%20back.%20Very%20frustrating.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20work%20in%20progress%20no%20doubt.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWill%20watch%20this%20thread%20for%20more%20news.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERob.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-11160%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-11160%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20turned%20off%20the%20new%20library%20experience%20until%20the%20navigation%20issues%20can%20be%20fixed%2C%20the%20majority%20of%20our%20sites%20are%20publishing%20sites%20and%20we%20cant%20have%20the%20navigation%20not%20working%20correctly.%20%26nbsp%3BI%20do%20like%20the%20look%20and%20feel%20of%20the%20new%20lists%20and%20libraries%20but%20will%20not%20roll%20it%20out%20to%20our%20users%20until%20navigation%20works%20like%20it%20should.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-9083%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-9083%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20here%2C%3C%2FP%3E%3CP%3EWe%20are%20also%20now%20focussing%20more%20on%20the%20top%20navigation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENext%20to%20that%20for%20every%20major%20site%20collection%20and%20major%20themed%2Fdepartemental%20sites%20wa%20have%20a%20home%20-%20landing%20-%20page%20containing%20%22promoted%20links%22-tiles.%20These%20tiles%20make%20it%20visually%20very%20easy%20to%20find%20your%20way%20around%20between%20major%20related%20sites%20and%20collections.%3C%2FP%3E%3CP%3EWould%20just%20be%20so%20much%20better%20if%20the%20tiles%20could%20be%20organized%20as%20a%20raster%20without%20any%20customization%2Fscript%20adding.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-8975%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-8975%22%20slang%3D%22en-US%22%3EDitto%20for%20me.%20We%20are%20also%20struggling%20to%20work%20with%20navigation%20alongside%20%22modern%22%20experience.%20Not%20only%20that%2C%20but%20we%20are%20also%20struggling%20to%20explain%20our%20users%20that%20the%20%22Page%20not%20found%22%20is%20NOT%20a%20menu%20item%20gone%20wrong%20by%20us%2C%20but%20a%20bug%20which%20is%20not%20yet%20solved%20by%20Microsoft.%20On%20a%20different%20note%20though%2C%20the%20%22modern%22%20experiences%20in%20lists%20and%20libraries%20come%20a%20jolt%20to%20the%20users.%20Somehow%20our%20users%20find%20the%20%22classic%22%20experience%20cleaner%20and%20neater%20as%20compared%20to%20the%20%22modern%22%20one.%20The%20%22modern%22%20experience%20looks%20and%20feels%20more%20vanilla%20and%20unpolished.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-8661%22%20slang%3D%22en-US%22%3ERe%3A%20Structured%20Navigation%20(Publishing)%20not%20supported%20on%20%22Modern%22%20Sites%2FPages%2FLists%2FLibrari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-8661%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20pointing%20out%20these%20issues%2C%20I'm%20working%20with%20a%20client%20that%20is%20getting%20ready%20to%20move%20from%202013%20to%20SPO%20and%20we%20are%20trying%20to%20figure%20out%20how%20to%20reorganize%20sites%20and%20what%20to%20do%20about%20cross-site%20collection%20navigation.%20I'm%20really%20struggling%20with%20what%20to%20recommend%2C%20the%20rapidly%20changing%20functionality%20and%20lack%20of%20clarity%20from%20MS%20make%20it%20hard%20to%20design%20an%20IA%20and%20logical%20stucture%20that%20will%20meet%20future%20needs.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Brent Ellis
Valued Contributor

Creating a dedicated post to track this.  Lots of discussion on this from Yammer, and havent really seen this anywhere here yet..

 

What is the status of new "Modern" capabilities to support structured navigation?

 

What structured navigation gives us today:

  • Dedicated navigation page
  • Menu items can be permissions limited by groups
  • Visual interface to easily move up / move down / create folders

 

For years we have had users leverage this navigation structure, because it was easier for them to "grasp" and the extra features that you dont get with just the regular navigation.

 

Right now, we have almost 500+ sites that leverage structured navigation.  We have also as an organization put real emphasis on the Top Global Navigation menu, and not as much on the Left Side Navigation menu (which "Modern" seems to really key off of).

 

This is one of the items keeping us from moving toward the modern UI, so we dont have to go redesign the navigation of every site just to fit into the new modern world.

 

If we have to bite the bullet and just touch every site to make it fit in modern, it would also be nice to know that.

111 Replies

Thanks for pointing out these issues, I'm working with a client that is getting ready to move from 2013 to SPO and we are trying to figure out how to reorganize sites and what to do about cross-site collection navigation. I'm really struggling with what to recommend, the rapidly changing functionality and lack of clarity from MS make it hard to design an IA and logical stucture that will meet future needs.

Ditto for me. We are also struggling to work with navigation alongside "modern" experience. Not only that, but we are also struggling to explain our users that the "Page not found" is NOT a menu item gone wrong by us, but a bug which is not yet solved by Microsoft. On a different note though, the "modern" experiences in lists and libraries come a jolt to the users. Somehow our users find the "classic" experience cleaner and neater as compared to the "modern" one. The "modern" experience looks and feels more vanilla and unpolished.

Same here,

We are also now focussing more on the top navigation.

 

Next to that for every major site collection and major themed/departemental sites wa have a home - landing - page containing "promoted links"-tiles. These tiles make it visually very easy to find your way around between major related sites and collections.

Would just be so much better if the tiles could be organized as a raster without any customization/script adding.

We turned off the new library experience until the navigation issues can be fixed, the majority of our sites are publishing sites and we cant have the navigation not working correctly.  I do like the look and feel of the new lists and libraries but will not roll it out to our users until navigation works like it should.

Thanks for posting this. We have turned off modern sites until the navigation is working more consistently.

 

I think the Modern UI should give more tools for building navigation (tiles, menus, other controls).

 

You can go to the URL for Top Menu and delete off the excess menu choices.

https://tentant_name.sharepoint.com/_layouts/15/topnav.aspx 

 

It's like the Top Menu has the Structured Navigation plus a bunch of random stuff. Even though you only see one level of navigation, the second level is in there too.

 

Be aware though, every time you edit the true Structured navigation, the "extra junk" links all get added back. Very frustrating.

 

A work in progress no doubt.

 

Will watch this thread for more news.

 

Rob.

...and /_layouts/15/quiklnch.aspx would be for the equivalent quick/left navigation section. In light of no information coming forward about when the navigation will be fixed in modern libraries, I'm going to have a look at cleaning these two areas up on one site and trying out the modern library experience with some users.

Thank you,+1 here! Currently the only issue completely stopping us from moving the majority of libraries to modern. Would be nice to see this in the pipeline. I guess there are some major updates coming to managing navigation. Can't see why it would take so long to address this otherwise. Would at least be nice to have a temporary support, until something else is in place, so that we can start getting users up to speed on the modern libraries.

 

On a side note: I measured that the TTFB for opening our libraries is up to 10-15 seconds(!), unlike the new ones which are max 1 second. Yet another reason to move over.

Solution

@Brent Ellis (and others) - good news! We're finally pushing out a fix to support structured and managed navigation on modern pages/apps in classic sites.

 

With this update, if you have enabled publishing on a classic team site, your structured or managed navigation nodes will now render correctly in the modern pages (both global and current navigation), including any scoped or audience-targeted links. We haven’t pulled all the classic settings into the modern panels yet, so when you need to edit the navigation nodes the edit link will direct you back to the classic settings page (/areanavigationsettings.aspx).

 

We hope this unblocks folks who have been eager to move to the modern UX. Do try it out let us know if you have any questions. Thanks!

Still a few more roadblocks, but this helps remove one of the major ones!

 

achievementUnlocked.jpg

Thrilled to hear you are addressing this, thank you. A wish would be for MSFT to include updates like this one on the roadmap – making it a bit more detailed around the (post) rolllout of the modern experience. This would most likely reduce the confusion and number of posts here, all asking for the same thing.

Thats awesome, cant wait for it to rollout so we can start using the new lists and libraries once the navigation is working as it should.

Thank you!!

 

Is there something obvious we can see to know that our tenant has received this capablity?

 

Rob.

 

Hi @Sean Squires , i can't found anything on the fasttrack roadmap. When is this fix planned?

Oooh ooh, me want!   Looking forward to having this show up.  Any rough timeline?  Couple weeks?

Just noticed the update to the managed navigation, great news and definitely more user friendly already.

However it doesn't seem show sub-links at the moment, is this feature still to come? Thanks

We are having trouble with this. We have a modern Document library in a Sub-Site under a Site that uses the traditional UI. The modern is a test site.

We set the modern to be "Same as Parent" for Global, and Structural for Current navigation on the side. The document library is showing the Current navigation menus BOTH on the side and in place of the Global. Our true global is not shown at all.

I am not sure if we have the new code or not, not sure how to tell.

Rob.
That's what happens to us as well. I wrote a Powershell script that gets the root navigation, breaks the inheritance, and then updates the navigation in all sub-sites. Such a pain

Yes, I have only seen it working in one test susbite, while it doesn't seem to show in another. Not too sure why this might be, but glad to hear I am not the only one confused. Good to seeing things move forward though.

@Sean Squires any idea when this will hit all tenants? I'm having issues with Page not Found showing up in modern views even though it's tagged as hidden in the navigation.

I'm eagerly awaiting this as well.  So, with this in place, will the navigation propogate to all sites and subsites on all pages and have both/multi-levels as well? Ultimately, I guess my question is, will the navigation exactly mirror what's on the top level publishing site (if settings are set that way)?  I'd also know if there's a way to check this as right now I basically script our navigation to pushed out everywhere and would love to stop doing that.

Hi @Sean Squires, we are yet to see this.

 

Although the navigation is now settled up and the "page not found" link is gone, but the global (top) and current (left-pane) navigations are now the same. The actual global menu is now gone!! We have set it on our sub-sites to inherit from the parent site-collection, but somehow the new nav ignores that and makes the global navigation exactly same as the current (left) one. In our case, both are structural and not managed.

 

Further, the modern list/library still does not allow metadata filtering! We have set filters on term-sets, but in modern view that is not available. This new style is getting more furstating day by day. Our users still find the classic view more neat and clean. The new view looks very unpolished and unncessarily big.

@Abhimanyu Singh -- there's no way that what you're seeing with the global and quick launch being the same is how it is supposed to be (I hope).  At least, I hope that's not what Microsoft thinks is "fixed" or reasonable......... if so, they have pretty much destroyed the global navigation and any hope that people will move to modern sites quickly. 

@Clint Lechner see the screenshots that I took for both the classic mode (what it is supposed to be) and the modern mode (what is messed up):

 

classic.pngClassicmodern.pngSo-called Modern

@Abhimanyu Singh -- right, my point was that I hope that isn't what is supposed to be happening.  That's what I see as well and it certainly isn't what I consider to be working correctly.

Yup. Sad part is that Microsoft people aren't as active here as they had been on the older Yammer group. @Sean Squires are you listening?

This is a major flaw. I'd even open a support ticket just to get this documented, not that there is a solution for it.
Highlighted

Hi @Abhimanyu Singh (and others on this thread!) - my apologies for the radio silence on our part. I was away on family business and inquries on this thread were missed by others. I will review w/ the feature crew this morning and get back to everyone. We are trying to as attentive as we can to folks questions and feedback on this platform - so please do continue reaching out (and @mentioning us to ensure we get the notification)!

 

A quick summary:

  • There was a related issue that delayed the rollout of this feature fix - so some of you may not have seen the fix in your tenant yet. It is currently at 50% WW and will be fully rolled out in the next two days to all of production (read: 100% WW this week). Thank you for your patience.
  • Fair ask/feedback about inclusion on the roadmap - we work closely w/ our marketing partners to try and provide the right level of notice/visibility on feature announcements and major fixes; I will discuss w/ them further about adding this one there.
  • As noted, this fix is specifically to enable the modern page navigation controls to read from the same publishing provider as classic pages do (for team sites where publishing feature is enabled); in other words, excepting functional differences between the classic (i.e., "recent" node) and modern controls themselves, the rendered data should be the same (per the settings you designate on the areanavigationsettings page. Some of the discrepancies noted here sound like bugs - so thank you for reporting and we'll look into it immediately.

Thanks!

 

Fair ask - let me follow-up w/ our marketing partners and see what we can do for this feature fix. Appreciate the feedback!

I'm guessing my dev tenant which is 1st release still hasnt received it yet, because I am still seeing the page not found in the navigation which should be hidden.  

 

When you say rollout is that to 1st release tenants or for all tenants?

Hi Rob - a related issue/regression slowed the release of this fix. It will be fully deployed to all tenants this week. The easiest way to check is verify your navigation settings (assuming you have enabled publishing feature on a classic team site - it's the areanavigationsettings.aspx page: site settings > [look and feel] navigation) and test structural or managed nav setting w/ a modern page (i.e., document library, site contents, etc.).
Hi David - this week we will be fully rolled out to all of production. Let me follow-up on the notice on the fasttrack roadmap. Thanks.
Yes, this week! Thanks for your patience!

Hi @Philine von Guretzky - can you elaborate on your scenario? If you have enabled the publishing feature and wish to display subsites in the nav you'll need to set navigation to structural and select the option "Show subsites". If you are referring to displaying sublinks in a managed nav term set, we do display up to two levels. HTH.

Thanks for reporting, Rob - I'm seeing this, too, and this is definitely not as designed; you should be able to set "Display the same navigation items as the parent site" and render the parent node values in the subsite. We'll take a look.
Hi Paul - rolling out fully to PROD this week. Thanks for your patience!
Knowing who to @mention is challenging. I have learned a few peoples names over the years, but it is always just a guess on my part, if a list of contacts for topics/features/releases could be shared, then we would be able to address our comments to the correct people.

Thanks @Abhimanyu Singh - sounds like @Rob O'Keefe is reporting same. We'll take a look; the intended design is the modern page/controls use the same publishing provider navigation settings and render the data similarly.

 

As for metadata filtering on lists/libraries, we are working on a new experience for this that should be rolling out soon. Adding @Miceile Barrett for notice/comment on that feature.

We should be fully rolled out to First Release tenants...can you provide more detail on what you're seeing on your dev tenant? Thanks.

yep still seeing the page not found in both the global and current navigation for site collections in my dev tenant which is 1st release.  I was testing the publishing navigation in my dev tenant and it seems to still not be working correctly.  Let me know if you need more info to help troubleshoot this.  I have created a few new site collections and enabled publishing on them and seeing the same thing on all of them.

 

pagenotfound.jpg

Hello @Abhimanyu Singh, I am working on creating the modern list/lib metadata filtering experience and wanted to give you some updates on the progress. Currently, we have released a feature called "filters pane"  Filters Pane Help Article.  We have just rolled out to PROD so you can expect to see it within the week if you don't already have it! 

 

This feature is the first iteration for replacing metadata nav. The next months will be focused on cleaning up the UI, supporting term set filtering, and making sure metadata nav will no longer force users to back to SP classic.   

 

Best,

Miceile 

@Sean Squires -- to be clear, you're saying the intended functionality should have the modern pages duplicate/inherit the global navigation and current navigation?  Meaning the global and current navigation should not be the same, correct? 

FYI, for those people having issues where the global and current navigation is the same, an alternative is to use managed navigation for the top level for global navigation.  It seems that modern pages DO seem to inherit the managed navigation correctly.  Yes, I know, it's not perfect but things are inherited just fine that way.

 

Hey, it's a step.............

I use managed navigation for Global in my production tenant. When I switch a single document library into Modern mode I am now correctly seeing the first level of drop-downs from each of the top level items, but not the second (normally displayed as fly-outs to the right of the drop-down items). Also, I have a very simple Alternate CSS that makes the width of the drop-downs a bit wider, adds a separation line between each drop-down item, and highlights in blue the drop-down item as you mouse over it - none of those effects are displayed when I put the document library into Modern mode. The drop-down items are highlighted in gray when I roll over them. Still, it is considerable progress!
Also, I have one term that is marked not to display in the navigation. This is obeyed in the classic view, but in the modern view it is displayed.
Thanks a lot @sean. Much appreciated. Hope the fix lands soon.
Thank you @Sean. Hope to see this fixed soon. And thank you for pinging @Miceile on metadata filtering.

Thank you @Miceile Barrett. Yes, we can see the filter pane, but that includes only a limited number of the list fields and no metadata terms. We look forward for the full metadata filtering options. It is good to know that you are working on this. 

Any idea @Sean on who to mention / ping for UI/UX (on modern lists) feedback?

@Sean Squires- I've since found more problems with the managed navigation in Global. While the navigation looks fairly normal (except for the fact that the final level of navigation, the flyouts to the right, are missing), all the links drop "/sites/SiteCollectionName/" from the URL behind them, so none work. Also, for the links displayed across the top, I have to double click on them to go to the link (which, of course, has the wrong URL). The links in the drop-downs require only a single click, but, like the others, are missing the "/sites/SiteCollectionName/" part in the middle of the URL. This is a normal tenant - nothing in first release. All using IE 11.

 

Finallly, in classic mode, hovering over any of the links shows the URL at the bottom left of the browser. In modern mode, the URLs are not shown.

 

Related Conversations
flashing a white screen while open new tab
cntvertex in Discussions on
13 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
22 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies
PacketMon Components are not loading in WAC 1909
HotCakeX in Windows Admin Center on
2 Replies