How to Remove Commas From a Dataverse Number Field (Model-Driven and Canvas Apps)

You store an asset tag or an ID in a Dataverse Whole Number column, and the grid shows 10,045,872 instead of 10045872. The commas aren’t in your data; they’re a display format, so you fix them where the number is shown.

In this tutorial, we’ll remove commas from Dataverse number field values in a model-driven app, in a canvas app, and for every user with a formula column.

Quick answer: in a model-driven app, open gear > Personal Settings > Formats > Customize and set Digit group to 123456789.00. In a canvas app, format the value with Text():

Text(ThisItem.'Asset Tag', "0")

That returns 10045872 as plain text, with no thousands separator.

Why Does Dataverse Show Commas in a Number Column?

Dataverse stores a Whole Number as a plain integer. The comma comes from the format of the person viewing it, which is English (United States) for most US users. If Dataverse is new to you, start with what Microsoft Dataverse is.

We added a Whole Number column named Asset Tag (Format None) to our Service Request table and typed values such as 10045872. Here’s what the table data grid in make.powerapps.com showed:

Every value picked up a comma after the millions and thousands digits. The stored value is still 10045872, which is why a canvas app shows it differently.

Remove Commas in a Model-Driven App (Personal Settings)

Model-driven apps and the make.powerapps.com table grid both read your personal number format. Open any model-driven app, such as one you built with our guide to model-driven apps in Power Apps, and select the gear icon, then Personal Settings:

The Personal settings dialog opens. Select the Formats tab. The Format preview shows Number as 123,456,789.00 for English (United States):

Select Customize, stay on the Number section, and open the Digit group dropdown. It lists four patterns:

Pick 123456789.00, the only pattern with no grouping, and select Save:

Back on the Formats tab, the preview now reads Number 123456789.00 and Currency $123456789.00. Select Save to keep it:

Then refresh the table grid. Microsoft notes you may need to refresh twice. Our Asset Tag column now shows 10045872:

Does This Change the Number Format for Other Users?

No. It’s a per-user setting, so every other user still sees 10,045,872 until they change their own Formats tab. It also applies to every number and currency column you see, not just one field.

Why the Blank Digit Grouping Symbol Doesn’t Work

Many older guides, including an earlier version of this post, say to set Digit grouping symbol to the blank option. That option isn’t empty; it’s a space character.

When we picked it, the preview changed to 123 456 789.00. The digits were still grouped, just with spaces instead of commas. Leave the symbol as a comma and change Digit group instead.

Remove Commas From a Dataverse Number in a Canvas App

Canvas apps don’t use your personal format. A label set to ThisItem.’Asset Tag’ already showed 10045872, with no commas. If you’re pulling rows into a gallery, see how to get data from Dataverse in Power Apps.

Commas show up in a canvas app only when a format string adds them. Here’s the label formula for each case:

// plain digits: 10045872
Text(ThisItem.'Asset Tag', "0")

// thousands separator: 10,045,872
Text(ThisItem.'Asset Tag', "#,##0")

Our NumberScreen shows the formula in the formula bar and the plain values in the gallery:

The comma in a format string adds grouping only when it sits between # or 0 placeholders. So “0” or “#” gives plain digits, and Text() with no format also skips separators.

For money values you’ll usually want the opposite. Our Power Apps currency format guide covers “$#,##0.00” and friends.

Show the Number Without Commas for Every User

If everyone must see the value without commas, add a Dataverse formula column that returns text. Our Dataverse formula column guide walks through creating one. Use this formula:

Text(ThisRecord.'Asset Tag', "0")

Microsoft documents a few rules here. Text() in a formula column needs a format argument, works only with whole numbers, and doesn’t accept the “.” or “,” locale tokens. A plain “0” or “#” format fits those rules.

The result is a text column, so it sorts as text and you can’t change its type later. Keep the original number column for math and filters, and show the formula column in views and forms.

Should Phone Numbers or IDs Be a Number Column?

Usually not. If you’ll never add, average or compare the value, it’s an identifier, not a number. Phone numbers, ZIP codes and employee IDs belong in a text column.

Dataverse has a Phone format for Single Line of Text, and a text column keeps leading zeros that a Whole Number drops. For a country code prefix in a form, see auto-populating the country code and phone number in Power Apps.

Already have data in a number column? Add a new text column and copy the values over, then switch your forms. Writing numbers from an app works the way patching a Dataverse number field shows.

Commas Still Showing? Common Problems

• The grid didn’t change. Refresh the page, sometimes twice, after you save Personal Settings.
• You see spaces instead of commas. You changed Digit grouping symbol to the blank (space) option; set Digit group to 123456789.00 instead.
• A coworker still sees commas. The setting is per user; they change their own, or you add a text formula column.
• Commas in a canvas label. The format string has a comma between placeholders, such as “#,##0”; use “0”.

SharePoint has its own version of this problem; see a SharePoint number column without commas. In a flow, formatting a thousand separator in Power Automate covers the reverse case.

If you’re tidying up a Dataverse table, these are worth a look next:

• Power Apps Add Data to Dataverse Table
• Delete All Records From Dataverse Table [With Examples]
• Create a Dataverse Table from Excel or CSV in Power Apps
• Power Apps Dataverse Yes/No Field [With Examples]

Frequently Asked Questions