cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Filtering taxonomy

Hi 

 

I'm stuck and Google has not been my friend in need this time.

 

I want to filter a get item from a sharepoint doc library on a metadata field with values from the taxonomy word set, but trail and error always ends up with error.

 

Isn't it possible to filter on managed metadata?

 

This should work in my book

 

Kategori eq 'Timeregnskaber Tilsyn', "Kategori" being the column name and "Timeregnskaber Tilsyn" being the value. The value is actually "Løn og Kørsel:Timeregnskaber Tilsyn" because the value I use is a sub of another value.

 

Any other work arounds because my flow is taking forever to fiddle through all items in the list.

1 ACCEPTED SOLUTION

Accepted Solutions
v-yamao-msft
Community Support
Community Support

Hi @Anonymous ,

 

Are you using Filter query of SharePoint action Get items?

 

I am afraid that not all the column types are supported in Filter query, such as Choice column, Lookup column.

 

Per my certain test, Managed metadata column is also not supported currently. If you need this feature, please feel free submit your request on Flow Ideas Forum:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

 

Further, a workaround for this issue is adding a Condition. Then use the dynamic content of Managed metadata label to check if it equal to the specific value.

Note: the returned value of Managed metadata column is of type String.

1.PNG

 

Best regards,

Mabel

 

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

5 REPLIES 5
v-yamao-msft
Community Support
Community Support

Hi @Anonymous ,

 

Are you using Filter query of SharePoint action Get items?

 

I am afraid that not all the column types are supported in Filter query, such as Choice column, Lookup column.

 

Per my certain test, Managed metadata column is also not supported currently. If you need this feature, please feel free submit your request on Flow Ideas Forum:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

 

Further, a workaround for this issue is adding a Condition. Then use the dynamic content of Managed metadata label to check if it equal to the specific value.

Note: the returned value of Managed metadata column is of type String.

1.PNG

 

Best regards,

Mabel

 

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Anonymous
Not applicable

Hi

 

Thank you for your response. I've found a work around for my specific case. Hopefully this will be poswsible in the near future.

Found this online and it works, but it filters on all the taxonomy fields on the item.

 

https://itgeneralisten.wordpress.com/2018/10/09/filter-a-sharepoint-list-on-a-managed-metadata-field... 

 

Jaco_Campher_1-1601987090330.png

 

Dear  v-yamao-msft (microsoft.com)

This Filter Condition is not working on my side.

Do i have to filter the ManagedMetadataColumn.Label from the Get Items Lists Value with the string(body('Get_File_Properties')?['ManagedMetadataColumn']?['Label']) ?

nickellis74
Responsive Resident
Responsive Resident

I found this thread after googling how to filter on a Managed Metadata column. It helped push my thinking a bit, but I wanted to share the full solution I built (I am sure not the only solution) for others struggling with this pain!

 

In my scenario I have a managed metadata column [Email Recipient] that just has three names in it. There is then a standard Single Line of Text column [Email] containing email addresses. The flow takes an input [Who gets the email?] of a name and returns the corresponding email address.

 

  1. Standard, unfiltered Get Items on the list (it will say you should add some oData filtering for performance but of course we know that doesn't work)
  2. Filter Array, input is the value of the Get Items action, [Email recipient] is equal to [Who gets the email?]. Being honest, I don't think this does anything in terms of filtering, but it does convert the output into JSON which is what I really needed, and you can't use Filter Array without giving it a filter parameter.
  3. Inside an Apply to Each loop on the Body output of the Filter Array
    1. Compose on Current Item
    2. Parse JSON (see sample below, but you obviously need to generate your own to get the structure right)
    3. Put first of the [Email] outputs (there are others because it also returns the tag creator and other bits) into a variable
  4. Respond to a PowerApp supplying the variable

The full flow looks like this:

Filtering on Metadata.png

It is conceivable that the Compose AND the Parse JSON is overcooking it a bit, but it works and I'm not tempted to fiddle about with it now!

 

{
    "type": "object",
    "properties": {
        "@@odata.etag": {
            "type": "string"
        },
        "ItemInternalId": {
            "type": "string"
        },
        "ID": {
            "type": "integer"
        },
        "Title": {
            "type": "string"
        },
        "Email_x0020_Recipient": {
            "type": "object",
            "properties": {
                "@@odata.type": {
                    "type": "string"
                },
                "TermGuid": {
                    "type": "string"
                },
                "WssId": {
                    "type": "integer"
                },
                "Label": {
                    "type": "string"
                },
                "Path": {},
                "Value": {
                    "type": "string"
                }
            }
        },
        "Email_x0020_Recipient#WssId": {
            "type": "integer"
        },
        "Email": {
            "type": "string"
        },
        "Modified": {
            "type": "string"
        },
        "Created": {
            "type": "string"
        },
        "Author": {
            "type": "object",
            "properties": {
                "@@odata.type": {
                    "type": "string"
                },
                "Claims": {
                    "type": "string"
                },
                "DisplayName": {
                    "type": "string"
                },
                "Email": {
                    "type": "string"
                },
                "Picture": {
                    "type": "string"
                },
                "Department": {},
                "JobTitle": {}
            }
        },
        "Author#Claims": {
            "type": "string"
        },
        "Editor": {
            "type": "object",
            "properties": {
                "@@odata.type": {
                    "type": "string"
                },
                "Claims": {
                    "type": "string"
                },
                "DisplayName": {
                    "type": "string"
                },
                "Email": {
                    "type": "string"
                },
                "Picture": {
                    "type": "string"
                },
                "Department": {},
                "JobTitle": {}
            }
        },
        "Editor#Claims": {
            "type": "string"
        },
        "{Identifier}": {
            "type": "string"
        },
        "{IsFolder}": {
            "type": "boolean"
        },
        "{Thumbnail}": {
            "type": "object",
            "properties": {
                "Large": {},
                "Medium": {},
                "Small": {}
            }
        },
        "{Link}": {
            "type": "string"
        },
        "{Name}": {
            "type": "string"
        },
        "{FilenameWithExtension}": {
            "type": "string"
        },
        "{Path}": {
            "type": "string"
        },
        "{FullPath}": {
            "type": "string"
        },
        "{HasAttachments}": {
            "type": "boolean"
        },
        "{VersionNumber}": {
            "type": "string"
        }
    }
}

 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

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.    

Updates to Transitions in the Power Platform Communities

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

Users online (1,197)