Applies to Product - Microsoft Dataverse
What’s happening?
The customer is experiencing an issue while importing a solution in the pipeline, specifically at the last step of pushing from the affected environment to production. The error message indicates that the import failed during a plugin execution, stating, "The given key was not present in the dictionary," and also mentions a failure to find connection references with logical names.
The customer is experiencing an issue while importing a solution in the pipeline, specifically at the last step of pushing from the affected environment to production. The error message indicates that the import failed during a plugin execution, stating, "The given key was not present in the dictionary," and also mentions a failure to find connection references with logical names.
Reason:
The underlying cause of this is related to missing connection references during the solution import process. The error details indicate that the system could not find a specific connection for the API, resulting in a 404 error. Additionally, a 500 internal server error was noted, which is attributed to a system error from the service provider's side.
The underlying cause of this is related to missing connection references during the solution import process. The error details indicate that the system could not find a specific connection for the API, resulting in a 404 error. Additionally, a 500 internal server error was noted, which is attributed to a system error from the service provider's side.
Resolution:
To resolve this, the following steps were taken:
- Re-added the necessary connection in the cloud flow.
- Published customizations.
- Performed a manual import of the solution, which successfully resolved the issue.
If similar errors occur, it is recommended to manually import the solution to avoid issues related to the environment setup.
To resolve this, the following steps were taken:
- Re-added the necessary connection in the cloud flow.
- Published customizations.
- Performed a manual import of the solution, which successfully resolved the issue.
If similar errors occur, it is recommended to manually import the solution to avoid issues related to the environment setup.