Microsoft VA
Powershell
when i update the KB and dispatch files via
-> .\Deployment\Scripts\update_cognitive_models.ps1 -RemoteToLocal
Follow the steps at
1:1.
no Errors :-)
(in the screenshot)
@danieldangler I tried wrong config file or empty luis app, none of them reproduce your situation. Do you add some special character in your luis app?
Maybe you could try to add the following lines to see the result of luis export:

These are the steps i did:
(My goal was to connect a new KnowledgeBase)
The problem is that nothing changes in the webinterface of LUIS.
I hope you can help me out with that :-)
ps. i tried to insert the four lines of code inside the Script but nothing happens. It just lists all of my Intents/utterances
@danieldangler maybe it is caused by encoding. You could try run $OutputEncoding = [Console]::OutputEncoding before running the script.
@xieofxie sadly this wont help.
I searched a bit more in the Issue Tab and found another User with the same (or similar) problem in
(But i dont get the Error with an invalid Subscription Key etc. by the way)
Could this be a region Problem?
UPDATE: If i change something in the KnowledgeBase and execute the command to update my cognitivemodels, LUIS is getting updated aswell, but inside the chat i get a Error if i want to ask a question from the connected KB. Strange strange strange.
What version of the tools are you running? Specifically dispatch, but also luis (run dispatch-v) and other tools would be good to know.
What OS are you running on?
Hi @danieldangler since General is also working wrongly, I would suggest a tedious way to check it..

It happens here, so first, check out the output of first part whether it is a valid json (same as General.luis when you deploy):
luis export version --appId $luisApp.appId --versionId $luisApp.version --region $luisApp.authoringRegion --authoringKey $luisApp.authoringKey
Then save it to file via
luis export version --appId $luisApp.appId --versionId $luisApp.version --region $luisApp.authoringRegion --authoringKey $luisApp.authoringKey | Out-File temp.json -Encoding OEM
(or any of the encoding until it looks right). They may be different because console and Out-File use different encodings.
Last refresh it to see if it could be refreshed as the original General.lu.
ludown refresh -i temp.json -n "$($luisApp.id).lu"
If any of these steps could not be right, please report the locale of General you used and your system language region.
Same exact issue here.
Same exact issue here.
I got around this for now by changing the script to output to JSON files in a temp directory and then calling ludown refresh on them, instead of reading from stdin.
I am also having the same issue with Luis and Qna files. @jason-hunt I also found that outputting to a temporary json file worked.
I have updated the update_cognitive_models script in the VA template to resolve this issue. You can find it here: https://github.com/microsoft/botframework-solutions/blob/master/templates/Virtual-Assistant-Template/csharp/Sample/VirtualAssistantSample/Deployment/Scripts/update_cognitive_models.ps1
@lauren-mills Thanks for updating the script.
As a sidenote I also have to edit the exported json file created because the depreciation error for the tools is added to the top of the file. Ex:
-----------------------------------------------------------
NOTICE:
This tool has been deprecated.
All functionality was ported over to the new BF CLI.
To learn more visit https://aka.ms/NewBFCLI
-----------------------------------------------------------
"qnaDocuments": [
{
"id": 1,
This causes the ludown refresh command to fail parsing the json. I only have this problem for the qna maker export and not the luis one.
(This depreciation error is also kind of annoying because the new bf tool has not implemented an export command yet, unless I'm not looking in the right place?)
Ah perfect! this works for me. Thank you :)
Looks like the removal for qnamaker is in the works: https://github.com/microsoft/botbuilder-tools/commit/c61cb62e7b2e02be3520e854102b477ec5c8856f
Most helpful comment
@lauren-mills Thanks for updating the script.
As a sidenote I also have to edit the exported json file created because the depreciation error for the tools is added to the top of the file. Ex:
This causes the ludown refresh command to fail parsing the json. I only have this problem for the qna maker export and not the luis one.
(This depreciation error is also kind of annoying because the new bf tool has not implemented an export command yet, unless I'm not looking in the right place?)