How do I patch text to a number field in Power Apps?

Wrap the text in Value(), for example {'Asset Tag': Value(txtAssetTag.Text)}. Without it, Patch shows "does not match the expected type 'Number'. Found type 'Text'."

Why does Patch say expected type 'Number' but found type 'Text'?

A text input's .Text is always Text, even with digits. Convert it with Value(); the Value function reference explains the language rules.

How do I patch a Dataverse currency column?

The same way: Patch takes a Number, so use Value() on text input. Dataverse adds Currency, Exchange Rate and _Base columns for you, as described in Column data types in Dataverse .

Can I patch a decimal into a Dataverse whole number column?

No. 12.7 failed with "Cannot convert the literal '12.7' to the expected type 'Edm.Int32'." Round it first with Round(Value(txtAssetTag.Text), 0) or use a Decimal column.

How do I add 1 to a Dataverse number column with Patch?

Read the current value with LookUp and add 1 inside the change record. Our Printer Setup row went from 10045990 to 10045991.

Patch Dataverse Number Field in Power Apps (Text to Number)

Our service desk tags every device with a numeric Asset Tag, and techs wanted to type it into a canvas app instead of the Dataverse grid. The catch: a text box gives you text, and the column wants a number.

In this tutorial, we’ll patch a Dataverse number field in Power Apps: update a row, add a new one, convert text to a number with Value(), and stop bad input before it reaches the server.

Here’s what we’re building: a screen whose buttons save 10045990 to a Whole Number column, shown in a gallery of the newest rows.

Power Apps preview gallery showing Scanner Setup and Printer Setup both saved with Asset Tag 10045990

Table of Contents:

Before You Start

You need a Power Apps license that covers Dataverse and a role that can edit the table. Dataverse stores data in tables made of rows and columns; new to it? Start with what Microsoft Dataverse is.

I used the Service Request table (plural name Service Requests) in my Power Platform developer environment. These are the columns we touch:

Column	Type	Notes
Subject	Text (primary column)	We find rows by it, e.g. Printer Setup
Asset Tag	Whole Number, format None	Logical name cr85a_assettag; range 0 to 2147483647
Customer	Lookup to Customers	A server rule requires it on new rows

I created Asset Tag for our post on how to remove commas from a Dataverse number field; that’s also where the grid’s 10,045,872-style commas come from.

Step 1: Build the Screen

Build a bare app in a few clicks (no shots needed here):

On make.powerapps.com, select Create > Start with design > Blank canvas app, and pick Tablet.
Select Data > Add data, search Service Requests, and add the Dataverse table. Add Customers too.
Insert a classic Text input, rename it txtAssetTag, and set its Default to 10045990.
Insert a vertical gallery with Items set to the formula below, and show Subject, Asset Tag and Modified On.

FirstN(Sort('Service Requests', 'Modified On', Descending), 8)

To set a property, select the control, pick the property in the dropdown left of the formula bar (fx), and type. Save often with Ctrl+S.

Checkpoint: the gallery lists your eight newest Service Requests.

Step 2: See the Text to Number Type Error

Let’s make the mistake everyone makes first. Add a button, select OnSelect, and pass the text box straight to the column:

Patch('Service Requests',
    LookUp('Service Requests', Subject = "Printer Setup"),
    {'Asset Tag': txtAssetTag.Text})

Studio flags it right away with a red X on the button and a squiggle under txtAssetTag.Text. Hover it and you get:

The type of this argument 'cr85a_assettag' does not match the expected type 'Number'. Found type 'Text'.