I think there are cases where you want to include data elements/indicators, and cases where you would not want to include it - so for me, the ideal would be that there was a choice.
A challenge at least as of 2.24 (was unable to test in 2.25, import failed) is that if you import a favourite into a database where the data items are missing, you can’t manually modify/add those in DV/PT/GIS favorite because the favorite won’t open. So for now, you really need the data element/indicators to be included if importing these in a database where the data items are different. If it had been possible to edit imported favorites with missing data dimension, not including the data items would have been good solution in many cases. With 2.25, you could even have used the "favorite description" to guide people in configuring the imported favorites to their database. So an additional feature request would be the ability modify "ill-defined" favorites. Olav > 29. okt. 2016 kl. 23.40 skrev Lars Helge Øverland <l...@dhis2.org>: > > How far should the dependencies go? Stop at favorites (pivot tables, maps > etc), or include data elements/categories/indicators etc?
_______________________________________________ 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
