Professional & Enterprise

Turn ordinary SharePoint fields into purpose-built inputs.

A toolkit of input enhancements that make forms faster, more accurate, and field-ready — from handwritten signatures to barcode scanning, GPS, star ratings, and dropdowns powered by live data.

The toolkit

Signature capture & co-signing

Draw a signature with mouse or finger; configure pen color, background, and line width. Co-signing mode collects multiple named signatures, each with a timestamp, with an optional maximum.

Barcode / QR scanner

Scan straight into a text field with the device camera. Supports QR, EAN, Code 128/39/93, UPC, Data Matrix, Aztec, PDF417, and more — pick which formats to accept.

GPS coordinates

Capture latitude and longitude into a field with one tap — ideal for inspections and field work.

Star rating

Replace a Number field with a clickable star control (1–10 stars); stores a normal integer.

Pattern validation

Enforce input formats — Email, URL, Number, Letters, Alphanumeric, or a custom regex.

Date range limits

Restrict which dates a user can pick on Date / Date & Time fields — a fixed date, a value relative to today or another field (e.g. “within 30 days of Start date”), or a formula. Available as a field option, a rule action, and from Custom JS.

SharePoint or REST data sources

Drive Dropdown and Autocomplete fields from a SharePoint list or any REST endpoint — with token-based dynamic URLs, auth, response-path mapping, and cascading field updates.

  1. Every one of these is a toggle, not code

    Enhancements live in the field’s own settings, beside the label and description you already set — nothing to install, no custom field type to register, and the column stays an ordinary SharePoint column. Turn Pattern validation on, pick a format, and write the message people should see when input doesn’t match. That message is what appears under the field, word for word.

    Pattern validation settings: a Yes toggle, a Pattern type dropdown set to Email, and a Validation message box reading "Please provide a valid email address", with a note that validation is skipped for empty values. The field on the form with "nestor" typed in: the input is outlined in red and the message "Please provide a valid email address" sits underneath.
  2. Limits that follow the form, not a fixed calendar

    Date fields take a minimum and a maximum, and each is more than a hard-coded day: Fixed date pins a calendar date, Relative counts from today or from another field on the form, and Formula computes the boundary outright. Here the minimum is today + 14 days — so on 1 August the picker grays out everything before the 15th, and the earlier months with it. No rule to write, and nothing for the user to get wrong.

    Restrict date range settings: Minimum date set to Relative, then Today, then 14 Days; Maximum date left as None. The DueDate picker open on August 2026 with the 1st marked as today: the 2nd to the 14th are grayed out and unselectable, the 15th onwards are active, and in the month panel January through July are grayed out.
  3. A dropdown fed by any REST endpoint

    Point the field at a URL, say where the array sits in the response and which property to display, and the options come from there. Tokens like [[fieldValue:FieldName]] make the URL dynamic, so one field can filter on another. Bearer-token and API-key-header authentication are built in for endpoints that need them.

    Dropdown list settings with REST endpoint selected as the data source: an Endpoint URL box, Authentication options of None, Bearer token and API key header, a path-to-array box, a Display property name set to "name", and placeholder text reading "-- select user --". The dropdown open on the form, showing the configured placeholder "-- select user --" and a list of names fetched live from the endpoint.
  4. …or an autocomplete fed by a SharePoint list

    Same idea, different source: name the list and the column to search, and the field suggests as the user types. Add extra search columns, a REST filter to narrow the source, a sort, and a cap on how many suggestions appear before any search term is entered. Selecting an item can populate other fields at the same time, so one pick fills in a whole row.

    Autocomplete search box settings with SharePoint list selected: List set to Products, the search field set to Title, placeholder text "-- select product --", plus boxes for additional search fields, a REST filter, sorting, setting other field values, and a suggested-items length of 25. The autocomplete field focused on the form, showing a Suggested items panel listing products from the source list — 27-inch 4K Monitor, Ergonomic Office Chair, Label Printer, Laptop, Noise-canceling Headset, Standing Desk and USB-C Docking Station.
  5. Coordinates without asking anyone to read a map

    Turn GPS capture on and choose how the pair is written — {lat} and {long} are placeholders, so you control the separator and the order. With Auto-fill if empty on, the field populates itself the moment the form opens on a blank value, which is what you want for an inspection logged on site. The result is plain text in an ordinary column.

    GPS coordinates settings: a Yes toggle, a Coordinate format box containing the lat and long placeholders, and Auto-fill if empty set to Yes. A GPSCoordinates field on the form holding a latitude and longitude pair, with a capture button to its right.
  6. Scanning beats typing a serial number

    The scanner reads thirteen symbologies — QR, EAN-13 and EAN-8, Code 128, 39 and 93, UPC-A and UPC-E, Data Matrix, Aztec, PDF417, Codabar and ITF. Leave Accepted formats empty and it takes any of them; tick a subset and it ignores everything else, which is worth doing when a label carries more than one code and you only want the right one.

    Barcode / QR scanner settings: a Yes toggle and an empty Accepted formats dropdown, noted as accepting all supported formats when left blank, with a tip to use a multi-line field for QR codes containing long text. The Accepted formats list open, with a checkbox for each symbology: QR Code, EAN-13, EAN-8, Code 128, Code 39, Code 93, UPC-A, UPC-E, Data Matrix, Aztec, PDF417, Codabar and ITF.

    On the form it is simply a camera button beside a text box. Tap it, point the phone at the label, and the value drops in.

    A form field labeled Barcode_QR: a normal text input reading "Enter value here" with a small camera icon button to its right.
  7. A rating people can actually hit with a thumb

    Point a Number column at the star control, set how many stars it should offer — anything from one to ten — and the field stops being a box you type a digit into. What gets saved is still an ordinary integer, so sorting, filtering, grouping and formulas all keep working on it.

    Star rating settings: a Yes toggle and a Number of stars box set to 5, noted as one to ten with the value saved as an integer. A Rating field on the form showing four filled amber stars and one empty star.
  8. Signatures, drawn on the device itself

    Set the pen color, background and line width, then decide how the field behaves: whether a signer must name themselves, whether more than one signature is allowed, and how many at most. With Allow multiple signatures on and a maximum of two, the field collects a pair and then stops.

    On the form it starts as an empty panel with a single button. Add signature opens a canvas — sign with a finger, a stylus or the mouse, name the signer, and save. Each signature is stored with its name and the moment it was given, listed alongside the drawing and removable one at a time. That is what makes co-signing hold up: not one image, but an ordered, attributed, timestamped set.

    Signature capture settings: a Yes toggle, Pen color #000000, Background color #ffffff, Line width 2 pixels, Require signer name set to Yes, Allow multiple signatures set to Yes, and Max signatures set to 2. An empty Signature field on a form: a dashed panel reading "No signature" with an Add signature button below it. The Draw signature dialog: a canvas holding a handwritten signature reading Nestor Wilke, a required Signer name box filled in with the same name, and Clear, Cancel and Save buttons. The completed Signature field holding two signatures, each with the signer’s name, the date and time it was given, and its own Remove button.

Every enhancement on this page attaches to a real SharePoint column and writes a normal value back to it — nothing here needs a custom field type. Looking for the Power BI tile? That’s a standalone form element rather than a field enhancement — see Form Builder & Rules.

Worked example

A field inspection form: scan an asset’s barcode into the asset field, capture the site GPS coordinates, rate condition with stars, and collect an inspector signature — all on a phone, all into standard SharePoint columns. Print it and the record reads properly too: Print to PDF renders star ratings as stars and signatures as the signature image, not the raw values stored behind them.

Signature & co-signing documentation →

REST data source documentation →

Build field-ready forms — free for 30 days.

Full functionality, no credit card.