[MCS-DE-GO] JSON object with non-string parameters

Currently we are facing the issue that we cannot find the right syntax in a JSON object within the https-Action to send numbers and booleans to an external API.

The only working syntax Composer allows in JSON in https-request body object is:

 {
     "question": "${conversation.string",
     "scoreThreshold": "${conversation.number}",
     "context": {
         "previousUserQuery": "${conversation.string2}",
         "boolean": "${conversation.boolean}"
     }
 }

This creates this JSON body on API call as output:

{
     "question": "und mein hund auch?",
     "scoreThreshold": "70",
     "context": {
         "previousUserQuery": "wer ist alles versichert",
         "boolean": "true"
     }
 }

What we want to have however is this: JSON body on API call expected output:

 {
     "question": "Hello World",
     "scoreThreshold": 70,
     "context": {
         "previousUserQuery": "Who are you?",
         "boolean": true
     }
 }

We tried different ways of adding the parameters inside the JSON object but the syntax validation and auto-correction in Composer does not allow us to create the correct output.

Please advise on options or the proper syntax for this or add this as a bug.

@joaollq @garypretty @cwhitten

[Stevenic]

@dmvtech use an expression for your body instead.

You can also use SetProperties to build up your object in memory and you should then be able to just say =dialog.body

[goergenj]

@dmvtech use an expression for your body instead.

You can also use SetProperties to build up your object in memory and you should then be able to just say =dialog.body

This worked for me:

={"question":turn.activity.text,"scoreThreshold":int(dialog.scoreThreshold),"context":{}}

If you set the property as “number” you can also use this:

={"question":turn.activity.text,"scoreThreshold":dialog.scoreThreshold,"context":{}}

This also works when you put it in a “Set Property” action as expression. When you try using the “Set property” as “object” the JSON parser will not allow you to add properties without the “${}” syntax which then will always create a string, even when you add the “int()” funtion to it.

I believe this is probably a bug but as the expression syntax works there is a work around. This should however be very clearly documented, if the “object” element cannot be fixed.