A field control for model-driven apps that shows a Whole Number column without
a thousands separator. Made for years: a column that holds 2024 should read
2024, not 2,024. No configuration.
The same column, Founded = 2024, on one form with the stock control and with Plain Number:
Users can type into it. Whatever they type, digits are kept and everything else
is dropped, so 1,999, 1 999 and 1999 all commit as 1999. After typing 1999
into Plain Number and pressing Enter, the stock control on the same form follows:
In the PCF test harness, mid-typing and after commit:
| While typing | After Enter or leaving the field |
|---|---|
![]() |
![]() |
Escape restores the last saved value. Empty commits a blank. Text with no digits at all is ignored and the previous value comes back.
Everything else about the field is the stock field. The same fill, width,
height, text colour and focus underline; --- when it is empty; a locked field
that keeps its fill and full-strength text and can still be copied from,
because it is readonly rather than disabled, exactly as the stock one is. Stock on the
left, Plain Number on the right, in the states an e2e run measures them both in
(node e2e/run-states.mjs):
Import the solution zip from a release, vendor the two files per control into your own solution (see VENDORING.md), or build and push from source:
cd PlainNumber
npm install
pac auth create --environment https://<your-org>.crm.dynamics.com
pac pcf push --publisher-prefix <your-prefix>After the push the control appears in the environment as
<prefix>_KK.PlainNumber.
- Open the form in the form designer (make.powerapps.com, Tables, your table, Forms).
- Select the Whole Number column on the form.
- In the properties pane on the right, expand Components and choose Get more components.
- Pick Plain Number and add it. There is nothing to configure.
- Save and publish the form.
The column keeps its type, its min and max, and its business rules. Only the rendering changes.
A view cannot carry a field control on a column, so the same package ships a second control, Plain Number Grid, a customizer for the Power Apps grid control. It has no settings and makes no network calls. Every whole-number column of the table it is assigned to renders without a thousands separator.
To turn it on for a table:
- Open the classic solution explorer (make.powerapps.com, Solutions, your solution, the table, then Switch to classic if needed).
- On the table, open the Controls tab.
- Add Control, choose Power Apps grid control, and select it for Web, Phone and Tablet.
- In its properties, set Customizer control to
<prefix>_KK.PlainNumberGrid. - Save and publish.
Every view of that table now shows all its whole-number columns without a separator. Decimal, currency and other types keep the user's format. Sorting and filtering are untouched; only the rendered text changes, and it sits exactly where the stock text sat.
A subgrid on a form does not pick the customizer up from the table. Set it on
the subgrid too: open the form, select the subgrid, add the Power Apps grid
control to it, and set that control's Customizer control to the same
<prefix>_KK.PlainNumberGrid. Save and publish. A subgrid left on the legacy
read-only or editable grid ignores customizers entirely.
Whatever you change here, the client caches the published control config: check it in a fresh InPrivate window rather than a reload, or you will be looking at the old grid.
Only one customizer can be assigned per table. If the table already has one, the two would have to be merged; see notes.md.
cd PlainNumber # the form control; same for PlainNumberGrid
npm install
npm run build # out/controls/PlainNumber
npm start # PCF test harness in a browser
pac pcf push --publisher-prefix <your-prefix>e2e/ holds Playwright scripts that host the harness headlessly and take the
screenshots above, plus a script that builds a fixture form in a Dataverse
environment and checks that typing into Plain Number updates the record.





