Microsoft Dynamics 365

Returns the current authenticated user context from Dataverse WhoAmI: userId, businessUnitId, organizationId, organizationName, and environmentUrl. Use this to verify authentication is working, retrieve the current user context, or obtain IDs needed for subsequent operations. WHEN TO USE: Verifying…

{
  "tool": "dataverse_whoami",
  "parameters": {}
}

Lists all Dataverse tables. By default returns ONLY custom (non-system) tables. Set includeSystemTables=true to include all ~1700+ system tables. WHEN TO USE: Discovering which tables exist in the environment. BEST PRACTICES: Start without includeSystemTables to focus on custom tables; use dataverse…

Puo’ usare: includeSystemTables

{
  "tool": "dataverse_list_tables",
  "parameters": {
    "includeSystemTables": "<boolean>"
  }
}

Returns full schema metadata for a Dataverse table: all attribute (column) logical names, display names, data types, required levels, and lookup target entities. Use this before writing queries or creating/updating records to confirm correct field names and types. Set includeAttributes=false if you…

Gli serve: logicalNamestring

Puo’ usare: includeAttributes

{
  "tool": "dataverse_get_table_metadata",
  "parameters": {
    "logicalName": "<string>"
  }
}

Returns all relationship definitions (1:N, N:1, N:N) for a Dataverse table, including relationship schema names, referenced/referencing entity names, and lookup attribute names. Use to determine the correct relationshipName for dataverse_associate/dataverse_disassociate, or to map lookup fields befo…

Gli serve: logicalNamestring

Puo’ usare: relationshipType

{
  "tool": "dataverse_get_relationships",
  "parameters": {
    "logicalName": "<string>"
  }
}

Lists all global (shared) option sets defined in the Dataverse environment, returning their names and metadata IDs. Use this to discover available option sets before calling dataverse_get_option_set to retrieve their values. Prefer this over dataverse_get_table_metadata when you need to find option…

{
  "tool": "dataverse_list_global_option_sets",
  "parameters": {}
}

Returns all option labels and their integer values for a named global option set. Use this to look up the numeric code for a picklist value before filtering records (e.g., statecode or statuscode equivalents), or to populate dropdowns with correct option values. WHEN TO USE: Looking up numeric codes…

Gli serve: namestring

{
  "tool": "dataverse_get_option_set",
  "parameters": {
    "name": "<string>"
  }
}

Returns all alternate key definitions for a Dataverse table. Useful before using dataverse_upsert to know which fields serve as alternate keys, their index status (Active/InProgress/Failed), and whether they are customizable. WHEN TO USE: Before using dataverse_upsert to verify which fields serve as…

Gli serve: tableNamestring

{
  "tool": "dataverse_get_entity_key",
  "parameters": {
    "tableName": "<string>"
  }
}

Returns all option labels and integer values for a table-specific attribute (Picklist, MultiSelectPicklist, Status, or State field). Use to look up the numeric codes for a column's choices before filtering or updating records. WHEN TO USE: Looking up option values for a specific table's picklist, mu…

Gli serve: entityLogicalNamestring attributeLogicalNamestring

{
  "tool": "dataverse_get_attribute_option_set",
  "parameters": {
    "entityLogicalName": "<string>",
    "attributeLogicalName": "<string>"
  }
}

Resolves entity names bidirectionally: input a logicalName (e.g. 'account') or entitySetName (e.g. 'accounts') and get both representations plus metadata. Essential for avoiding 404/0x80060888 errors caused by using logicalName in OData URLs (which require entitySetName). WHEN TO USE: Any time you'r…

Gli serve: namestring

{
  "tool": "dataverse_resolve_entity_name",
  "parameters": {
    "name": "<string>"
  }
}

Updates configuration flags on an existing Dataverse entity definition — enables or disables Notes (HasNotes), Change Tracking, and Audit. Requires System Customizer or System Administrator privileges. WHEN TO USE: Enabling notes/attachments support, change tracking, or audit on a table. BEST PRACTI…

