How to Utilize the PowerApps Remove Function for Field Deletion

How to Utilize the PowerApps Remove Function for Field Deletion

For anyone working with data in PowerApps, understanding the nuances of data manipulation is key. One such essential operation is removing fields from a record. In this guide, we’ll walk you through the steps to effectively use the powerapps remove function for deleting fields from individual records.

Why Remove Fields from a Record?

When dealing with data-driven applications, specific situations demand the removal of certain fields. For instance, records might contain temporary working fields that are only required during the app’s operation. Such fields could be temporary sequence numbers or ones meant to enhance the app’s presentation.

However, when it comes to saving these records to a data source, these additional fields may become unnecessary. At this juncture, it’s optimal to get rid of these fields, especially before passing the record to functions like the Patch function in PowerApps.

Dropping Columns vs. Removing Fields

While PowerApps provides a handy DropColumns function to remove columns from tables, the same isn’t available for individual records. But worry not, as we’ve got a workaround for you.

Step-by-Step Guide to Remove Fields from a Record

For illustrative purposes, consider a record defined and stored in a variable named varRecord:

Set(varRecord, { Forename:"Tim", Surname:"Leung", Address:"10 Kings Road", City:"London", UpdateDatabase:true, SequenceNo:5 } )

The above record contains two specific fields – UpdateDatabase and SequenceNo. To exclude these fields and retrieve the modified record, utilize the given syntax:

First( DropColumns(Table(varRecord), "UpdateDatabase", "SequenceNo" ) )

Now, to patch this modified record to a data source, here’s how you can structure the syntax:

Patch(CustomerList, Defaults(CustomerList), First( DropColumns(Table(varRecord), "UpdateDatabase", "SequenceNo" ) )


In PowerApps, while there isn’t a direct “DeleteFields” function to cater to individual records, there’s always a way around. By converting the record into a table and then dropping columns, you can achieve the desired outcome. It’s all about understanding the tools at hand and using them creatively.

If you ever find yourself stuck or in need of technical assistance related to this topic or others, don’t hesitate to contact us. We’re here to provide the expert guidance you need, and yes, our expert solutions are chargeable, ensuring you receive premium support every time.

About The Author