Actions6
Overview
This node integrates with the Microsoft Dynamics 365 Dataverse API, enabling users to interact with Dataverse entities and their metadata. Specifically, for the "Get lookup from option set definitions" operation, it retrieves the list of options (lookup values) defined in an OptionSet attribute of a specified Dataverse entity.
Common scenarios include:
- Fetching available choices for a picklist (OptionSet) field in a Dataverse entity to dynamically populate dropdowns or validate input.
- Synchronizing option sets between Dataverse and other systems.
- Building user interfaces that require displaying human-readable labels alongside option values.
For example, if you have a "Status" OptionSet attribute on the "contacts" entity, this node can retrieve all possible status options with their IDs and labels.
Properties
| Name | Meaning |
|---|---|
| Entity Name | Select the Dataverse entity to query, e.g., contacts, accounts. |
| Attribute Name | Enter the logical name of the OptionSet attribute within the selected entity. |
Output
The output JSON contains an options array representing the OptionSet entries. Each entry has:
Id: The numeric value of the option.Name: The label of the option as displayed in Dataverse.
Example output structure:
{
"options": [
{
"Id": 1,
"Name": "Option Label 1"
},
{
"Id": 2,
"Name": "Option Label 2"
}
]
}
No binary data is produced by this operation.
Dependencies
- Requires an authenticated connection to Microsoft Dynamics 365 Dataverse via an API key or OAuth credentials configured in n8n.
- The node depends on the Dataverse API endpoints for retrieving entity metadata and OptionSet definitions.
- Proper permissions are needed on the Dataverse environment to read entity metadata and OptionSet attributes.
Troubleshooting
- Authentication errors: Ensure the API credentials are valid and have sufficient permissions.
- Empty or missing options: Verify that the specified entity and attribute names are correct and that the attribute is indeed an OptionSet type.
- API rate limits or timeouts: Large OptionSets or slow network connections may cause delays; consider retrying or optimizing queries.
- Invalid attribute name error: Double-check the attribute logical name spelling and casing.
- Node fails with unexpected errors: Enable "Continue On Fail" to isolate problematic items and inspect error details.