Gli serve: entityLogicalNamestring confirmboolean

Puo’ usare: hasNotes changeTrackingEnabled isAuditEnabled autoPublish

{
  "tool": "dataverse_update_entity",
  "parameters": {
    "entityLogicalName": "<string>",
    "confirm": "<boolean>"
  }
}

Queries a Dataverse table using OData ($filter, $select, $orderby, $top, $expand, $count). Use for simple to moderate reads on a single table or with shallow $expand for related fields. Always specify $select to minimize payload. For complex aggregations (count, sum, avg), multi-entity joins, many-t…

Gli serve: entitySetNamestring

Puo’ usare: select filter orderby top expand count apply formattedValues

{
  "tool": "dataverse_query",
  "parameters": {
    "entitySetName": "<string>"
  }
}

Executes a FetchXML query against Dataverse — use for complex scenarios requiring aggregations (count, sum, avg, min, max with grouping), linked-entity joins across multiple tables, many-to-many relationship traversal, or advanced filtering not expressible in OData. Returns a typed array of records.…

Gli serve: fetchXmlstring

Puo’ usare: entitySetName fetchAll formattedValues

{
  "tool": "dataverse_execute_fetchxml",
  "parameters": {
    "fetchXml": "<string>"
  }
}

Retrieves ALL records matching a query by automatically following OData nextLink pages. Use instead of dataverse_query when you need more than 5000 records or all records in a table. Returns totalRetrieved count. Set maxTotal to cap retrieval (default 5000, max 50000) to avoid overwhelming the conte…

Gli serve: entitySetNamestring

Puo’ usare: select filter orderby expand maxTotal formattedValues

{
  "tool": "dataverse_retrieve_multiple_with_paging",
  "parameters": {
    "entitySetName": "<string>"
  }
}

Retrieves a single Dataverse record by its GUID. Use when you already know the exact record ID and want specific fields — faster and more precise than dataverse_query with a GUID filter. Specify select to limit returned columns and reduce payload size. WHEN TO USE: You have the exact record GUID and…

Gli serve: entitySetNamestring idstring

Puo’ usare: select expand formattedValues

{
  "tool": "dataverse_get",
  "parameters": {
    "entitySetName": "<string>",
    "id": "<string>"
  }
}

Creates a new record in a Dataverse table and returns the new record's GUID. Use dataverse_get_table_metadata first to confirm correct logical field names and required fields. For setting lookup fields, use the format "_fieldname_value" with the related record GUID. For bulk creation of multiple rec…

Gli serve: entitySetNamestring dataobject

{
  "tool": "dataverse_create",
  "parameters": {
    "entitySetName": "<string>",
    "data": "<object>"
  }
}

Updates an existing Dataverse record using PATCH semantics — only the fields provided in data are changed, all other fields remain unchanged. Requires the record GUID. Use dataverse_upsert instead if you want to create-or-update using an alternate key without knowing the GUID upfront. WHEN TO USE: M…

Gli serve: entitySetNamestring idstring dataobject

Puo’ usare: etag

{
  "tool": "dataverse_update",
  "parameters": {
    "entitySetName": "<string>",
    "id": "<string>",
    "data": "<object>"
  }
}

Permanently deletes a Dataverse record by its GUID. This operation is irreversible — you MUST set confirm=true to proceed. Use dataverse_list_dependencies to check if the record is referenced by workflows, plugins, or other components before deleting shared or configuration records. WHEN TO USE: Per…

Gli serve: entitySetNamestring idstring confirmboolean

{
  "tool": "dataverse_delete",
  "parameters": {
    "entitySetName": "<string>",
    "id": "<string>",
    "confirm": "<boolean>"
  }
}

Creates or updates a Dataverse record using an alternate key (no GUID needed). Returns operation="created" or "updated". Use mode="createOnly" to fail with an error if the record already exists, or mode="updateOnly" to fail if the record does not exist. Default mode="upsert" creates or updates. Supp…

Gli serve: entitySetNamestring dataobject

