Hello people,
by reading the different elements of the documentation (in particular concerning JSON and OOB) I can not determine what would be the easiest way to recover user variables _0 stored in $XXX and insert them in the columns of a database provided for this purpose.
I need a REST API on the DB side, but on the side of ChatScript (which is a server), is it possible to simply create a JSON object collecting my $name and $city directly in a topic and doing POST ?
After I imagine that a modification of the file simpletopic.top is necessary to declare the modalities of connection with the database?

Am I going in the right direction?
I am surprised to find only information about the receipt of OOB data in the documentation and almost nothing on the mail, including in the forum.
Maybe I read it wrong ...

Simple answer, yes.

If your remote store has a REST api then you can just build the payload in JSON in ChatScript and use ^jsonopen() to interact with that API. We use this extensively, not only to retrieve additional data but also to insert/update/delete.

Thanks for your reply Andy. What you say confirms what I thought I understood. It is astonishing that the documentation, although very detailed and very precise, does not give examples on this subject. Maybe a “Howto” could do it.

So let’s go: how to store a user variable memorized as $myvar =_0 in a database.

ChatScript manuals invoked:
- Installing-and-Updating-ChatScript
- ChatScript-Json
- ChatScript-System-Functions-Manual

Prerequisites :Have a ChatScript server, a Postgres database with a REST API based.

ChatSCript side:

1. prepare JSON to build the payload (issue a JSON string of the content of the variable to be broadcast)
In case your $myvar variable should be stored in your mycolumn column

CS should build JSON structure like

2. Post the message to the REST API.
- open a rule to react u : ()
- set URL of your REST API
- Set your login
- declare header
- POST your data through the API

Can it work this way ?
sorry for the “beginner aspect” of the thing

1. prepare JSON
I am not a huge fan of using ^jsonparse() to create a JSON object from a string directly in CS script because it can get messy with nulls and escaping characters and ungainly with deep structures.
I prefer:

Note: Json dotted syntax never generates a fail in CS

2. Post the message
I don’t know your full situation but a rule is not strictly necessary here. You could build an utility topic that you trigger by a ^respond() to invoke some common functionality, but that is a bit of overkill. It is easier to write your own macro to do a common function that can then be called from anywhere.

Note: that CS can now allow the data parameter be passed in ^jsonopen() as a JSON object, instead of a string. The engine will do the serialization correctly. This is useful if your payload exceeds the CS output buffer size (about 80K).

So now that you’ve constructed your payload object, got a general function (though the above version is minus error handling and could be made even more general purpose), you just need to call it after you have prepared your JSON.

And there you go.

Thank you so much for your help Andy I will test all that.

Perhaps a series of Howto (or FAQ) could complement the documentation effectively, what do you say?

I’ll add it to my list