As of April 12th, you must go to Progress SupportLink to create new support cases or to access existing cases. Please, bookmark the SupportLink URL and use the new portal to contact the support team.
Dave thanks for the feedback, will give it a try and let you know.
D
Dave
said
over 9 years ago
Vaughan - we deployed a fix for this issue, should be working fine now. Let me know if you encounter any issues!
D
Dave
said
over 9 years ago
Vaughan - looks like the API console isn't properly encoding type information in some cases. The lat/long values you provided are being sent as strings, not numbers, triggering the validation failure. I've filed a ticket to track this down, but in the meantime, I'd suggest avoiding using the API console to manipulate _geoloc field. The data store interface should work just fine, however.
V
Vaughan Daly
said
over 9 years ago
When using the API Console.
D
Dave
said
over 9 years ago
Are you using the API Console or the data store view when this fails?
Vaughan Daly
"error": "ParameterValueOutOfRange",
"description": "The value specified for one of the request parameters is out of range",
"debug": "Geolocation points must be in the form [longitude, latitude] with long between -180 and 180, lat between -90 and 90"
This is the data in the _geoloc field :
"_geoloc": [
27.93606251480797,
-26.137809050293768
]
This works fine from inside an application but not from the console. I have even tried to using only the 2 decimal places but it makes no difference.
1 person has this question