User Profile
LincolnDeMaris
MicrosoftJoined Jul 21, 2016
User Widgets
Recent Discussions
Re: Upload folder allowed even when make new folder command is set to no in settings
Hello, Unfortunately, we have no plans to fix this issue and expand the scope of this setting to include more places. This setting is not by any means comprehensive today - it does not affect folder creation in mobile experience or synched locations either. Upload folder is just one of the "holes" in the present story.Re: Update: Document Sets in Modern Document Libraries
Hello everybody, I'm sorry to say I made a mistake. Modern Document Sets are currently 100% of Targeted Release. We're working on one more bug fix and will then move it as quickly as we can to all of production. I'm sorry for the confusion that my last message caused, as well as the delay of this rollout in general.Re: Update: Document Sets in Modern Document Libraries
reveler24 Modern document sets are rolled to all organizations. If you are still seeing the classic document set page, that should mean that either the library itself is configured to use classic, or the document set welcome page has been customized and we're detecting that and falling back to classic.Re: Update: Document Sets in Modern Document Libraries
Dudditz They have not been pulled. We had a temporary rollback because of an issue with the flight - it was not any of the issues being discussed here, it was a backend thing. Sorry about the confusion. Additionally, we have internal confirmation that the following issues have been fixed in production: Opening in a new tab Properties not showing Some of the breadcrumb click issues - we're still working on this New button not showing the correct items in a document set If anybody's still having difficulties with the above, please let us know.Re: Update: Document Sets in Modern Document Libraries
Hi all, I'm sorry to hear that many of you are having problems with document sets in modern. Move To/Copy To on document sets. The change that's rolling out does not enable any new move to/copy to scenarios on document sets. We hear this feedback and this is near the top of our backlog to address. Opening in a new tab. Before this change, document sets would open in a new tab in classic mode. After this change, they open in the same tab in modern mode. If folks are seeing document sets opening in modern mode in a new tab, that's very surprising - let us know for sure that the new tab behavior is indeed the modern document set view (as pictured at the top of this thread) and we'll look into this. Document set metadata. Document set metadata should be appearing in the details pane when inside the document set. If this is not happening, there's a bug we need to fix. If this is happening in your environment, please message me with the field types inside the document set content type and we'll try to reproduce, although your best and fastest recourse might be calling support. Document set views and content types. Document set views and content types as configured inside the document set content type should be respected. If this is not happening, we have a bug that we need to reproduce. Please send me more information in a private message - like what views and/or content types are present in the document set content type settings. A screenshot of the settings page could work wonders.Update: Document Sets in Modern Document Libraries
I am pleased to announce some updates on the plan and timeline for improving the Document Set experience in modern document libraries. In January, we communicated a March delivery date for these improvements. We apologize for missing that date. We’re now planning on rolling out this change in May. We will be making the official announcement to the Message Center very soon with exact dates. Thank you all for your patience! This change allows organizations to use the power of document sets to group related documents together with consistent metadata and structure without having to go back and forth between classic and modern experiences. Document sets now look and feel like ordinary folders in modern libraries, and benefit from all the cool new features in modern. This means that users can drag and drop content to upload to document sets, link to content that lives outside the document set, pin files to the top of the document set, start flows on document set items, and define conditional formatting on document set items. It also means that the Document Set experience can be customized using SharePoint Framework Extensions, just like all other modern list views. All the content management rules you can define on document set content types are still supported. No business processes were harmed in the making of this change! Document set metadata can be viewed and edited in the details pane while in a document set. Shared metadata specified in a document set content type continues to work as it always has; values inside shared columns will be copied to items inside the document set. Columns that are identified as Welcome page columns in the content type are sorted to the top of the details pane, so that users can find them easily. Content and structure rules specified in the document set content type are also supported, including the default content and default view settings. Document set versioning functionality will appear under the context menu on document set items in the modern list view, include “Capture Version” and “Version History.” Other document set-specific actions from the Document Set ribbon are still there, but only in classic. Just like any other modern list view page, you can click “Return to classic SharePoint” in the lower left hand corner to go back the classic document set experience back. The one caveat is that customized document set welcome pages are not supported in modern. This change will not affect document sets that use welcome pages that have been configured with custom HTML or web parts; those welcome pages will still be displayed in classic mode, as they are today.Re: Update: Document Sets in Modern Document Libraries
SWalter2937 We posted the official announcement to the Message Center yesterday. Modern document sets rollout will begin early May! Deleted I think that everything you're using Document Sets for, as evidenced by your screenshot, will continue to work with this change. Document set metadata is displayed in the details pane. Default content that's specified in your content type will be created by default. You can configure which view is used to display document set contents.Update on modern list tenant opt-out removal
In January, the SharePoint team announced that we are removing the ability to opt an entire tenancy out of modern lists. That announcement said that we would start this rollout on April 1 st , 2019. This post is an update of where we are with this rollout, and when you can expect this rollout to affect your environment. We are rolling this out in two waves: an early wave, and a late wave. Start dates for these waves are as follows: Early wave: Rollout will begin April 24, 2019 and conclude by the end of May. Late wave: Rollout will begin June 3 rd , 2019 and conclude by the end of June. Every tenant is in either the early wave or the late wave. All tenants in the early wave received the following message in the Message Center in early April: MC177122 Reminder: SharePoint tenant opt-out for modern lists is retiring in 2019 If you did not receive this message in your tenant, then that tenant is in the late wave. We’ll make this reminder post to the Message Center for late wave tenants towards the middle of May. Many of you have asked for the ability to predict exactly when this change will affect your environment. Unfortunately, we are not able to do that – this change, just like our other changes, will roll out slowly over the course of an entire month. However, there is a way to take fate into your own hands. Since all this change does is remove the tenant opt out mechanism for modern lists, you can preempt our rollout cadence and make the change yourself as early as you’re ready. Simply enable modern lists in SharePoint admin center! All the change does is flip this switch on your behalf; by doing it yourself, you can control precisely when your end users will be impacted. In our conversations with customers about this change, we’ve learned that many organizations are relying on their end users to identify the lists in their environment that need to stay classic, and opt those lists out of modern. We’ve made a small change that makes it a little bit easier for an end user to opt a whole site collection out of the modern experience. The site collection feature that opts all the lists in that site collection out of modern previously required PowerShell to activate; now it appears in the Site Collection Features UI. If need be, Site Collection Owners with no PowerShell access or abilities can find this feature on this page and activate it to keep all lists in that site collection in classic: SharePoint Lists and Libraries experience Activate this feature to turn off the new SharePoint list and library experience for this site collection Many of you are crafting internal communications to let your users know this is coming. We definitely consider this a best practice for large changes like this. In these communications, linking to this new article from us can serve as an introduction to what is happening with this change, why folks should be excited and not concerned, and how they can opt some lists out if they don’t want to embrace modern yet.
