Forum Discussion
Document libraries - name field linked or calculated from other fields
Hello,
We're in the process of upgrading to Office365 from on-premise. I'm working on understanding SharePoint365, Teams, etc. I'd like to share a use-case which just came up and discuss the current pain points we're facing to see if anyone can provide recommendations (or how to submit a feature request).
I created a private channel in a Team to coordinate on grant applications. Since this is a private channel- a 365 Sharepoint site was created for it. We'd like to use the default document library (Shared Documents) - already mapped to files tab in Team channel to track additional grant data. I enabled/created a DocumentSet on the site, added this content type to our library, and created a new view to show these additional properties. Pain points:
- It seems there STILL isn't a way to have a meaningful Name.....
- such as:
- Have sharepoint calculate the name of an item - i.e. Name = [Field1] + "-" + [Field2]
- Create a calculated column based on Name
- Work arounds:
- I would typically create a new property- such as "Grant Number" and create a workflow in sharepoint designer to set "Grant Number" = "Name". However, I cannot do this as:
- We've disabled / don't have access to Power Automate
- Workflows / sharepoint designer are depreciated
- I would typically create a new property- such as "Grant Number" and create a workflow in sharepoint designer to set "Grant Number" = "Name". However, I cannot do this as:
- such as:
- Per folder views
- I'd like to default to a specific view to show the additional grant properties when browsing. Unfortunately, the methods listed https://camerondwyer.com/2014/01/06/harness-sharepoint-default-views-at-different-navigation-hierarchy-levels-to-build-more-appealing-solutions/ won't work.
- I can't change the content type of the parent folder as this is managed in Teams. I cannot find how to change this in Teams
- I'd like to default to a specific view to show the additional grant properties when browsing. Unfortunately, the methods listed https://camerondwyer.com/2014/01/06/harness-sharepoint-default-views-at-different-navigation-hierarchy-levels-to-build-more-appealing-solutions/ won't work.
1 Reply
CraftyMittens42 JFYI, SharePoint 2013 designer workflows are not yet deprecated by Microsoft. Only SP 2010 workflows are deprecated.
Please consider giving a Like if my post helped you in any way.