How to use TBox Clipboard to copy JSON content to the clipboard

I just tried this myself (with Tosca 2023.1) and it worked fine. Do you get the same error if you use e.g. TBox Set Buffer to do the same thing?

If you haven’t already - try editing the Value column and make sure there’s no extra characters, line breaks etc that might not be obvious from the way Tosca displays the value.

Out of curiosity - what are you planning to do with the response once it’s in the clipboard? As there may be a different way to achieve whatever it is you’re trying to do with it.

Hello @brendon.russell 

 

You’re right! It works… somehow! For this post, I simplified the example back to the minimal steps it takes to achive my goal: get the JSON response in the clipboard > and the simplified version works very well, due to your comment. Nice nice nice 😅😅😅!!!! Thank you very much!

 

What led to my error is a detour utilizing a buffer, please take a look at this screenshot from the scratchbook:

Test looks like this

Name	ActionMode	Value
TBox Set Buffer
lastRes	Input	{RES[LastResponseResource]}
<Buffername>
TBox Clipboard
Value	Input	{B[lastRes]}

 

So, copying the RES to a buffer and clipping this buffer does not work. Seems, “TBox Set Buffer” is the bad boy in the sequence… 

 

Nevertheless… Thank you very much for your support @brendon.russell ! Kind regards

Ah very sneaky, the actual steps you were using were not the same as your original screenshot ;)

I was able to replicate your issue using the steps above, i.e. buffer the response resource then try to copy the buffered value to the clipboard.

After a little more trial and error, I was able to trigger a similar error with TBox Set Buffer itself. I thinik It must be something to do with the combination of { } and “ characters (and possibly others in your full JSON response), which have specific meaning when used as a Tosca value. Normally you’d have to work hard to escape those characters in the right way so that Tosca treated them as a literal string and didn’t try to parse them as special values.

I guess {RES[]} is designed to cater for those characters so it works, but once that value has been converted to a normal string of text (e.g. by buffering it), you’re probably not going to have any luck trying to use them as a Tosca value.