Hi I am using clickatell REST api and getting following error:
{"messages":[],"error":"ScheduledDeliveryTime format is incorrect. - "}"
I am using correct format "yyyy-MM-dd'T'HH:mm:ssZ"
please help to fix this issue.
thanks
You need to do exactly like in documentation
--> 2018-01-25T18:17:20+0200
+0200 is your timezone
And don't forget to concatenate 'T' letter in the middle
If you don't intend to schedule it for a later time, remove that property(name-value pair) from your json.
That worked for me for now but please do post the real answer if you found it.
Related
I think the title says it all. I have a shared google sheet which I'd like to limit several columns to make sure the information is correctly added as a hexcode.
I've been searching and I just can't seem to find anything, but this code I found for EXCEL may be a starting point:
=AND(LEN(A2)<13,ISERROR(HEX2DEC(A2))=FALSE)
It does not seem to work for Sheets...
try:
=ISNUMBER(HEX2DEC(REGEXEXTRACT(A1, "#(.*)")))*(LEN(A1)<8)
when i set my cardholder to be either NOTENROLLED or TECHNICALDIFFICULTIES the wrong values are returned from Sage Pay V.4.0
As per the documentation, I expected the 3DSecureStatus response to be NOAUTH and INCOMPLETE respectively but i am getting Status = 3DAuth and 3dSecureStatus = OK for NOTENROLLED and OK,OK for TECHNICALDIFFICULTIES.
All other magic values returned expected results.
Is this to do with my 3D Secure settings in Test sagepay? I haven't specifically set any rules, just left all as default
thanks
I think you're looking at an older version of the direct guide.
re: TECHNICALDIFFICULTIES - the value is (now) actually TECHDIFFICULTIES
And the latest version of the guide says that NOTENROLLED will "Fallback to 3DSv1" rather than returning a 3DSecureStatus of NOAUTH which was what the previous version of the guide said.
The latest version of the guide is here.
Top man/woman. that's the answer. Sage have cunningly changed the document but kept the status of Draft with the same date and version number. useful.!
I am hoping there haven't been any other changes to the doc.
If anyone from Sage is following this forum it would be good to have a version history in the documentation to stop anyone else having this type of problem.
Thanks for the tip
http://localhost:9191/sts/ADD?FILENAME=/tmp/newEventsFlag.csv&LINE=7ddb876ac39c485a&ADD_MODE=FIRST&UNIQUE=TRUE
If i run this multiple times and then do a GET http://localhost:9191/sts/LENGTH?FILENAME=/tmp/newEventsFlag.csv
I can see that the body length is equal to the number of posts I made.
So unique parameter does not work I guess or am I missing something here?
If it does not work is it possible to get the source code to fix this?
This is a bug in the simple table server version 2.2.
Should be fix in 2.3
I tried this URL and it works fine...
http://api.flickr.com/services/feeds/photos_public.gne?per_page=6&jsoncallback=?
...almost. It is set to "per_page=6" but it don't listen to it. What's wrong?
You have an extra question mark at the end. Can you remove the last parameter?
It seems like this URL does not accept any limit.
Unfortunately according to the API this isn't supported
http://www.flickr.com/services/feeds/docs/groups_pool/
I was in need of it as well
i am using ruby gems json_pure and when i get parsing errors i am not able to determine the line number where the error is occuring. i was expecting to find a validator written in ruby that would tell me the line number. what is the best ruby approach to finding the json errors quickly?
thanks!
You could try Kwalify: http://www.kuwata-lab.com/kwalify/ruby/users-guide.html
It's not just a JSON/YAML validator, but you give it a schema and it validates against that.
You could use that to verify that your config file is correct (as per your definition of "correct") as well as correct JSON (or YAML), and it will tell you what line number the error happened on, and a bit of context for the error as well.
I removed a ']' from a sample in their documentation and the error message it gave me was
ERROR: document12a.json:10:1 [/favorite] flow sequence is not closed by ']'.
It also does data binding class generation if you want. It seems like a pretty good configuration management/validation tool.
You might find it easier to use http://www.jsonlint.com/ to check the JSON is valid - it will highlight any problematic lines.
It's and old question, but it's still an issue in current Ruby.
Default JSON parser in Ruby does not tell you the line number and/or column number the parse error occured. Just 'parse' error and that's it.
You could change the parser to Oj and use with MultiJson gem.
Oj is great, it's very fast, and it will show the line and even the column number the parsing errors occured! Great.
Sample error for one-line very big JSON (170KB+), Oj will give column 102421.
.../adapters/oj.rb:15:in `load': unexpected character at line 1, column 102421 [parse.c:666] (MultiJson::ParseError)
JSON is supposed to be sent over the network as a string, so there's actually only one line.