Hi team,
Does anyone know if a blueprint was ever made for cascading/nested selections? I was unable to find it through a quick search right now.
If not, I can add a blueprint on this (hopefully there might be some room in 2.25)
Knut
···
On 7 December 2015 at 18:51, Markus Bekken markus.bekken@gmail.com wrote:
Dear David,
program rules for filtering/hiding option set values is not yet supported. That said we have seen a few use cases for this, now including yours. We plan to include support in the program rules for hiding options in an option set, pushing for 2.22 here.
In 2.21 you would have to make separate dataelements with separate option sets to acheive something similar. If you make separate data elements you can hide the ones that is not relevant based on pre-selectors, provided that each data element has an option set that includes only the option values that is relevant for the values in the pre-selectors.
Best regards,
Markus
On Mon, Dec 7, 2015 at 2:37 PM, Lars Helge Øverland larshelge@gmail.com wrote:
Halla kunne du svart på denne? Noen planer om linking av option sets for program rules…?
---------- Forwarded message ----------
From: David Hagan david.hagan@sagehagan.com
Date: Fri, Dec 4, 2015 at 6:13 AM
Subject: [Dhis2-users] Filtered Drop-downs on Tracker/Event Forms
To: DHIS dhis2-users@lists.launchpad.netHi,
A quick question on whether the standard out-of-the-box capability of DHIS2 allows one to filter a drop-down based on a previous selection (I would assume something like this would normally be implemented via a rule - ideally the skip-logic rule area).
For larger lists (e.g. diagnosis codes) I’m sure this must have been considered previously, but can’t find any mentions in the mail list, and can’t see how this can be implemented (using standard capability currently offered).
We are looking at the scenario of implementing a simplistic version of ICPC for field encounters … and there are 2 quick potential ‘pre-selectors’ that reduce final selection from hundreds to less than 30 items, greatly speeding up the data capture process for the end-user.
(Note we are looking at using the latest v2.21 Android Tracker App as the basis for serving this encounter form)
Cheers
David
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
–
Knut Staring
Dept. of Informatics, University of Oslo
Norway: +4791880522
Skype: knutstar