Hi Knut
I'm not sure exactly why that is happening, but if you are not using push
analysis, you can probably just drop the content of that table and it
should work (delete from pushanalysis).
If you are using it, try to set a valid integer value to it...
--
Morten Olav Hansen
Senior Engineer,
Does anyone have an idea on how to deal with these errors?
* INFO 2018-04-12 18:04:25,125 Executing startup routine [5 of 18,
runlevel 4]: ReportingIdentityPopulator (DefaultStartupRoutineExecutor.java
[Thread-2])
* INFO 2018-04-12 18:04:25,239 Executing startup routine [6 of 18,
runlevel 5]:
Hi Henning,
Sorry if I was not clear. What's not working was in event capture there's a
list of events already recorded. Adjacent to the show/hide button, there's
a download list button.
While the option for JSON and XML are working fine, the CSV option doesn't
work.
I've confirmed the same is
Thanks for the clarification, Morten.
Regarding the last question, no, there was no feedback when it failed, only the
hibernate-exception in the tomcat log. In the GUI, it was just stuck
indefinitely on "importing X objects…"
This was 2.27 btw.
Olav
12. apr. 2018 kl. 11:09 skrev Morten Olav
the below expression should work, yes :)
> 12. apr. 2018 kl. 11:13 skrev Jane Greig :
>
> So numeric would solve it for us?
> That is, if the code for the option we want is numeric = 2 in all 3 data
> elements, this should work?:
>
Hi,
What is not working? Can you include some more information - the url, payload,
exception?
Regards,
Henning Håkonsen
henn...@dhis2.org
> On 12 Apr 2018, at 11:19, Seid Hussein wrote:
>
> Hi all,
>
> I was testing 2.29 and the download event list as CSV in Event
Hi all,
I was testing 2.29 and the download event list as CSV in Event capture is
not working while XML and JSON are working fine. I have tested this on the
demo site as well.
Is this intentional? Is support for CSV droppped or is it a bug?
--
Seid,
So numeric would solve it for us?
That is, if the code for the option we want is numeric = 2 in all 3 data
elements, this should work?:
d2:condition('#{qaDVwQUHD0j.g4bPEQ4a7WM} == 2 ',1,0) +
d2:condition('#{qaDVwQUHD0j.FFpJ2FZU7rJ} == 2 ',1,0) +
d2:condition('#{qaDVwQUHD0j.dLKjtfo7GD3} == 2
HI Markus
Thanks for your response. I thought that might be the problem. Unfortunately
our use case is more complex than my example, so the filter workaround doesn't
help - we want the indicator to return a combined set of conditions. For
example, 3 data elements all with the same option set
Ok, I understand - was fearing this could be the reason :) The codes need to be
quoted when they are text-based, so the other short-term workaround I can think
of is to use numeric codes.
Markus
> 12. apr. 2018 kl. 11:06 skrev Jane Greig :
>
> HI Markus
> Thanks for
On Thu, Apr 12, 2018 at 1:54 PM, Olav Poppe wrote:
> Hi, I managed to solve the problem in the end. It was indeed caused by
> one single object being shared with a group I had not included in export…
>
Good
I’m still left with some questions though:
> - even with
Hi there Jane!
The problem with the below condition is that we are using single quotes inside
a single quoted statement. This is not supported at the moment.
Not really knowing enough about the use case, I venture into suggeting a
possible workaround: If you are able to use the condition below
Hi, I managed to solve the problem in the end. It was indeed caused by one
single object being shared with a group I had not included in export…
I’m still left with some questions though:
- even with skipValidation=true the import failed until I identified the extra
user group - is that a bug,
13 matches
Mail list logo