Forum Discussion
Problem Exporting Copilot with Custom Connection
Here’s Some Other Helpful Steps
Solution 1: Add the custom connector to a solution
- This is the most frequent cause of the “Solution Export Error”.
- Create a new solution specifically for your custom connector.
- Add the custom connector to this solution
- Export this connector solution first.
- Import the connector solution into the target environment.
- Then import the main solution containing your Copilot
Solution 2: Verify credentials and configuration
- Ensure you have the correct API key or used a Valid Microsoft Entra authentication method.
- Check that the correct regional API endpoint is being used.
- If you are using a deployment, ensure there are no blank spaces at the beginning or end of the deployment name.
Solution 3: Check for other potential issues
- Firewall/Antivirus: Make sure your firewall or antivirus settings are not blocking the connection.
- Internet Connection: A stable and reliable internet connection is necessary for many Copilot functions.
- Sample JSON: When building a custom connector, you may need to define default responses by importing sample JSON data for your actions to ensure the Copilot can understand the data structure, according to this YouTube video.
Hope This Helps Mike Allen !
Solution one was the clue. I added the connector to its own solution and exported that. I removed the tools from the Copilot solution and exported that. Then deleted both solutions and all their objects. I reimported the connector solution and the copilot solution and added the tools to the copilot solution. I ran the solution checker, which ran ok. I then exported the copilot as a managed solution, it asked If I wanted to add the connection to the solution and I said yes. After all this I imported the copilot solution into the production managed environment with no problem. Note that I did not need to import the connector solution first as the build had incorporated it into the copilot solution.
Note that the connector is a swagger file and I plan to add a longer description to each endpoint. There is a limit of 1024 characters, so I have to be precise, and this gives the orchestration the information it needs. The Swagger is detailed, and I assume that the orchestration pulls the structure(?). Forward plan is to manage the connector in Swagger.
As an extra, I'm considering adding some knowledge on accounting terminology to either the instructions or as a knowledge file. For example, ROI has a field Return On Investment in the Executive Summary. Or maybe an instruction to scan all the item names in the report first. It's a work in process, next step is to add more endpoints and add test questions. Thanks for your feedback UhLukas , we need this forum to thrive 😁
Your welcome feel free to invite as many members as you can