Hi,
The issue you're encountering with the `ImportSolution` Unbound Action and the `ConnectionReferences` parameter likely stems from how the **ComponentParameters** collection is structured and interpreted by the Dataverse API.
Although the documentation suggests that `ConnectionReferences` can be passed as part of `ComponentParameters`, the error:
> **Invalid property 'ConnectionReferences' was found in entity 'Microsoft.Dynamics.CRM.crmbaseentity'**
indicates that the API does not recognize `ConnectionReferences` as a valid property in the context you're using it.
### Recommendations:
1. **Use the correct entity structure** – Instead of embedding `ConnectionReferences` directly inside `ComponentParameters`, try passing each connection reference as a separate `crmbaseentity` object with the appropriate logical name and attributes.
2. **Review the expected schema** – The `ComponentParameters` should be a collection of entities where each entity represents a component (e.g., a connection reference), not a nested structure.
3. **Use the Dataverse Web API or SDK** – Consider using the Dataverse Web API or Power Platform Tools for Visual Studio to validate the structure and test the import.
4. **Check for known limitations** – The `ImportSolution` action may not support all component types equally. You can refer to the ImportSolution Action documentation for supported parameters and examples.
Please verify if this helps clarify the issue or guide your next steps.
Thanks and best regards,
Daniele
*Note: This response was prepared with support from Copilot to ensure clarity and completeness.*
