Dataverse

Overview

This node integrates with the Microsoft Dynamics 365 Dataverse API, enabling users to perform various operations on Dataverse entities. Specifically, for the "Get lookup from entity" operation, it retrieves a list of records from a specified Dataverse entity, returning selected columns that represent an ID and a name. This is useful when you want to fetch reference data or lookup values from Dataverse to use in workflows, such as populating dropdowns, validating inputs, or linking related records.

Practical examples:

• Fetching a list of contacts with their IDs and names to populate a selection menu.
• Retrieving account records to associate with a new sales order.
• Getting lookup values dynamically to ensure workflow actions use up-to-date entity data.

Properties

These properties allow the user to specify which entity and which fields to retrieve for the lookup operation.

Output

The output is a JSON object containing an options array. Each element in this array represents a record from the selected entity, structured as:

{
  "options": [
    {
      "Id": "<value of the selected ID column>",
      "Name": "<value of the selected Name column>"
    },
    ...
  ]
}

This structure provides a simple list of key-value pairs suitable for populating UI elements or further processing in workflows.

The node does not output binary data for this operation.

Dependencies

• Requires an authenticated connection to the Microsoft Dynamics 365 Dataverse API via an API key or OAuth credentials configured in n8n.
• The node uses cached metadata about entities and their columns to provide options for entity and column selection.
• Network access to the Dataverse environment is necessary.

Troubleshooting

• Authentication errors: Ensure that the API credentials are correctly configured and have sufficient permissions to read entity data.
• Empty or missing results: Verify that the selected entity name and columns exist and contain data.
• Invalid column selections: If the chosen ID or Name column does not exist or is not accessible, the node may fail or return empty results. Use the provided dynamic options to select valid columns.
• API rate limits or timeouts: Large datasets might cause delays or throttling; consider filtering queries or limiting returned records if supported.

Common error messages will typically relate to authentication failures, invalid entity or column names, or network issues. Resolving these involves checking credentials, verifying entity schema, and ensuring connectivity.

Links and References

• Microsoft Dataverse documentation
• Dynamics 365 Web API overview
• n8n Documentation - Credentials

If you need details on other operations or resources, please provide their names.