User Profile
ssquires
MicrosoftJoined Aug 10, 2016
User Widgets
Recent Discussions
Re: Selected Group Language not honored by created Sharepoint site
All correct - for folks monitoring this thread please note the recent blog post we published around self-service site creation updates: https://techcommunity.microsoft.com/t5/Microsoft-SharePoint-Blog/Updates-to-SharePoint-self-service-site-creation/ba-p/218971 - which includes a new language selector to set the default site language at creation time to something other than the default tenant language. Note this only sets the site language, not the group mailbox language. Hope this helps!4.5KViews0likes3CommentsRe: Structured Navigation (Publishing) not supported on "Modern" Sites/Pages/Lists/Libraries
Hi RichardSharp11 - thanks for the detailed reply/feedback. Great to hear that the recent updates are enabling you to move forward with using modern library ux. I'll take a look at that behavior w/ "no url" to evaluate whether there's more we should do there. I am keen to get this functionality working w/ modern templates so we'll keep the community posted on our progress there. RE: other items: #1 - inconsistent status toast of L2 items - I've bugged so we can take a look at. Thanks for reporting. #2 - interesting; I'd thought w/ the client-side improvements we'd made here it was faster. We'll take a look, but let me know if this persists. #3 - yes, I'm seeing that now, too - and agree the flyouts shouldn't persist when you move cursor focus away. I've bugged for investigation Re: your last comment on classic publishing template - there is likely more work to do there on our side. We haven't done much w/ that template in favor of the new communication template. I'll note and forward feedback to the team. Thanks again! Sean2.5KViews0likes5CommentsRe: UPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Hi Beilul Brhane - not completely at this time (though I've heard of folks manipulating the page client-side after load). You can disable the quick launch in navigation elements setting (_layouts/15/navoptions.aspx) - but we still render the recycle bin outside of this setting so it will still display. We are looking to modify this, but no ETA at this time.2.9KViews0likes0CommentsRe: Structured Navigation (Publishing) not supported on "Modern" Sites/Pages/Lists/Libraries
Hi RichardSharp11 - I think we're there! But I want to make sure I understand your configuration. I'm not sure I understand how you have Leve 0 implemented to render in the nav if your L1 is the header node. I assume you are using term-driven pages? If I configure simple links for each child node each one works: that is, I create a global nav w/ managed navigation and set up L1 (global nav), L2 (drop-down), and L3 (fly-out) nodes (all w/ hyperlinks) - they all work as expected. If I set up the child nodes as term-driven pages I seem to get the correct URL path and behavior: /L1/L2/L3 (which is relative to the parent site so the URL for the L3 page would be https://domain.sharepoint.com/teams/ssquires/L1/L2/L3 ). I haven't configured any other target page settings, so let me know if you're doing something different. As for collapse by default - yes, we are evaluating changing the home page behavior to default collapsed (which would also make it consistent w/ the libraries). Thanks for the feedback here.2.6KViews0likes7CommentsRe: UPDATE: Create Office 365 Groups with team sites from SharePoint home moving beyond First Release
That's right Salvatore Biscari, mgable_presidio - we haven't updated the sub site creation experience yet so currently your only choices there are "classic" templates (yes, we are working on this - more to share in the new year). As Salvatore notes, most of the modern team site elements are available in the classic team site (modern site contents, document library, site pages w/ client-side web parts, etc.) - and the site by default will inherit permissions of the modern parent site's group.5.3KViews0likes0CommentsRe: UPDATE: Create Office 365 Groups with team sites from SharePoint home moving beyond First Release
That's right - thanks Salvatore Biscari - but SoonhoKim note that the subsite can either inherit the parent site's group permissions (default) or be set up w/ unique permissions.5.2KViews0likes0CommentsRe: Structured Navigation (Publishing) not supported on "Modern" Sites/Pages/Lists/Libraries
Hi Paul Martello - correct, I was referring to the classic publishing feature. No, unfortunately that scenario isn't supported at the moment as the communication site doesn't use/display the top link nav bar (which is what would be inherited down to the subsite). Even enabling classic publishing wouldn't fix this - and you can't activate it as it conflicts w/ the new publishing model. We are evaluating how to best support sub sites in the new modern site templates, but nothing we can share at this time. Your best workaround is to manually add the reference links you need to the sub site.2.7KViews0likes1CommentRe: Structured Navigation (Publishing) not supported on "Modern" Sites/Pages/Lists/Libraries
Hi Robert Schouten - yes, it's currently using the same nav provider (the work we did earlier this year was effectively to ensure the modern control behaved similarly to classic one for consistency on those classic sites where publishing infra feature was enabled) - so it will be bound by the same functionality and limitations. As for support on modern sites - yes, something we are looking into, but no specifics I can share at this time. Thanks.2.8KViews1like9CommentsRe: UPDATE: Create Office 365 Groups with team sites from SharePoint home moving beyond First Release
Hi Sucheta Patil - you can do some degree of customization on modern sites using PnP PowerShell (check out: https://msdn.microsoft.com/en-us/pnp_articles/modern-experience-customizations) - but we also announced - and will start rolling out next month - support for site scripts and site designs (check out this Ignite talk for more details: https://techcommunity.microsoft.com/t5/Microsoft-Ignite-Content-2017/Using-custom-themes-and-designs-to-standardize-the-creation-of/m-p/109118#M1406). Thanks!5.3KViews1like0CommentsRe: UPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Of course - and yes, missed your note that you were looking to edit horizontal. In modern team we're moving to a left, vertical nav only - but will materialize the classic horizontal nav if you have subsites. You can, of course, continue to edit the toplink nav bar directly, but only through classic settings/page. Thanks.8KViews1like2CommentsRe: UPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Hi Peter Mcdermott - if you have sufficient permissions you should see an inline edit button that allows you to add, move, and group navigation links. From the pages library there's also an option in the context menu to add to the navigation. Take a look at this article for more details: https://support.office.com/en-us/article/Customize-the-navigation-on-your-SharePoint-site-3cd61ae7-a9ed-4e1e-bf6d-4655f0bf25ca?ui=en-US&rs=en-US&ad=US (let us know if you have other questions). Thanks!8KViews1like4CommentsRe: UPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Hi Adrienne Kidd - terribly sorry to have gone dark on you. I was out of town and thought an update was shared. The regression took a bit longer to isolate and fix, but I'm happy to report that a fix is in and should be rolling out this week (fully in by end of week). I'm looking into a related issue w/ the browser status reporting the URL of the node w/ focus, but the L2 and L3 links are correctly rendering. Thanks for your patience!7.7KViews0likes0CommentsRe: UPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Adrienne Kidd - very sorry about this; we validated this very scenario when we rolled the fix out earlier this month - but I'm now able to repro, too. I have an engineer investigating.7.9KViews0likes11CommentsRe: SharePoint Online File Editor Won't Save Changes
Thanks for reporting, Mark Rackley. We've confirmed repro (seems to be an issue w/ text editor control only in SharePoint; works fine in ODB). The engineering team is investigating and will get a fix out as soon as possible.14KViews0likes22CommentsRe: UPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Glenn Goldberg, DenisT Scott Joyner, - Sorry I missed these comment last week - yes, we learned there was a regression that broke the rendering of the L3 URL. A fix has already been patched and should be rolling to PROD. Apologies - thanks for your patience!8KViews1like0CommentsRe: UPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Sorry I missed this comment last week - yes, we learned there was a regression that broke the rendering of the L3 URL. A fix has already been patched and should be rolling to PROD.8KViews0likes0CommentsRe: UPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Hi Adrienne - you beat my announcement! The fix to support L3 links in managed nav horizontal orientation had to be made in two different code bases. It might have still been rolling through. I'll check a test tenant, but let me know if you don't see it next week. Thanks!8.1KViews0likes2Comments
Recent Blog Articles
No content to show