dhis2-users team mailing list archive

[Lars Helge Øverland <lars@xxxxxxxxx>]

Hi Jhansi,

this should be considered expected behavior. The link between options (in
option sets) and data / events in "soft" in the sense that it is based on
text (not relational constraints in the database). This means that there is
nothing stopping you from editing existing option codes if you do it
directly in the database. Deleting all data / events which are linked to an
option when the option is deleted is too drastic in my mind - better to
leave this up to the implementor.

best regards,

Lars




On Mon, May 16, 2016 at 11:24 AM, jhansi <jhansirk@xxxxxxxxxxxxxxxx> wrote:

> Hello,
>
> We have configured event reports to display the number of occurrences of a
> particular option for a given period and orgunit in the event data. In a
> couple of these reports, we are noticing option code instead of option
> name.
>
> We further investigated into this and found that this issue is happening
> because of deleting an existing option which has already been used in the
> event data entry. All the events which had previously used this option now
> display the option code.
>
> When an option is deleted (which has been used in the event data entry),
> DHIS is not completely removing its trace from the events data and reports.
> Has someone faced this issue before or has any suggestions/fix for this?
>
> Thanks,
> Hari/Jhansi
>



-- 
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
lars@xxxxxxxxx
http://www.dhis2.org <https://www.dhis2.org/>