creating a BOTB from BOTA in same environment

[dacostadaniel]

Hello Colleagues

Can anyone help with creating a BOTB from BOTA in same environment please?

pac copilot extract-template --environment 1e33b310-6f9d-e3ff-8941-a0862324b21e --bot 674457c4-e1e5-ee11-904c-0022480ac6c9 --templateFileName CALINT.yaml

the above pac copilot extract-template works however,

the above pac copilot create fails

pac virtual-agent create --SchemaName cr7d0_calint --TemplateFileName CALINTER.yaml --environment 1e33b310-6f9d-e3ff-8941-a0862324b21e --displayName CALINTER --solution CALINTER

Loaded 357 components for bot 'CALINT' with id a46dccfb-fb85-4479-bff2-f85a22a31b53. Primary language: English, supported languages:
Sorry, the app encountered a non recoverable error and will need to terminate. The exception details have been captured and will be forwarded to the development team, if telemetry has been enabled. Exception Id: 34c67bca-e784-4022-bf79-4a135422a3e9, Exception Type: Microsoft.Bot.Platform.Content.Exceptions.DataverseBadRequestException

any help appreciated.

I just need a copy so I can make minor changes to BOTB rather than kill myself building a new one.

regards
Daniel da Costa
+447902596815
daniel@educlaas.com

[haack42]

Hello Daniel,

The exception contains "It is invalid to create component bot with the same export key value(s) as an existing component. Please change the key. The current value(s) are schemaname: daniel_calint"

You can also run pac telemetry status to get the path to the log file which should contain this exception contents. For me this showed this message when I tried to use a schemaName already in use:

2024-06-28 06:24:01.9153 | FTL | bolt.Session :: HTTP Status:BadRequest, ServiceRequestId: 5e0d57d9-ab6c-480a-a031-8b4945843fd4 [0x80072013:ExportKeyInvalidCreate] It is invalid to create component bot with the same export key value(s) as an existing component. Please change the key. The current value(s) are schemaname: crd15_translationTestCopilot ...

Regards,
Matthias

[dacostadaniel]

Hello

Will I be receiving any more guidance on this issue please?

regards
Daniel

[haack42]

Hello,

Please use the version 1.32.8 which should not fail on the template extraction. The version 1.33.5 indeed has an issue for which a fix was provided today and the next release will contain it.

I tried a new copilot with a connector, extracted and created it... this worked. But it fails for your YAML, even when I use my working connector reference. I do not know why yet but I shared this with my colleagues.

Regards,
Matthias

[dacostadaniel]

Hello

I have doe what you requested; extract works but fails the create

Microsoft Windows [Version 10.0.19045.4651]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Sevara Kenjaeva>pac use 1.32.8
Now using version 1.32.8 of the Microsoft PowerApps CLI.

C:\Users\Sevara Kenjaeva>pac copilot extract-template --environment 1e33b310-6f9d-e3ff-8941-a0862324b21e --bot a3261537-7772-4bea-808d-e712d5133511 --templateFileName CAL_2024_07_19_SOL_1_32.8.yaml -o
Connected as daniel@educlaas.com

Loaded 355 components for bot 'CAL' with id a3261537-7772-4bea-808d-e712d5133511. Primary language: English, supported languages:

CAL -> C:\Users\Sevara Kenjaeva\CAL_2024_07_19_SOL_1_32.8.yaml
CAL_2024_07_19_SOL_1_32.8_yaml.txt

C:\Users\Sevara Kenjaeva>pac virtual-agent create --schemaName cr7d0_CALINTERN4 --templateFileName CAL_2024_07_19_SOL_1_32.8.yaml --environment 1e33b310-6f9d-e3ff-8941-a0862324b21e --displayName CALINTERN4 --solution CALINTERN4_2024_07_19_SOL
Connected as daniel@educlaas.com

Loaded 355 components for bot 'CALINTERN4' with id f71902b5-fb94-48bf-973b-354415befcfa. Primary language: English, supported languages:
Sorry, the app encountered a non recoverable error and will need to terminate. The exception details have been captured and will be forwarded to the development team, if telemetry has been enabled. Exception Id: 65a06300-8a7a-42c5-ab43-3f2c61da59e6, Exception Type: Microsoft.Bot.Platform.Content.Exceptions.DataverseBadRequestException
The diagnostic logs can be found at: C:\Users\Sevara Kenjaeva\AppData\Local\Microsoft\PowerAppsCLI\Microsoft.PowerApps.CLI.1.32.8\tools\logs\pac-log.txt
pac-log.txt

I do not know why. Also i do not know how to interpret the log file. Mayb eyou can tell me so I can delete the topic that might be causing the issue. I looked in process but I do not know which column contains the identifier.

regards
Daniel

[dacostadaniel]

By the way, you can give the dev team my yaml and ask them to use it; if they cannot solve the issue then the extract and create solution is not much of a COE master piece as my yaml is real-world issue. I hope you can help with this.

regards Daniel

[dacostadaniel]

Hello Sir,

can I ask if there is any update on the issue I reported please? Is there a chance that I will receive a solution please?

regards
Daniel da Costa