You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/docs/content/docs/en/tools/microsoft_dataverse.mdx
+189-1Lines changed: 189 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,9 +27,10 @@ The Dataverse integration empowers solution builders and business users to autom
27
27
Connect Microsoft Dataverse to your automations to unlock sophisticated data management, orchestration, and business logic across your apps, teams, and cloud services.
28
28
{/* MANUAL-CONTENT-END */}
29
29
30
+
30
31
## Usage Instructions
31
32
32
-
Integrate Microsoft Dataverse into your workflow. Create, read, update, delete, upsert, associate, and query records in Dataverse tables using the Web API. Works with Dynamics 365, Power Platform, and custom Dataverse environments.
33
+
Integrate Microsoft Dataverse into your workflow. Create, read, update, delete, upsert, associate, query, search, and execute actions and functions against Dataverse tables using the Web API. Supports bulk operations, FetchXML, file uploads, and relevance search. Works with Dynamics 365, Power Platform, and custom Dataverse environments.
33
34
34
35
35
36
@@ -62,6 +63,27 @@ Associate two records in Microsoft Dataverse via a navigation property. Creates
62
63
|`targetEntitySetName`| string | Target entity set name used in the association |
63
64
|`targetRecordId`| string | Target record GUID that was associated |
64
65
66
+
### `microsoft_dataverse_create_multiple`
67
+
68
+
Create multiple records of the same table type in a single request. Each record in the Targets array must include an @odata.type annotation. Recommended batch size: 100-1000 records for standard tables.
|`entitySetName`| string | Yes | Entity set name \(plural table name, e.g., accounts, contacts\)|
76
+
|`entityLogicalName`| string | Yes | Table logical name for @odata.type annotation \(e.g., account, contact\). Used to set Microsoft.Dynamics.CRM.\{entityLogicalName\} on each record. |
77
+
|`records`| object | Yes | Array of record objects to create. Each record should contain column logical names as keys. The @odata.type annotation is added automatically. |
78
+
79
+
#### Output
80
+
81
+
| Parameter | Type | Description |
82
+
| --------- | ---- | ----------- |
83
+
|`ids`| array | Array of GUIDs for the created records |
84
+
|`count`| number | Number of records created |
85
+
|`success`| boolean | Whether all records were created successfully |
86
+
65
87
### `microsoft_dataverse_create_record`
66
88
67
89
Create a new record in a Microsoft Dataverse table. Requires the entity set name (plural table name) and record data as a JSON object.
@@ -125,6 +147,93 @@ Remove an association between two records in Microsoft Dataverse. For collection
125
147
|`navigationProperty`| string | Navigation property used for the disassociation |
126
148
|`targetRecordId`| string | Target record GUID that was disassociated |
127
149
150
+
### `microsoft_dataverse_download_file`
151
+
152
+
Download a file from a file or image column on a Dataverse record. Returns the file content as a base64-encoded string along with file metadata from response headers.
|`fileName`| string | Name of the downloaded file |
169
+
|`fileSize`| number | File size in bytes |
170
+
|`mimeType`| string | MIME type of the file |
171
+
|`success`| boolean | Whether the file was downloaded successfully |
172
+
173
+
### `microsoft_dataverse_execute_action`
174
+
175
+
Execute a bound or unbound Dataverse action. Actions perform operations with side effects (e.g., Merge, GrantAccess, SendEmail, QualifyLead). For bound actions, provide the entity set name and record ID.
|`actionName`| string | Yes | Action name \(e.g., Merge, GrantAccess, SendEmail\). Do not include the Microsoft.Dynamics.CRM. namespace prefix for unbound actions. |
183
+
|`entitySetName`| string | No | Entity set name for bound actions \(e.g., accounts\). Leave empty for unbound actions. |
184
+
|`recordId`| string | No | Record GUID for bound actions. Leave empty for unbound or collection-bound actions. |
185
+
|`parameters`| object | No | Action parameters as a JSON object. For entity references, include @odata.type annotation \(e.g., \{"Target": \{"@odata.type": "Microsoft.Dynamics.CRM.account", "accountid": "..."\}\}\)|
186
+
187
+
#### Output
188
+
189
+
| Parameter | Type | Description |
190
+
| --------- | ---- | ----------- |
191
+
|`result`| object | Action response data. Structure varies by action. Null for actions that return 204 No Content. |
192
+
|`success`| boolean | Whether the action executed successfully |
193
+
194
+
### `microsoft_dataverse_execute_function`
195
+
196
+
Execute a bound or unbound Dataverse function. Functions are read-only operations (e.g., RetrievePrincipalAccess, RetrieveTotalRecordCount, InitializeFrom). For bound functions, provide the entity set name and record ID.
|`functionName`| string | Yes | Function name \(e.g., RetrievePrincipalAccess, RetrieveTotalRecordCount\). Do not include the Microsoft.Dynamics.CRM. namespace prefix for unbound functions. |
204
+
|`entitySetName`| string | No | Entity set name for bound functions \(e.g., systemusers\). Leave empty for unbound functions. |
205
+
|`recordId`| string | No | Record GUID for bound functions. Leave empty for unbound functions. |
206
+
|`parameters`| string | No | Function parameters as a comma-separated list of name=value pairs for the URL \(e.g., "LocalizedStandardName=\'Pacific Standard Time\|
207
+
208
+
#### Output
209
+
210
+
| Parameter | Type | Description |
211
+
| --------- | ---- | ----------- |
212
+
|`result`| object | Function response data. Structure varies by function. |
213
+
|`success`| boolean | Whether the function executed successfully |
214
+
215
+
### `microsoft_dataverse_fetchxml_query`
216
+
217
+
Execute a FetchXML query against a Microsoft Dataverse table. FetchXML supports aggregation, grouping, linked-entity joins, and complex filtering beyond OData capabilities.
|`entitySetName`| string | Yes | Entity set name \(plural table name, e.g., accounts, contacts\)|
225
+
|`fetchXml`| string | Yes | FetchXML query string. Must include <fetch> root element and <entity> child element matching the table logical name. |
226
+
227
+
#### Output
228
+
229
+
| Parameter | Type | Description |
230
+
| --------- | ---- | ----------- |
231
+
|`records`| array | Array of Dataverse records. Each record has dynamic columns based on the table schema. |
232
+
|`count`| number | Number of records returned in the current page |
233
+
|`fetchXmlPagingCookie`| string | Paging cookie for retrieving the next page of results |
234
+
|`moreRecords`| boolean | Whether more records are available beyond the current page |
235
+
|`success`| boolean | Operation success status |
236
+
128
237
### `microsoft_dataverse_get_record`
129
238
130
239
Retrieve a single record from a Microsoft Dataverse table by its ID. Supports $select and $expand OData query options.
@@ -174,6 +283,60 @@ Query and list records from a Microsoft Dataverse table. Supports OData query op
174
283
|`nextLink`| string | URL for the next page of results |
175
284
|`success`| boolean | Operation success status |
176
285
286
+
### `microsoft_dataverse_search`
287
+
288
+
Perform a full-text relevance search across Microsoft Dataverse tables. Requires Dataverse Search to be enabled on the environment. Supports simple and Lucene query syntax.
| ↳ `Attributes`| object | Record attributes matching the search. Keys are column logical names. |
314
+
| ↳ `Highlights`| object | Highlighted search matches. Keys are column names, values are arrays of strings with \{crmhit\}/\{/crmhit\} markers. |
315
+
| ↳ `Score`| number | Relevance score for this result |
316
+
|`totalCount`| number | Total number of matching records across all tables |
317
+
|`count`| number | Number of results returned in this page |
318
+
|`facets`| object | Facet results when facets were requested. Keys are facet names, values are arrays of facet value objects with count and value properties. |
319
+
|`success`| boolean | Operation success status |
320
+
321
+
### `microsoft_dataverse_update_multiple`
322
+
323
+
Update multiple records of the same table type in a single request. Each record must include its primary key. Only include columns that need to be changed. Recommended batch size: 100-1000 records.
|`entitySetName`| string | Yes | Entity set name \(plural table name, e.g., accounts, contacts\)|
331
+
|`entityLogicalName`| string | Yes | Table logical name for @odata.type annotation \(e.g., account, contact\). Used to set Microsoft.Dynamics.CRM.\{entityLogicalName\} on each record. |
332
+
|`records`| object | Yes | Array of record objects to update. Each record must include its primary key \(e.g., accountid\) and only the columns being changed. The @odata.type annotation is added automatically. |
333
+
334
+
#### Output
335
+
336
+
| Parameter | Type | Description |
337
+
| --------- | ---- | ----------- |
338
+
|`success`| boolean | Whether all records were updated successfully |
339
+
177
340
### `microsoft_dataverse_update_record`
178
341
179
342
Update an existing record in a Microsoft Dataverse table. Only send the columns you want to change.
@@ -194,6 +357,31 @@ Update an existing record in a Microsoft Dataverse table. Only send the columns
194
357
|`recordId`| string | The ID of the updated record |
195
358
|`success`| boolean | Operation success status |
196
359
360
+
### `microsoft_dataverse_upload_file`
361
+
362
+
Upload a file to a file or image column on a Dataverse record. Supports single-request upload for files up to 128 MB. The file content must be provided as a base64-encoded string.
0 commit comments