User Profile
Dudditz
Iron Contributor
Joined 7 years ago
User Widgets
Recent Discussions
Re: SharePoint document set as Teams Tab
JoanelleFryx_n-9th Hello, I simply want to map the inside of a document set like you can with a standard folder in SharePoint in a TeamsTab. Folders work, Document sets do not. Pretty common that companies create documents sets for projects and would want to see a just the contents of a related document set rather than the entire library.3.3KViews0likes5CommentsSharePoint document set as Teams Tab
I been testing adding folders as a team tab and these work fine. Also, adding a library that contains document set's also works fine and the document sets seem to browse and operate as expected. When adding a document set URL it produces the error below. The same exact process with a folder works. It's a bit surprising this does not work as the document sets do work when adding the entire library however a specific document set like adding a folder does not work. Any feedback is appreciated.3.4KViews0likes13CommentsCommunication Site Vertical Section Dimensions
As of today we noticed that the vertical section on several of our sites seems to have changed size or rendering various app differently than yesterday. For example, the call to action webpart displayed in the vertical section today looks smaller, image is a bit squished looking. We have some powerapps that we display in the vertical section on various sites that previously never displayed scroll bars and as of today all of them are displaying scroll bars. Not sure whats going on here however seems like overnight or recently vertical section dimensions have changed.1.3KViews0likes3CommentsRe: Add "Other" Option has disappeared
Raya_Anderton Indeed I can confirm Add Other option is missing on Standard forms however its there for Forms PRO. Has this basic feature simply been pulled without any communication and transitioned to only Forms PRO? Seems like a ridiculous concept if this is true or possibly a bug?34KViews1like2CommentsRe: Update: Document Sets in Modern Document Libraries
Hi LincolnDeMaris I believe we have discovered a bug when using modern document sets with the new flow action create folder. The action creates sub folders just fine under document sets however when you have any shared columns enabled the following error is generated in flow. "One or more field types are not installed properly. Go to the list settings page to delete these fields." Creating sub folder using the create file connector works fine with shared columns enabled however this is not desirable when your creating lots of sub folders as it leaves a file behind you have to deal with. Also the Plumsail connector works fine when creating sub folders with shared folders enabled. I have a ticket open with Microsoft and will share this information with them however its not clear this will get any traction. It would be nice to see this fixed as this create folder action is the correct way to be creating folders and the create file action is more or less a work around with undesirable results. See here for more information4.2KViews0likes0CommentsRe: Update: Document Sets in Modern Document Libraries
LincolnDeMaris It sure would be nice to get an update on what the current status of Modern Doc sets are. Have they officially been pulled? Sounds like many are saying including the organization I work for had them and now they are gone.8.2KViews0likes24CommentsRe: Update: Document Sets in Modern Document Libraries
JustSpoor Same here, Seems like the updated icon is still there however they have reverted back to classic experience. Far to much stumbling for such an important update. I question if Microsoft really understood those that use these depended on them in their ECM processes.8.3KViews2likes0CommentsRe: Update: Document Sets in Modern Document Libraries
Another thing, The welcome page does not seem to respect which columns you are actually showing and not showing within the Document set settings. It simply shows all columns after the modernization regardless if they are selected or not selected. I am trying to stay positive here however whats the point on releasing something with a key component such as the welcome page not working correctly. You use the welcome page to create a document set so it's not like this is an optional feature that you can simply disregard.29KViews0likes0CommentsRe: Update: Document Sets in Modern Document Libraries
LincolnDeMaris If you are using custom folder content types within the modern document set they use the classic form similar to the classic welcome page that is used when creating new document set. This in combination with the classic welcome page results in a fragmented experience for our organization. The very thing one would have though would have been eliminated by the modernization of the Doc set sill exists.29KViews0likes1CommentRe: Update: Document Sets in Modern Document Libraries
Lanceter Please consider voting for moving & Copying of modern Document sets. You can find the suggestion here in the user voice. I also added a user voice for replacing the classic welcome page with a modern one when creating new document sets however it still has not shown up, will check back tomorrow.32KViews1like1CommentRe: Update: Document Sets in Modern Document Libraries
osborn_amy It's quite strange that the welcome page is opening a new tab and is classic while the rest is modern. I am pleased that we have this update even though it feels unfinished. Our bigger concern is you still can't move these like other folders within SharePoint, You can only move them within the context of their respective library.33KViews0likes1CommentRe: Update: Document Sets in Modern Document Libraries
Thank you for the update, we are patiently waiting and are looking forward to this release. Hopefully we can use the move function within Modern libraries to move the Doc Set to another library and or Collection as needed for Archiving purposes like you can with files & Folders. Something to consider, Within the enterprise document handling is often tied to a Customer, project, etc. generated from a LOB system. Often this data exists upstream so it would make sense one would wan't to generate the document set, folder, etc. from an upstream process rather than a manual process within SharePoint. I would really like to see the ability to be able to create Document sets & Folders directly from PowerApps. In my opinion most organizations rarely start their enterprise ECM processes from within SP and often begin well before we get to SharePoint. This would really take Document sets to a new level. Currently to do this you have to use a variety of work around's by writing your values to a SharePoint list and 3rd party tools to finally take the values and generate a Doc Set.63KViews5likes3CommentsRe: What is the plan for "modern" Document Sets?
Looking forward to using these, Something to consider, Within the enterprise document handling is often tied to a Customer, project, etc. generated from a LOB system. Often this data exists upstream so it would make sense one would wan't to generate the document set, folder, etc. from an upstream process rather than a manual process within SharePoint. I would really like to see the ability to be able to create Document sets & Folders directly from PowerApps. In my opinion most organizations rarely start their enterprise ECM processes from within SP and often begin well before we get to SharePoint. This would really take Document sets to a new level. Currently to do this you have to use a variety of work around's by writing your values to a SharePoint list and 3rd party tools to finally take the values and generate a Doc Set.4.8KViews0likes0CommentsRe: What is the plan for "modern" Document Sets?
Ian out of curiosity how big is your environment, number of users, sites, etc.? For the metadata consistency across site collections I used to use the Content type hub, package term store AKA manage metadata columns into content types and publish these to all site collections. I do not believe the Content type hub is compatible with group sites. I never was a fan of using this, it was not very flexible and a good way to fill your sites up with columns and content types and no simple way to remove items you no longer needed. Some of the concepts you are talking about I feel like SharePoint is moving away from and becoming more and more dynamic, nimble, collaborative, etc. Like you I often used to stride to drive consistency across every collection, etc. Focused on extensively using managed metadata, required columns, enterprise search centers with extensive usage of refiners, custom search results, etc. Those concepts while still important seem challenging to execute within the modern SP and the focus for us has shifted to providing more user-friendly experiences such as surfacing the document libraries though teams channels, building power apps and embedding in SharePoint sites & Team channels. Mobility for our organization is more important than extensive usage of metadata and the interesting thing is folders are mobile friendly while metadata is not so much. For example, browsing a document library with one level of folders works great on a mobile device through the OneDrive app or offline file sync makes sense when you have a layer of folders for file organization however with only metadata you have a folder of files with no organization. It's kind of bizarre to think we are now building solutions that are using folders when for so many years we did everything possible to avoid them. We still use metadata extensively when appropriate however mostly with a 3rd party form designer called Infowise, it's much more than a form designer. We will often use it for cascading columns, column validation, associated items or repeating tables. It can provide a lot of added value with driving metadata consistency with it's ability to use logic to default metadata based upon conditions and validation. We also use Infowise to pull data from other LOB systems such as SQL and use this data to pre-populate fields in forms & document libraries. We are building an enterprise document handling solution with Infowise that consumes values from our ERP, Microsoft Dynamics Finance and operations and automatically builds a document set for every project we open in Dynamics. It passes about 12 values and automatically names the document set, sets project managers, emails people, sets security, and populates additional metadata columns for consistency and data findability. With this scenario you can even have a unique document set for each department and each document set has unique and common company content types embedded within them. Since the department is one of the fields that comes from dynamics we use some logic in the Infowise action to automatically create the correct type of document set. It's a very powerful concept and I believe concepts like this can replace trying to create a standardized document library with a specific site column across every site collection. Also, since it's centralized you are not managing 100', or even 1000's s of document libraries. If you prefer to use multiple doc libraries this is also easy to perform within the Infowise actions during document set creation. For example, if department = A use Doc set A and create in document library A. The solution was built with the legacy document sets and we are now waiting for the modern document sets before going live. Regarding looking data across site collections, are you referring to a lookup column to consume a value from a central list? Have you considered adding these values to the term store than creating a column that points to the correct hierarchy within the term store? You can use this method and have some interesting hierarchies. You can create this as a site column which can be added to every collection and added to any list or library. Previously the content type hub would allow for this to replicate to every collection however this is probably no longer the case with it not working with group sites. That said, as mentioned above any serious document handling for organizational processes such as Project Management, sales, HR, etc. I find using some of the methods mentioned above with a good 3rd party tool to be more manageable than using some of the legacy concepts across 100’s of site collections. Simply put, smaller footprint, less libraries, and investment in a good tool will make it more manageable and open opportunities up in how you facilitate the metadata. We use Sharegate to quickly copy lists, column, content types, etc. from collection to collection. There are some great tools out there for moving/migrating data including Sharegate and Microsoft has just released a new version of their migration tool.4.9KViews0likes1Comment