Dataverse icon

Dataverse

Seamless integration with the Dynamics 365 Dataverse API

Overview

This node integrates with the Dynamics 365 Dataverse API, enabling users to retrieve data using either FetchXML or OData query languages. The "Get data" operation allows querying Dataverse entities flexibly by specifying a custom query string. This is useful for scenarios where you want to fetch records from Dataverse based on complex filters or specific attributes.

Practical examples include:

  • Retrieving customer records that meet certain criteria.
  • Querying related entity data using FetchXML joins.
  • Extracting data for reporting or further processing in an automation workflow.

Properties

Name Meaning
Type Selects the query type to use: either FetchXML (a proprietary XML-based query language) or OData (an open protocol for RESTful APIs).
Query The actual query string to execute against the Dataverse Web API. Supports both FetchXML and OData syntax depending on the selected Type.

Output

The node outputs JSON data representing the results of the executed query. The structure depends on the query but generally includes the retrieved records and their fields as returned by the Dataverse API.

  • The output JSON contains the queried data under the json property.
  • Each item corresponds to one input item processed.
  • No binary data output is produced by this operation.

Dependencies

  • Requires an authenticated connection to the Dynamics 365 Dataverse API via an API key or OAuth token configured in n8n credentials.
  • The node uses internal authentication methods to connect and perform queries.
  • Network access to the Dataverse environment is necessary.

Troubleshooting

  • Authentication errors: Ensure the API credentials are valid and have sufficient permissions to read data.
  • Invalid query syntax: Errors may occur if the FetchXML or OData query string is malformed. Validate queries using external tools or Dataverse query builders.
  • Empty results: Confirm that the query matches existing data and that the entity logical names and attribute names are correct.
  • API limits: Large queries might hit API throttling limits; consider paginating requests or filtering data more narrowly.

Links and References

Discussion