cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
314mp_M0th4
Helper III
Helper III

Filter out empty values from get items sharepoint.

Hello. I'm using getitems to get items from a sharepoint list. In this list is a column that may have empty values. I want to filter out the rows where that column contains empty values. How do I do that? 

 

Thanks!

11 REPLIES 11
Pstork1
Most Valuable Professional
Most Valuable Professional

You can use a filter array to filter out all the rows where that column is null.  Then take those results and use a Parse JSON action to reestablish the dynamic content.  In the following screenshot the column is called Color

image.png



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
ScottShearer
Most Valuable Professional
Most Valuable Professional

@314mp_M0th4 

In addition to the suggestion from @Pstork1 you might want to use a filter query like this:

MyColumn ne null

 

Enter null as plain text and not as a formula.

Note that you must use the internal name of your SharePoint column which may/may not be the same as the display name.

Here is this solution from another post

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Scott

I get the following error : Unable to process template language expressions in action 'Parse_JSON' inputs at line '0' and column '0': 'The template language expression 'outputs('Filter_array')['body/value']' cannot be evaluated because property 'body/value' doesn't exist, available properties are 'body'. Please see https://aka.ms/logicexpressions for usage details.'.

Pstork1
Most Valuable Professional
Most Valuable Professional

The output of the filter array is body, not value. The output you use from Get Items for input to the filter array is body/value



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.


@Pstork1 wrote:

The output of the filter array is body, not value. The output you use from Get Items for input to the filter array is body/value


Hi @Pstork1 ,

 

How do resolve this? I'm trying to do the same thing, but also get this error. Is the JSON schema wrong then? How do I get body/value?

Yes I put the body output in first but after test running the flow it changes to body/value.


@314mp_M0th4 wrote:

Yes I put the body output in first but after test running the flow it changes to body/value.


I have put the output of "Filter array" as input for the Parse JSON and this "seems" to work, but I get "Body" in all names of the properties (see screenshot). This doesn't seem right and the "Append to array" action doesn't work. The array is not filled with the values of the parsed JSON.

 

I also don't get the right options at the Dynamic content for the "For each" action (see 2nd screenshot.

 

JOAS_Niels_0-1702469223929.png

 

JOAS_Niels_1-1702469241528.png

 

I'm using this as schema:

{
    "type": "object",
    "properties": {
        "@@odata.etag": {
            "type": "string"
        },
        "ItemInternalId": {
            "type": "string"
        },
        "ID": {
            "type": "integer"
        },
        "Title": {
            "type": "string"
        },
        "Volgorde": {
            "type": "integer"
        },
        "OmschrijvingURL": {
            "type": "string"
        },
        "URLdocument": {
            "type": "string"
        },
        "Linkdocument": {
            "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"
        }
    }
}
Pstork1
Most Valuable Professional
Most Valuable Professional

The schema should be showing an array of objects. Your schema just shows an object.  If you look at the screenshot I posted you can see that it is an array inside an object.  Your schema doesn't include an array.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.


@Pstork1 wrote:

The schema should be showing an array of objects. Your schema just shows an object.  If you look at the screenshot I posted you can see that it is an array inside an object.  Your schema doesn't include an array.


Hi @Pstork1 ,

 

I have changed the schema and included the array, but I now get this error:

 

"The execution of template action 'For_each_1' failed: the result of the evaluation of 'foreach' expression '@body('Parse_JSON')?['value']' is of type 'Null'. The result must be a valid array."

 

I still get only a body as output from the parse JSON action. See here:

 

JOAS_Niels_0-1702545185152.png

 

This is my schema:

 

Spoiler
{
    "type": "object",
    "properties": {
		"value": {
			"type": "array",
			"items": {
				"type": "object",
				"properties": {
					"@@odata.etag": {
						"type": "string"
					},
					"ItemInternalId": {
						"type": "string"
					},
					"ID": {
						"type": "integer"
					},
					"Title": {
						"type": "string"
					},
					"Volgorde": {
						"type": "integer"
					},
					"OmschrijvingURL": {
						"type": "string"
					},
					"URLdocument": {
						"type": "string"
					},
					"Linkdocument": {
						"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"
					}
				}
			}
		}
	}
}

Can you see what I'm doing wrong?

 

Pstork1
Most Valuable Professional
Most Valuable Professional

I would verify that the Filter array is returning an array of things first. Your current error would lead me to believe that the filter array is returning an empty array. If that is the case your problem is in the filter, not the parse JSON.  Please post this as a new question.  You'll get more responses and others will be able to find the answer more easily later.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.


@Pstork1 wrote:

I would verify that the Filter array is returning an array of things first. Your current error would lead me to believe that the filter array is returning an empty array. If that is the case your problem is in the filter, not the parse JSON.  Please post this as a new question.  You'll get more responses and others will be able to find the answer more easily later.


The array is not empty. I created a new post, although I'm doing the exact same thing as in this post. Thanks for the help so far.

 

https://powerusers.microsoft.com/t5/Building-Flows/Filter-empty-values-from-get-items-to-array/m-p/2...

Helpful resources

Announcements

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (3,641)