Puo’ usare: alternateKey alternateKeyValue alternateKeys mode

{
  "tool": "dataverse_upsert",
  "parameters": {
    "entitySetName": "<string>",
    "data": "<object>"
  }
}

Assigns a Dataverse record to a different user or team owner. Sets the ownerid lookup field using the OData bind syntax. WHEN TO USE: Changing the owner of a record to a different user or team. BEST PRACTICES: Use dataverse_list_users or dataverse_list_teams to find valid owner GUIDs first. WORKFLOW…

Gli serve: entitySetNamestring idstring ownerTypestring ownerIdstring

{
  "tool": "dataverse_assign",
  "parameters": {
    "entitySetName": "<string>",
    "id": "<string>",
    "ownerType": "<string>",
    "ownerId": "<string>"
  }
}

Creates an association between two Dataverse records via a named N:N or 1:N relationship. Requires the relationship schema name obtainable from dataverse_get_relationships. Use for N:N relationships or to link records without modifying a lookup field directly — for simple 1:N lookups, setting the lo…

Gli serve: entitySetNamestring idstring relationshipNamestring relatedEntitySetNamestring relatedIdstring

{
  "tool": "dataverse_associate",
  "parameters": {
    "entitySetName": "<string>",
    "id": "<string>",
    "relationshipName": "<string>",
    "relatedEntitySetName": "<string>",
    "relatedId": "<string>"
  }
}

Associates one source record with multiple related records at once via a named relationship, executing all associations in parallel. Unlike dataverse_associate (one pair at a time), this accepts an array of related IDs and runs them concurrently. Uses Promise.allSettled semantics — individual failur…

Gli serve: entitySetNamestring idstring relationshipNamestring relatedEntitySetNamestring relatedIdsarray

{
  "tool": "dataverse_associate_bulk",
  "parameters": {
    "entitySetName": "<string>",
    "id": "<string>",
    "relationshipName": "<string>",
    "relatedEntitySetName": "<string>",
    "relatedIds": "<array>"
  }
}

Removes an existing association between two Dataverse records on a named relationship. For N:N relationships, provide relatedId and relatedEntitySetName to build the correct $id URL. For 1:N relationships, relatedId and relatedEntitySetName are optional. Use dataverse_get_relationships to find the c…

Gli serve: entitySetNamestring idstring relationshipNamestring confirmboolean

Puo’ usare: relatedId relatedEntitySetName

{
  "tool": "dataverse_disassociate",
  "parameters": {
    "entitySetName": "<string>",
    "id": "<string>",
    "relationshipName": "<string>",
    "confirm": "<boolean>"
  }
}

Reads existing N:N associations for a record by querying through a navigation property. Returns the related records — use to verify what's already linked before calling dataverse_associate or dataverse_disassociate. WHEN TO USE: Check if a role already has specific privileges before adding them; che…

Gli serve: entitySetNamestring idstring navigationPropertystring

Puo’ usare: select top filter

{
  "tool": "dataverse_query_associations",
  "parameters": {
    "entitySetName": "<string>",
    "id": "<string>",
    "navigationProperty": "<string>"
  }
}

Executes a global (unbound) Dataverse action that is not tied to a specific record — for example WinOpportunity, SendEmail, or custom process actions. Use dataverse_execute_bound_action when the action must operate on a particular record. Actions differ from functions in that they are state-changing…

Gli serve: actionNamestring

Puo’ usare: parameters

{
  "tool": "dataverse_execute_action",
  "parameters": {
    "actionName": "<string>"
  }
}

Executes a global (unbound) Dataverse OData function that is read-only and returns data without side effects — for example RetrieveTotalRecordCount or InitializeFrom. Use dataverse_execute_action for state-changing operations. Use dataverse_execute_bound_action when the function/action requires a sp…

Gli serve: functionNamestring

Puo’ usare: parameters

{
  "tool": "dataverse_execute_function",
  "parameters": {
    "functionName": "<string>"
  }
}