User Profile
LincolnDeMaris
MicrosoftJoined 9 years ago
User Widgets
Recent Discussions
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.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.Column Formatting - now with Flow button support
One scenariothat we demoed at Ignite last year was the ability to create Flow buttons using the SharePoint column formatter.The initialpublic release of the column formatter, however, did not include this functionality. We're proud toannounce that allSharePoint Online users can now create their own Flow buttons inside column formats. This is useful when you want to put a business-critical Flow asingle click or tap away for userswhen they're viewing a list or library. To learn how to accomplish this, checkthe Create a button to launch a Flow sample on our documentation page. Let us know any feedback or concerns you have about thisfunctionality, or aboutcolumn formatting in general.Column formatting now rolling out to first release users
Hi all, I would like to update you all on the rollout progress of the column formatting feature. Today, we begun rolling this feature out to first release users. All first release users will have the capability by the middle of next week (Wednesday, November 8th). After that, we'll begin rolling out to first release tenants. All tenants worldwide will have this feature by the end of November. Here are some handy links to help you get started with column formatting: My session from Ignite 2017 where I talk about many of the newcapabilities in lists and libraries, including column formatting. Skip to 29:50 to view the portion of the talk devoted to column formatting. Column formatting overview - a high level overview of the column formatting capability Column formatting reference documentation - complete technical documentation on the capabilities provided, including many samples that will help you get started Community sample repository - this is a Git repository where you can contribute useful samples that demonstrate how to use the feature, or accomplish common user scenarios. We've seeded this repository with some of the samples from our reference documentation, and we're hoping to see lots of submissions from the community. We are very eager to hear your feedback on this feature, and hear your suggestions on how we can make it more useful.Guidance and API for determining rendering mode for a list
Hi everybody, We frequently hear customers ask, "Why is this listin classic mode? Modern experiences are enabled at the tenant level, but this liststill uses classic mode - what's going on?" We've released some new API thatallows you to determine, given the URL of a list, what rendering mode that list will use when visited in the browser, and if that rendering mode is classic, what feature or setting is causing that to happen. Learn more about this API here. Let us know what you think!Use the Quick Links web part to put your content front and center
Don’t bury your lead - put important stuff right up front for your site visitors. The Quick Links web part allows you to add visibility to the most important content you create – with the ability to adjust and curate as you go. We’re pleased to announce a small but important improvement we’ve made to the Quick Links web part. You can now adjust the image that represents your link inside Quick Links cards. This often-requested update will be available to use in this web part on all modern pages. Let’s say you’ve been using Quick Links on your modern team site home page to showcase important team resources – it might look something like this: If you want to swap out the default images with something that's more visually engaging, or more appropriate in the context of your site,find the tile you want to change, and select Edit: This brings up the edit pane, where you can change the link's title, or its image: You can upload an image, or use one that's already in your site. You might wind up with something that looks like this: We hope that this feature will help you create more beautiful, engaging SharePoint sites. As always, we would love to hear your feedback. How can we continue to improve this web part, and all our modern web parts, to best meet your needs now and in the future?Custom field rendering in modern list views
Hi SharePoint Developers, We're working hard on making modern lists and libraries more extensible. One feature that we're working on right now is a SharePoint Framework component that allows you to customize the rendering of fields inside modern list views. In other words, this is a modern version of the classic Field.JSLink extensibility point. We want to work with you guys on fleshing this out and enabling real scenarios that are currently blocking modern adoption. We'd like to gather more real-world examples of how people are customizing fields inside list views today. Please help us out! To get things started, below are a few field customization patterns that we're aware of and are considering how we can make them work with this new framework component. We want to hear from you examples of scenarios that fit one of these patterns as well as scenarios you've encountered that are totally different. Conditional formatting. This is applying a different style to a field depending on its value. Example: I have a number field in a custom list called "KPI." I want values between 0-20 in this field to be shown in the list view as red; 21-40 as yellow; 40+ as green. Supplementing the output of a field with more information. This is displayingadditional data inside a field alongside the data that's displayed by default. Example: I have a person/group field that stores contact information. I want to display the name of the person's division next to their name. Inserting links to actions. This is placing links to actions on a list item within that list item's row. Think of this as like a URL-based customaction, but the action is invoked by clicking the action's URL in the view instead ofselecting that item and clicking abutton. We've heard that sometimes it's easier to train people to click a link in a row than it is to train them to select the item and find the right button in our menus. Example: I have a field in a document library called "Kick off Approval Workflow." Client side code constructs a URL that kicks off an approval workflow (in SharePoint or in another system) for the item in question and places that URL inside that column.Groups get SharePoint: Update on rollout
Hi all, Here's an update on the rollout of Office 365 Groups getting the full power of SharePoint sites. This is the change that we announced at the end of August in this blog post. Currently,all First Release tenants have this capability; all Groupsin first release tenants have an associatedSharePoint site that you can do tothrough SharePointHome, the "Home" link in left navigation inside the files view, or the "Site" tab in Outlook. Tomorrow,we will be launching these capabilities to firstrelease users as well. Normally, we flight new features like this to first release users first. We did this feature differently because there's no way to isolate the change to just particular users in the tenancy - once a group has been provisioned or upgraded to contain a full site, that's visible to allusers in the tenancy who visit this group. Initally, we didn't think it was appropriate to expose this change tonormal users who just happen to be inside tenancies where there are first release users who are giving this new capabilitiy a try. Things are different now - the feature has been live for over a month, and we are seeing healthy usage and gettingquality feedback. In the second half of November we'll begin rolling outthese capabilities to production tenancies outside of first release - we'll post again to let you all know this is starting to happen.
