Create records in a Microsoft Dataverse elastic table via the Web API
domain: learn.microsoft.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Choose an elastic table for high-throughput, bursty, semi-structured workloads rather than scenarios needing relational joins or cross-table transactions.
When creating a record, optionally set the partitionid column; if omitted, Dataverse defaults it to the primary key value.
Remember uniqueness in an elastic table is the combination of primary key plus partitionid, not the primary key alone.
Keep partition values high-cardinality, under 1,024 bytes, and free of the characters / < > * % & : \ ? +, since each logical partition caps at 20 GB.
Do not plan to change partitionid after it's set — it cannot be modified once assigned.
Known gotchas
Deep insert (creating related entities in one nested request) is unsupported on elastic tables — Dataverse returns an explicit error that each entity must be created individually.
$batch changesets and ExecuteTransactionRequest against elastic tables currently "succeed but aren't atomic," so don't rely on them for multi-record rollback.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?