Hi Mortenapologies for the delay in replying.
I am still seeing this with
/api/trackedEntityAttributes
2.20-SNAPSHOT
Build revision: 19647
I will let you know if I encounter any others.
Regards
Alan
On Wed, Jul 8, 2015 at 11:06 PM, Morten Olav Hansen
wrote:
> Hi
>
> In which endpoi
Hi
In which endpoints do you see this? I have fixed it in the data element
operand endpoint, but there could be others also
--
Morten
On Thu, Jul 9, 2015 at 12:23 AM, Alan Hill wrote:
> Hi Morten
>
> Thanks for the information.
>
> Regarding the filtering bug, do you know which version/build t
Hi Morten
Thanks for the information.
Regarding the filtering bug, do you know which version/build this was fixed
in? I am still seeing the issue in 2.20-SNAPSHOT build #19473
Kind regards
Alan
On Tue, Jul 7, 2015 at 9:35 PM, Morten Olav Hansen
wrote:
> Hi
>
> Most of this should now be f
Hi
Most of this should now be fixed, please note that also our import
summary(ies) are now wrapped in a WebMessage (check responseType to know
which payload was sent)
Regarding the filtering bug, that was fixed a while back.
We know about the difference in paging parameters, but we will not chan
Hi
I have a couple of additions:
- Filtering results does not always retrieve the record you're after unless
you specify paging=false (or it's on the first page)
- Some entties use paging=false, others use skipPaging=true
Thanks
Alan
On Thu, Jun 18, 2015 at 1:07 PM, Lorill Crees wrote:
> Hi
Hi Morten,
These are the places where we're seeing inconsistencies:
- /api/sqlViews//execute POST: returns String - "SQL view created"
- /api/sqlViews//data GET: exception in tomcat logs returns HTML
error page (eg: if view has not been executed)
-
- /api/events POST: returns impor
Hi
We have started changing some of endpoints already, if you e.g. try to get
a invalid data-element /api/dataElements/abc123 you will see the new output
format (xml and json supported, json is default). I have not started
changing the import conflict format yet, and it probably will not be
change
Thanks Morten.
On a related note, have you defined how you will be changing the response
messages yet? We've written a rudimentary response message parser as part
of our app because we get quite inconsistent results from the various web
api calls. EG: some responses return "conflicts" whereas othe
Hi
No, this is not currently supported. We might support it in a future
release, as we are changing our responses messages a bit in 2.20/2.21.
--
Morten
On Wed, Jun 17, 2015 at 5:58 AM, Lorill Crees wrote:
> Hi All,
>
> Is it possible to receive messages back from the web api in other
> langua
Hi All,
Is it possible to receive messages back from the web api in other
languages? Specifically if there are import conflicts we would like to give
these messages back to the user in their preferred language.
Thanks,
Lorill
___
Mailing list: https://
10 matches
Mail list logo
