Give Dataverse records numbers and names that carry useful context. Stamp is planned to configure formatted sequences, build readable text patterns and bring existing records into the same approach.
Planned · Collection launch target: January 2027
Give a sequence the structure your team needs.
Stamp is planned to combine a counter with prefixes, padding, dates, fiscal periods and record values. Scope a sequence by parent or selected values, reset it by period, and assign a number when a record is created or first meets a condition.
Planned · intended first-preview scope
A number format with its scope in view.Planned view of format segments, counter scope, reset period and a read-only example.Screenshot placeholder
Reserved for an approved product capture. No demonstration is available here yet.
Make record names useful at a glance.
Build a primary name or another text value from selected parts, with separators, formatting and missing-value rules. The intended first preview keeps patterns based on the record’s own columns in sync. Background renaming after a related record changes belongs to later scope.
Planned · own-column patterns first
The parts behind a readable name.Planned view of a name pattern and its output when an optional part is empty.Screenshot placeholder
Reserved for an approved product capture. No demonstration is available here yet.
Bring existing records into the same pattern.
Preview a scoped backfill or name rebuild before starting a job, then review its progress and failures. Previews are designed to read without consuming numbers. Renumbering, migration from native autonumber columns and conditional undo are later capabilities.
Planned · first-preview jobs exclude undo
Where could this help your team?
Starting points for a fit discussion. These are use-case ideas to evaluate against the supported scope, not packaged industry solutions.
A sequence for each parent
Explore numbering related tasks within a fictional project, so the identifier reflects both the parent and the task’s place in its sequence.
Names people can recognize
Plan a readable name from a record’s own number, title and date, with empty parts omitted rather than leaving repeated separators.
A consistent starting point
Evaluate a previewed backfill for records missing a number, or rebuild existing names after agreeing on a pattern. Normal business logic still runs during job updates.
Planned scope
Formatted number sequences with prefixes, padding, date and fiscal parts
Counters scoped by parent or column values, with calendar or fiscal resets
Assignment on creation or when a condition first becomes true, with assigned numbers protected
Name patterns built from the record’s own values in the intended first preview
Read-only previews, backfill numbers and rebuild names on existing records
Later scope: related-change rename jobs, renumbering, autonumber migration and conditional undo
Planning handoff only. A first preview is intended after Blueprint. January 2027 is the collection target, not a confirmed availability date for Stamp. Pricing and collection inclusion remain to be confirmed.
Plan around the boundaries.
Stamp is at the planning stage. Its design allocates numbers within the save transaction, but concurrency and rollback behavior still need verification. Deletions and administrator counter changes can leave gaps; this is not an accounting-compliance guarantee. Administrators supply ordinary text columns. Formats, patterns and jobs use the system service, so review which information becomes visible in names and lookups. Availability, pricing and collection inclusion are unconfirmed.
Configurable record identity within Dataverse. Evaluate whether native autonumber already meets your needs; Stamp’s planned scope adds conditional assignment, scoped counters and maintained name patterns.
From a rule to a recognizable record.A planned route through number formatting, name patterns and a reviewed backfill.Animation placeholder
Reserved for an approved product capture. No demonstration is available here yet.
Plan your rollout with us. This module is not on sale yet. We’ll confirm supported features, requirements and availability before purchase. Core is included; Microsoft licenses and implementation services are separate.