We are trying to benefit from using folder structures and managed metadata to store our SharePoint documents. so i created a term group >> with 2 term sets >> named "client" and "Doc Type", as follow:-
and at the same time we are storing the files into this folder structure as follow:-
-ClientName
-DocType
-the documents
as follow:-
now i want to know if it is possible to populate the new documents with the 2 managed metadata fields based on the Parent folder name and the subfolder name? for example if i upload a document inside the Proposals sub-folder which is under ClientC parent folder>> to have the Client metadata for the newly added document = ClientC & the DocType metadata = Proposal ? and so on.. can anyone advice?
Solved! Go to Solution.
Hi @johnjohnPter,
I think in the same thread they also tried add new defaults without removing the old ones. But if you have already tried it lets go for your own suggested approach.
I would use the Full Path property and split it on the / character. In that case you could use the 2nd and 3rd item of the returned array.
Below is an example
1. Via a split expression the Client and DocType are retrieved
Client
split(triggerOutputs()?['body/{FullPath}'], '/')[1]
DocType
split(triggerOutputs()?['body/{FullPath}'], '/')[2]
2. Those are used in a couple of HTTP requests to retrieve the term id of the corresponding label
URI Client
_api/v2.1/termStore/groups/@{variables('TermGroupId')}/sets/@{variables('ClientTermSetId')}/terms?$filter=labels/any(a: a/name eq '@{split(triggerOutputs()?['body/{FullPath}'], '/')[1]}')
URI DocType
_api/v2.1/termStore/groups/@{variables('TermGroupId')}/sets/@{variables('DocTypeTermSetId')}/terms?$filter=labels/any(a: a/name eq '@{split(triggerOutputs()?['body/{FullPath}'], '/')[2]}')
I also got a blog about that approach:
https://www.expiscornovus.com/2022/12/29/get-terms-by-label/
3. With concat expressions they are used in an update file properties action (as a custom value)
Client
concat(split(triggerOutputs()?['body/{FullPath}'], '/')[1], '|', outputs('Send_an_HTTP_request_to_SharePoint_-_Client')?['body']['value'][0]['id'])
DocType
concat(split(triggerOutputs()?['body/{FullPath}'], '/')[2], '|', outputs('Send_an_HTTP_request_to_SharePoint_-_DocType')?['body']['value'][0]['id'])
Below is my test result.
Hi @johnjohnPter,
Your requirements sound a lot like the document sets feature. You could create a document set per customer and use the shared columns feature. Below is a thread where I shared an example
Alternatively, if you want to keep using folders you can also use the Column default value setting as well.
Below is an example of that
1. The Default value for the Client column is set to Contoso Sports for the CustomerA folder.
2. The Contracts folder inherits this value
@Expiscornovus document set as become somehow an old approach to manage documents with the flat structure and modern UI and more collaboration rather than having a documents repository.
i know that i can set the default values for folders, but users will keep adding new folders, and they find it difficult to set the default values for the folders by themselves + this will require me to grant them additional permissions to manage the libraries which i do not want to provide.
so i find my approach simple and straight forward, users have to only create a new term for the new client and create a folder with the same name as the client.. then the workflow will populate the metadata accordingly. what do you think?
Hi @johnjohnPter,
Good to know you prefer folders instead of doc sets 👍
I would still suggest to look into the column default value setting. It should be possible to automate that setting for each new folder with a flow as well.
@Rhiassuring has shared a nice solution about updating these settings via a Power Automate flow:
@Expiscornovus it is not possible to set the column default value using power automate, i tried this long time ago, and when i set a default value for a new column all the old values got removed. so in other words if we want to set a default value using power automate or SharePoint rest api, we will need to do it for all existing folders.. as when you set this for a single folder this will reset the values for all the other folders.
Hi @johnjohnPter,
I think in the same thread they also tried add new defaults without removing the old ones. But if you have already tried it lets go for your own suggested approach.
I would use the Full Path property and split it on the / character. In that case you could use the 2nd and 3rd item of the returned array.
Below is an example
1. Via a split expression the Client and DocType are retrieved
Client
split(triggerOutputs()?['body/{FullPath}'], '/')[1]
DocType
split(triggerOutputs()?['body/{FullPath}'], '/')[2]
2. Those are used in a couple of HTTP requests to retrieve the term id of the corresponding label
URI Client
_api/v2.1/termStore/groups/@{variables('TermGroupId')}/sets/@{variables('ClientTermSetId')}/terms?$filter=labels/any(a: a/name eq '@{split(triggerOutputs()?['body/{FullPath}'], '/')[1]}')
URI DocType
_api/v2.1/termStore/groups/@{variables('TermGroupId')}/sets/@{variables('DocTypeTermSetId')}/terms?$filter=labels/any(a: a/name eq '@{split(triggerOutputs()?['body/{FullPath}'], '/')[2]}')
I also got a blog about that approach:
https://www.expiscornovus.com/2022/12/29/get-terms-by-label/
3. With concat expressions they are used in an update file properties action (as a custom value)
Client
concat(split(triggerOutputs()?['body/{FullPath}'], '/')[1], '|', outputs('Send_an_HTTP_request_to_SharePoint_-_Client')?['body']['value'][0]['id'])
DocType
concat(split(triggerOutputs()?['body/{FullPath}'], '/')[2], '|', outputs('Send_an_HTTP_request_to_SharePoint_-_DocType')?['body']['value'][0]['id'])
Below is my test result.
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24 17 @Anil_g 7 @ManishSolanki 13 @eetuRobo 5 @David_MA 10 @VishnuReddy1997 5 @SpongYe 9JhonatanOB19932 (tie) @Nived_Nambiar 8 @maltie 2 (tie) @PA-Noob 2 (tie) @LukeMcG 2 (tie) @tgut03 2 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate @Deenuji 12@ManishSolanki 19 @Anil_g 10 @NathanAlvares24 17 @VishnuReddy1997 6 @Expiscornovus 10 @Tjan 5 @Nived_Nambiar 10 @eetuRobo 3 @SudeepGhatakNZ 8 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2 Anil_g2 SharonS2
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages