Jan Görgen

Adding a note: When I switch the **Microsoft.Bot.Builder.\*** packages from "4.14.1" to "4.13.1" in my local Bot csproj, the bug does not occur.

@srinaath **.Net** Microsoft.Bot.Builder.AI.Luis Microsoft.Bot.Builder.AI.QnA Microsoft.Bot.Builder.Dialogs.Adaptive.Runtime

@srinaath @mrivera-ms Any update on this topic? Will this be fixed in the next release? We currently cannot upgrade from 2.0.0 to 2.1.0 due to this issue.

@skommireddi Thanks for reaching out via Chat. This must be discussed. If this is the new expected behaviour this is a major change and a major issue to a number...

We found the causes for the double input as discussed with Gabo. We fixed a code issue in our Custom SharedSkill Issue which caused the double inputs required. All Skill-Calls...

@sgellock Has the documentation been extended with a best practice which catches all cases like this by now?

@cwhitten No. What would this look like to create a JSON body?

> @dmvtech use an expression for your body instead. > >  > > You can also use `SetProperties` to build up your object in memory and you should then...

See also: https://github.com/microsoft/BotFramework-Composer/issues/3317

@peterinnesmsft Thanks for the information. @garypretty @cwhitten Is it possible to add the "preditionoptions" into the appsettings of the Bot in Composer: "luis": { "name": "Botname", "defaultLanguage": "de-de", "authoringEndpoint": "https://xx-authoring.cognitiveservices.azure.com/",...