Hi Travis,
Are u trying to import the coordinates to an existing org unit tree in
DHIS2? In that case you need to match the gml against unique value for each
org unit eg: name, code.
On Fri, Jan 13, 2017 at 10:18 PM, Travis Fried wrote:
> Greetings,
>
>
> I'm a new user to DHIS2, so I'm unsure
Hi Stephen,
You may need to pull the comments directly from the database (data value table)
via an sql view. Alternatively, marking the star sign after “Comment” will make
the entry visible in the follow analysis function within the Data Quality App
(This however does not include the comments bu
Sorry if I misunderstood, do you mean this?
1. {trackedEntityInstance: "QtFqVt2NZ6l", program: "i7udy8Ca0SQ",
status: "ACTIVE",…}
1. coordinate:{latitude: -2.96624, longitude: 115.2057}
1. latitude:-2.96624
2. longitude:115.2057
2. enrollmentDate:"2015-10-01"
Hi Seth,
If the data type is numeric, there should not be any quotes. See example in
27.4.1.3. About filters: 27.4.1. About program indicators
It seems you already tried this though, perhaps I can have a look in your
instance if you send me login info privately.
Markus
> 13. jan. 2017 kl. 10.
Hello Marcus,
Thank you very much, I have the options in the right format as you have said,
now the problem is,
do I use quotation marks for the numerical codes i.e.
#{yUVXpYVeY6I.Z8W89lDV4IL} ==‘1'
(Demographics, Admission and Treatment.Gender ==‘1')
or just
#{yUVXpYVeY6I.Z8W89lDV4IL}
Hi,
Both event capture and tracker capture are using the same thing:
1. use data capture orgunits tree in the left hand column
2. use data output and analysis organisation units tree for data
elements of type 'ORGANISATION_UNIT'.
What kind of configuration would you like to have?
A sim
Hi there Seth,
the option set codes only need to be unique within each option set.
One option set can be
Male - 1
Female - 2
And another can be
Yes - 1
No - 0
But when your option set is
Male - 1
Female - 1
...then the two options will always be seen as "1" when analyzing the data.
Markus
7 matches
Mail list logo
