version: "1.0" author: Klemens Stelk

⚠️ MANDATORY: Read this skill BEFORE using any MCP tools to interact with CRM/Dataverse records. Do not call get-record, query-records, create-record, update-record, or delete-record until you've reviewed this guidance.

Dataverse CRUD Operations

Field Type Reference

Critical Gotchas

Lookup Fields: Logical Names Work

Both logical names (lowercase) and SchemaNames work—use field names directly from get-record output:

{ "si_titleid@odata.bind": "/si_titles(guid)" }

No need to call get-lookup-target for setting lookups.

Polymorphic Lookups Need Entity Suffix

When a lookup can point to multiple entity types:

{ "si_customerid_contact@odata.bind": "/contacts(guid)" }
{ "si_customerid_account@odata.bind": "/accounts(guid)" }

Read-Only Fields (Never Set These)

• •createdon, modifiedon, createdby, modifiedby
• •versionnumber, @odata.etag
• •Calculated/rollup fields, fullname on Contact
• •ownerid, owninguser, owningbusinessunit
• •Fields ending in _base (base currency)
• •Fields starting with _ and ending with _value (use @odata.bind instead)

Option Set Values Are Integers

Find values from existing records or metadata—not labels.

Efficient Workflows

Clone a Record

1. •Extract record ID from URL
2. •get-record to retrieve original
3. •create-record with field values (exclude read-only, modify as requested)
4. •If related records needed, create and link via lookups

Avoid: get-entity-metadata, get-lookup-target (not needed)

Create New Record with Specific Values

1. •Identify required lookups (e.g., "title Mr." = need si_title record)
2. •query-records on reference table to find record GUID
3. •create-record with fieldname@odata.bind syntax

Update Existing Record

1. •Extract record ID from URL
2. •update-record with changed fields only (partial update)

Link Records via Lookup

Update the entity with the lookup field:

{ "si_emailid@odata.bind": "/si_communicationchannels(email-guid)" }

Common Patterns

Finding Reference Data

// 1. Query reference table
query-records: si_titles, filter: "contains(si_name, 'Mr')"
// 2. Use GUID in create
{ "si_titleid@odata.bind": "/si_titles(<guid>)" }

Option Set Values

// Get existing record with correct value set, note the integer
get-record: existing contact with "Events" selected
// Use integer in create
{ "sic_joiningreasonsource": 157430003 }

Error Solutions

Pre-Create/Update Checklist

• • Excluded read-only fields
• • Integer values for option sets (not labels)
• • Entity suffix for polymorphic lookups (_contact, _account)
• • Boolean fields use true/false (not 0/1)
• • DateTime in ISO 8601 format
• • Lookups use @odata.bind syntax