Actions6
Overview
This node integrates with the Dynamics 365 Dataverse API, enabling users to interact with various Dataverse resources and operations. Specifically, for the "Get lookup from global option set definitions" operation, it retrieves the options defined in a global option set by its attribute name. This is useful when you want to fetch all possible values (options) of a global option set to use them in workflows, such as populating dropdowns or validating input against allowed values.
Practical examples:
- Fetching all status codes or categories defined globally in Dataverse to dynamically build UI elements.
- Validating incoming data against the allowed values of a global option set before processing.
- Synchronizing option sets between Dataverse and other systems.
Properties
| Name | Meaning |
|---|---|
| Attribute Name | The logical name of the global option set attribute whose options you want to retrieve. |
Output
The output JSON contains an object with an options array. Each element in this array represents one option in the global option set and has the following structure:
{
"Id": <number>, // The numeric value of the option
"Name": <string> // The label of the option (localized)
}
If the global option set is not found or has no options, the output will contain the raw response from the API.
No binary data output is produced by this operation.
Dependencies
- Requires a valid connection to the Dynamics 365 Dataverse API using an API authentication token credential.
- The node depends on the Dataverse API endpoints for retrieving global option set definitions.
- Proper permissions are needed on the Dataverse environment to read global option set metadata.
Troubleshooting
Common issues:
- Incorrect or misspelled attribute name: The node may return empty results or errors if the specified global option set attribute name does not exist.
- Authentication failures: Ensure that the API key or authentication token is valid and has sufficient privileges.
- Network or API endpoint issues: Connectivity problems or incorrect environment URLs can cause failures.
Error messages:
- Errors related to "not found" or empty responses usually indicate the attribute name is invalid or the global option set does not exist.
- Authentication errors typically mention unauthorized access; verify credentials and permissions.
- Timeout or network errors suggest connectivity issues; check network settings and API availability.
To resolve these, double-check the attribute name spelling, validate credentials, and ensure the Dataverse environment is accessible.