Version 2.16 vs 2.17 : assign a Dataset from the OU group and that reverberate to organizational units of this group

Hi Devs

With the vesion inferior at 2.17 DHIS2, we can assign a Dataset from the OU
group and that reverberate to organizational units of this group. It was
easy in the sense that we imported organization and we were bonding by
import units, it was perfect. But now with version 2.17, we do not have the
ability to assign a dataset to the OU group rather only to the OU. Now with
the ability to import, we still need to assign datasets units manually.
What work!

Regards

Carlos

Sorry, can you read the french version!

Avec les vesions inferieures à 2.17 de DHIS2, nous avions la possibilité
d'assigner un Dataset à partir du groupe d'unité d'organisation et cela se
réperccutait aux unités d'organisation de ce groupe. Cela était facile dans
le sens que nous importions des unités d'organisation et nous les groupions
par importation, c'était parfait. Mais actuellement, avec la version 2.17,
nous n'avons pas la possibilité d'assigner un dataset au groupe d'unité
d'organisation plutot seulement à l'unité d'organisation. Or avec la
possibilité d'importation, nous devons encore assigner les datasets aux
unités manuellement. Quel travail!

Hi Carlos,

With an award wining nominated post doctoral multidimensional actor network theory based empirical use case research in Applied Molecular Biological Informatics in association with Applied Meta Nuclear Physics comes with outcome that assigning data set to molecular organization unit group some times comes with very big and fettle data security issue in its vector atomic models design specially when user use to migrate at-least one serialized molecular organization unit from assigned molecular organization unit group with specifically assigned dataset to other remote molecular organization unit group environment by other scheduled static molecular organization units of previously assigned molecular organization unit group with special privileges on memory loading and data integrity checks operations.

One probable cause should be difference in type of molecular organization unit with difference in type of molecular organization unit group with rare to denser or from denser to rare remote migration environment causing up in inflation
in physical deficits in property value assignment.

Other probable cause could be highly reactive previously assigned molecular organization units with molecular organization unit group some times starts playing adversarial and viral role to remotely migrant molecular organization unit specially on its developed uninterrupted power supply to central nervous system causing still dominant role by previously assigned molecular organization unit group.

So, if a subsequent previously assigned molecular organization unit group plays adverse, viral, confusing and influential role to destination molecular organization unit group for a molecule organization unit migration in-spite of getting successful migration without dataset assignment, than why we should assign any dataset to any static experimental molecular organization unit group specially when previously assigned static molecular organization unit group starts playing intentional, dominant and influancial role on migrant dynamic quantum molecular organization unit, more specially when static molecular organization unit group does’t have any declarative functionality nor had property of data compression privileges which is by default all the time available in migrant dynamic molecular organization unit ?

Regards

Brajesh Murari

···

2015-03-02 15:52 GMT+05:30 Carlos Nyembwe nyembwe@gmail.com:


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Hi Devs

With the vesion inferior at 2.17 DHIS2, we can assign a Dataset from the OU group and that reverberate to organizational units of this group. It was easy in the sense that we imported organization and we were bonding by import units, it was perfect. But now with version 2.17, we do not have the ability to assign a dataset to the OU group rather only to the OU. Now with the ability to import, we still need to assign datasets units manually. What work!

Regards

Carlos

Sorry, can you read the french version!

Avec les vesions inferieures à 2.17 de DHIS2, nous avions la possibilité d’assigner un Dataset à partir du groupe d’unité d’organisation et cela se réperccutait aux unités d’organisation de ce groupe. Cela était facile dans le sens que nous importions des unités d’organisation et nous les groupions par importation, c’était parfait. Mais actuellement, avec la version 2.17, nous n’avons pas la possibilité d’assigner un dataset au groupe d’unité d’organisation plutot seulement à l’unité d’organisation. Or avec la possibilité d’importation, nous devons encore assigner les datasets aux unités manuellement. Quel travail!

Hi Carlos,

You can still add OU groups to data sets by using the group function when assigning the OU. If you click on the data set and select Assign to Organisation Unit, you have an option to assign by level or by group. You can choose to assign OU groups this way.

Hope that helps.

Regards,

Busoye

···

2015-03-02 15:52 GMT+05:30 Carlos Nyembwe nyembwe@gmail.com:


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Hi Devs

With the vesion inferior at 2.17 DHIS2, we can assign a Dataset from the OU group and that reverberate to organizational units of this group. It was easy in the sense that we imported organization and we were bonding by import units, it was perfect. But now with version 2.17, we do not have the ability to assign a dataset to the OU group rather only to the OU. Now with the ability to import, we still need to assign datasets units manually. What work!

Regards

Carlos

Sorry, can you read the french version!

Avec les vesions inferieures à 2.17 de DHIS2, nous avions la possibilité d’assigner un Dataset à partir du groupe d’unité d’organisation et cela se réperccutait aux unités d’organisation de ce groupe. Cela était facile dans le sens que nous importions des unités d’organisation et nous les groupions par importation, c’était parfait. Mais actuellement, avec la version 2.17, nous n’avons pas la possibilité d’assigner un dataset au groupe d’unité d’organisation plutot seulement à l’unité d’organisation. Or avec la possibilité d’importation, nous devons encore assigner les datasets aux unités manuellement. Quel travail!