Dear Lars
We also required detailed metadata export with dependency from where can
select a subset (not all the organisationunits, dataelements etc) as Knut
says. Without that we will be in deep water. We already have lots of issues
with metadata.
Regards
Hannan
On Sat, Oct 29, 2016 at 11:56
I am also supporting Olav; We are also badly requires "dashboard with
dependencies" export. Also if there is any mechanism to synchronize
dashboard, with provision to active/deactivate the option.
Regards
On Sun, Oct 30, 2016 at 1:25 AM, Olav Poppe wrote:
> Hi, I would be
That sounds like a good idea.
How far should the dependencies go? Stop at favorites (pivot tables, maps
etc), or include data elements/categories/indicators etc?
On Sat, Oct 29, 2016 at 3:25 PM, Olav Poppe wrote:
> Hi, I would be interested in a "dashboard with
A nice feature with the detailed one was that you could select a subset
(not all the organisationunits, dataelements etc).
On Sat, Oct 29, 2016 at 5:07 PM, Lars Helge Øverland wrote:
>
> Hi Nick,
>
> if you have specific needs let us know and we can consider including new
>
Hi Nick,
if you have specific needs let us know and we can consider including new
objects here.
As Morten said, the previous detailed metadata export was too error prone
as one would typically forget important parts when exporting things like
categories and data sets.
regards,
Lars
On
Absolom,
Kindly check the hibernate.properties or dhis.conf file again. It is
responsible to point DHIS2 to the right database.
On 10/27/16, Absolom MURAMIRA wrote:
> Dear All,
> I am setting up DHIS2 to run on Ubuntu 16.04 server and PostgreSQL database
> but after setting
Hi Nick and Morten,
I'm think I'm still seeing this functionality on the play.dhis2.org/demo
instance - this is 2.25 no?
https://play.dhis2.org/demo/dhis-web-importexport/dxf2MetaDataExport.action
I was hoping to use the import meta-data functionality to create a large
number of org units in my
7 matches
Mail list logo