← Back to team overview

dhis2-devs team mailing list archive

Re: [Bug 1471816] [NEW] constant_does_not_exist Message in Data Integrity Report

 

DHIS2,

Any word on this?

[image: Inline image 1]

I pulled this from the SL Demo.

Timothy Harding
RPCV Vanuatu
Skype: hardingt@xxxxxxxxx
+1 (541) 632-6623

On Mon, Jul 6, 2015 at 7:01 AM, hardingt <hardingt@xxxxxxxxx> wrote:

> Public bug reported:
>
> Hello Devs,
>
> I was able to recreate this in SL stable demo server with the following
> steps:
>
> 1. Create a constant
> 2. Create an indicator that uses the constant
> 3. Run the Data Integrity report
>
> The Data Integrity report will report that constant_does_not_exist.
>
> My guess is that this is erroneous, but the message is confusing users,
> they think they have done something wrong with their indicator
> configuration.
>
> Additional Note:
>
> While testing this bug in the SL demo, I also noticed it produces a
> similar error for OUGs:
> org_unit_group_does_not_exist
>
> But the indicator works, and the web gui provides no indication that
> there is a problem when creating the indicator.
>
> ** Affects: dhis2
>      Importance: Undecided
>          Status: New
>
> ** Attachment added: "Snippit from the SL Stable Demo"
>
> https://bugs.launchpad.net/bugs/1471816/+attachment/4425090/+files/constant_does_not_exist.png
>
> --
> You received this bug notification because you are a member of DHIS 2
> developers, which is subscribed to DHIS.
> https://bugs.launchpad.net/bugs/1471816
>
> Title:
>   constant_does_not_exist Message in Data Integrity Report
>
> Status in DHIS 2:
>   New
>
> Bug description:
>   Hello Devs,
>
>   I was able to recreate this in SL stable demo server with the
>   following steps:
>
>   1. Create a constant
>   2. Create an indicator that uses the constant
>   3. Run the Data Integrity report
>
>   The Data Integrity report will report that constant_does_not_exist.
>
>   My guess is that this is erroneous, but the message is confusing
>   users, they think they have done something wrong with their indicator
>   configuration.
>
>   Additional Note:
>
>   While testing this bug in the SL demo, I also noticed it produces a
> similar error for OUGs:
>   org_unit_group_does_not_exist
>
>   But the indicator works, and the web gui provides no indication that
>   there is a problem when creating the indicator.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dhis2/+bug/1471816/+subscriptions
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>


** Attachment added: "image.png"
   https://bugs.launchpad.net/bugs/1471816/+attachment/4446050/+files/image.png

-- 
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1471816

Title:
  constant_does_not_exist Message in Data Integrity Report

Status in DHIS:
  New

Bug description:
  Hello Devs,

  I was able to recreate this in SL stable demo server with the
  following steps:

  1. Create a constant
  2. Create an indicator that uses the constant
  3. Run the Data Integrity report

  The Data Integrity report will report that constant_does_not_exist.

  My guess is that this is erroneous, but the message is confusing
  users, they think they have done something wrong with their indicator
  configuration.

  Additional Note:

  While testing this bug in the SL demo, I also noticed it produces a similar error for OUGs:
  org_unit_group_does_not_exist

  But the indicator works, and the web gui provides no indication that
  there is a problem when creating the indicator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhis2/+bug/1471816/+subscriptions


References