I fixed it,but will detail the problem when I get back, as I still do not
understand what it was, but it was related to an option set assigned to a
data element.
On Fri, Sep 25, 2015 at 1:34 PM, Halvdan Grelland
wrote:
> Agree with Mark. Check wether you're supposed to get two or three
> option
Agree with Mark. Check wether you're supposed to get two or three
optionSets.
2015-09-25 13:20 GMT+02:00 Mark Polak :
> Yes it should be an option set just like the others, something like the
> others "Thfz8125uPk-USfPOPAeN16":{"uid":"eUZ79clX7y1","v":1}"
>
> However, perhaps there shouldn't be a
Yes it should be an option set just like the others, something like the
others "Thfz8125uPk-USfPOPAeN16":{"uid":"eUZ79clX7y1","v":1}"
However, perhaps there shouldn't be anything there and there is just a
comma too much, because the object in between is actually "null" or w/e.
But i'm not really s
Yeah, i see it but not sure what that object should be. Is this related to
option sets?
On Fri, Sep 25, 2015 at 12:57 PM, Mark Polak wrote:
> "optionSets": {
> "Thfz8125uPk-USfPOPAeN16":{"uid":"eUZ79clX7y1","v":1} *,
> ,*"f1R88WLGXvs-USfPOPAeN16":{"uid":"M2dZRqmn8A7","v":1}
> },
>
> "indicator
"optionSets": {
"Thfz8125uPk-USfPOPAeN16":{"uid":"eUZ79clX7y1","v":1} *,
,*"f1R88WLGXvs-USfPOPAeN16":{"uid":"M2dZRqmn8A7","v":1}
},
"indicatorFormulas": {
Between those (red) commas there should be another object. As it currently
is that is not a valid JSON structure.
On Fri, Sep 25, 2015 at 12
>From the file, it looks like this
"optionSets": {
"Thfz8125uPk-USfPOPAeN16":{"uid":"eUZ79clX7y1","v":1} ,
,"f1R88WLGXvs-USfPOPAeN16":{"uid":"M2dZRqmn8A7","v":1} },
"indicatorFormulas": {
Any ideas what might be causing that?
On Fri, Sep 25, 2015 at 12:01 PM, Jason Pickering <
jason.p.picke
Can you give a bit more?
--
Morten
On Fri, Sep 25, 2015 at 5:01 PM, Jason Pickering <
jason.p.picker...@gmail.com> wrote:
> I got this
>
> [Error: Parse error on line 11:
> ...Z79clX7y1","v":1} , ,"f1R88WLGXvs-USfPOP
> ---^
> Expecting 'STRING', got ',']
>
> On Fri, Sep 25, 2
I got this
[Error: Parse error on line 11:
...Z79clX7y1","v":1} , ,"f1R88WLGXvs-USfPOP
---^
Expecting 'STRING', got ',']
On Fri, Sep 25, 2015 at 11:53 AM, Morten Olav Hansen
wrote:
> Try to manually run the getMedaData.action in data-entry, and then take
> that output to jso
Try to manually run the getMedaData.action in data-entry, and then take
that output to jsonlint.com
Unexpected token u, means something was undefined..
--
Morten
On Fri, Sep 25, 2015 at 4:49 PM, Jason Pickering <
jason.p.picker...@gmail.com> wrote:
> We are seeing an error in data entry, which
We are seeing an error in data entry, which is preventing all data entry,so
it is pretty critical.
Uncaught SyntaxError: Unexpected token u
Unknown revision of 2.18. I suspect it is a meta-data problem, but not
really sure how to pinpoint it?
Any ideas?
Regards,
Jason
--
Jason P. Pickering
10 matches
Mail list logo