If you the data type of a parameter that you're passing is string, please make sure that you enclose the argument you're entering with quotation marks. This is especially important for long numeric IDs (such as those used by the Flickr API) as, otherwise, Service Explorer will interpret these as integers and you'll end up with the wrong ID and failing call.
So, for instance, if a call takes a string ID, enter "72157600948554269" not 72157600948554269 into the input box for the ID parameter in the SWX Service Explorer.
Remember, when in doubt, enclose in quotes. 
(By the way, I am aware that the SWX Service Explorer should be smarter about this and enclose string arguments in quotes for you. It should be smarter in a few other areas too and these are on my to-do list for Version 1 as they catch me out from time to time too.)
I think not the service browser but the service class itself should take care of that. Service browser is not supposed to manipulate data in any case should it ?
Also when talking json, this ‘ is not a valid json, should use ” instead.
Hi Folkert,
No, the Service Browser is not supposed to manipulate the data but it could a few things to make it easier for people to input it. Going to be looking into this before I release version 1.
Hi,
I’m trying to send a variable from an inputText.
(…)
args:[inputText.text],
(…)
When publishing for Flash7 there’s no problem passing the string, but when I publish for Flash8 the end result is:
“r” the string.
If I send the variable directly using quotation marks(Flash8):
(…)
args:["test"],
(…)
the result is fine.
What am I doing wrong?