Generated actual content constraints do not take into account empty observation values with existing attributes
When empty observation values are uploaded with some attribute values filled, such data points are not taken into account when generating actual content constraints, but must. In DE this issue leads to a result that when this actual content constraint will be applied to a data filter in the visualisation view, such code will be removed from the filters, but the data will still be shown in the table.
Example: Uploaded data to DF_NIS_KH_AGRI for Cambodia ASIKHM (observation values with attributes) and its region Kampot ASIKHM007 (empty observation values with attributes filled). As a result in the generated actual content constraint the REF_AREA is fixed only to ASIKHM.
http://nsi-reset-siscc.redpelicans.com/rest/dataflow/KH_NIS/DF_NIS_KH_AGRI/latest?references=all
When this actual content constraint is applied in DE filters, the "Reference area" filter disappeared from the filters (because it only knows about 1 value ASIKHM), but the data request correctly returns the observations for Kampot and they are shown in the table.