Renee Barnette
My feedback
-
4 votesRenee Barnette
supported this idea
·
-
18 votesRenee Barnette
supported this idea
·
-
618 votesnot in our plans right now ·
AdminSites Product Team
(Product Owner, Microsoft SharePoint)
responded
Thank you for submitting this suggestion and voting on it. We have two events/calendar solutions in modern pages today. The events web part has card based event tiles, powered by events lists. You can roll-up events from multiple sites into one page, but there isn’t currently a wall calendar view.
Alternatively you can select to leverage a group calendar, and pull all of your events (including recurring events) from Exchange. This too is a compact card based view.
While we understand a wall calendar view is desirable, we’re not working on it at this time.
Renee Barnette
supported this idea
·
-
700 votes
We’re actively thinking about how we can better support the desire for a great looking, responsive, wall calendar view. As we solidify our thoughts, we’ll share more.
Renee Barnette
supported this idea
·
-
308 votesRenee Barnette
supported this idea
·
-
44 votesRenee Barnette
supported this idea
·
-
11 votesRenee Barnette
supported this idea
·
-
165 votes
An error occurred while saving the comment Renee Barnette
supported this idea
·
-
57 votesRenee Barnette
supported this idea
·
-
15 votesRenee Barnette
supported this idea
·
An error occurred while saving the comment Renee Barnette
commented
I agree with this.
If this could not be hidden, I request that Microsoft at least add a warning, along with a link for what the recommended best practices are for avoiding being throttled due to use of what is not recommended.
-
310 votes
We’re working on audience targeting in hub navigation. Hub owners will be able to set who should view certain links and those links are filtered out.
Trimming based on a users access to the site or resource is not in the plans.
Renee Barnette
supported this idea
·
-
7 votesRenee Barnette
supported this idea
·
An error occurred while saving the comment Renee Barnette
commented
I also request that the calendar events all have the option to pick the time zone, and then have the calendar event display the time zone in the calendar, so it is obvious, as there are people who use calendars across various time zones, so they don't have to figure out what zone the website's administrator has set it to be, or connect the calendar to outlook if they can't get a hold of the site owner.
-
3,599 votes
Thank you everyone for your feedback on this item. We recognize this is a valuable feature and are looking at ways we can address it. We do not have a timeline to share at this point.
Renee Barnette
supported this idea
·
-
2 votesRenee Barnette
shared this idea
·
-
42 votesRenee Barnette
supported this idea
·
-
126 votes3 comments · SharePoint Administration » on-premise Central Admin · Flag idea as inappropriate… · Admin →Renee Barnette
supported this idea
·
-
14 votesRenee Barnette
supported this idea
·
An error occurred while saving the comment Renee Barnette
commented
Thank you for this suggestion.
I would like to see this, if not for users to view, at least for those who can manage permissions, such as those with Full Control (if not possible at that level, then for Collection Administrators), so those responsible for managing permissions can determine more easily where users have access, and the permission level granted, through the site structure.
-
35 votes3 comments · SharePoint Hybrid And Migration » SharePoint Insights · Flag idea as inappropriate… · Admin →Renee Barnette
supported this idea
·
-
4 votesRenee Barnette
shared this idea
·
-
35 votesRenee Barnette
supported this idea
·
Currently I see the following warning for structural navigation in SharePoint Online, Site Settings, Navigation Settings:
(Structural navigation has significant performance impact and is not recommended in SharePoint Online. You can find more details here.)
...and no warning for use of managed navigation with navigation security trimming enabled.
Please update the warning for structural navigation to include stronger/more visible (color, or bolding, or highlighted) text, and the word "Warning"; if possible, make the text in red, at least the word "Warning" in red, something like:
(Warning: Structural navigation has significant performance impact, is not recommended in SharePoint Online, and can contribute to throttling of your entire tenant, affecting functionality and performance of all websites. Read navigation recommendations here.)
For managed navigation, please add a warning to set navigation security trimming to off to avoid risking latency, such as:
(Warning: Managed navigation, while navigation security trimming is enabled, can impact performance in SharePoint Online. If you use managed navigation, it is recommended to disable navigation security trimming. Read navigation recommendations here.)
I ask this because navigation for SharePoint on-premises has worked perfectly fine for many years, and I believe website owners are not aware (and difficult to keep informed distributed across a large enterprise) and may not take the current warning to heart, as they're used to all of the navigation options working fine, and structured navigation had been such a reliable, self-updating, easy to use feature for so many years, on-premises.
We're trying to get the potential issues found on our tenant resolved (after recent resolution of latency, 503 errors, and troubleshooting finding one specifically deeply nested offending site out of thousands), however, even if we were to go through and brute-force change offending/potentially offending navigation - - only the warning would stop any of the website owners from going back and setting it back, especially with turnover in such a large org; keeping uninformed/new website owners from setting new sites to use these navigation types/settings would be difficult.
As long as it's available, and it is such a huge known issue, the warning needs to be made very clear and extremely obvious. I think even a pop-up on selecting them, with a bold warning of potential impact, would be in order, but unless/until that is done, or the option to set these is removed, the quickest way to address the issue would be to have the text updated to be extremely obvious, and very clear that a single website owner's choice to use structured navigation (and the potential issue with managed nav w/security trimming) could cause every website in a tenant to be affected.