Hi,
I've seen this a few times but don't seem to have a definite answer. This is concerning exporting a bot from one tenant to another.
The Scenario
Aim:
Content:
Issue:
Exporting from Tenant A and Importing to Tenant B causes issues with the connector. The issue being that when imported, the connector is broken as it appears to be looking for the reference ID of the connector in Tenant A, which does not exist in Tenant B. You cannot select an alternative connector during the import process. You cannot point it to an alternative connector after import.
Our Current Workaround:
Now, that's a bit of a pain in the above example. When the bot gets built out more it becomes a massive hurdle and more open to human error. We end up having to alter ID's in lots of different places within the XML and JSON files. For example, every topic/flow JSON file that uses a connector, requires it to be altered.
Is there an inherent/already built in way to do this that we've missed? Is there an alternative method? How can we successfully import a bot to another tenant that uses custom connectors with as little pain as possible? 🙂
Thanks,
Jase
Hi @Diganta ,
Environment ID: eab21d64-5f94-e758-8cf0-ab03f2314aa9
Custom Connector ID: new_sharedfresh5fservice5f165f115f95f405f1d0ac512f0529afe5ab8a04ad2_24b63
Flow ID: (Flow Identifier): v1/eab21d64-5f94-e758-8cf0-ab03f2314aa9/5230c420-135d-461d-ac34-c72ac37677b5
Bot ID: f3b3d584-5ff7-4c3c-841c-0075a48f05b2
I hope all IDs are correct, if no, please feel free to reach out to me.
Kindest regards,
Jon
Hi Diganta,
Thanks for the response. My lead developer is away for a week, so he may post the details, but if not then he will post them when he returns.
Many Thanks.
Thank you, Jase, for reporting this issue. This could be a bug in the custom connector. Please share your environment ID, custom connector ID, flow ID, and bot ID.