← Back to team overview

dhis2-devs team mailing list archive

Re: [Bug 785804] [NEW] Field check utility not working

 

I cannot reproduce this bug. What was the version of the snapshot you
were using and what is your current version?

On Fri, May 20, 2011 at 4:27 PM, Ifeanyi Okoye
<785804@xxxxxxxxxxxxxxxxxx> wrote:
> Public bug reported:
>
> I just upgraded to DHIS 2.2 from the 2.2 snapshot.
> The utility in DHIS 2 that checks that there are no duplicate field names or short codes etc. etc. is not working. You do not find out that there is an existing field name in the database until you try to save and then get an error. Was it disabled or just a bug?
> Thanks
>
> ** Affects: dhis2
>     Importance: Undecided
>         Status: New
>
> --
> You received this bug notification because you are a member of DHIS 2
> India Developers, which is subscribed to DHIS.
> https://bugs.launchpad.net/bugs/785804
>
> Title:
>  Field check utility not working
>
> Status in DHIS 2 - District Health Information Software:
>  New
>
> Bug description:
>  I just upgraded to DHIS 2.2 from the 2.2 snapshot.
>  The utility in DHIS 2 that checks that there are no duplicate field names or short codes etc. etc. is not working. You do not find out that there is an existing field name in the database until you try to save and then get an error. Was it disabled or just a bug?
>  Thanks
>


-- 
Jason P. Pickering
email: jason.p.pickering@xxxxxxxxx
tel:+260974901293

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

Title:
  Field check utility not working

Status in DHIS 2 - District Health Information Software:
  New

Bug description:
  I just upgraded to DHIS 2.2 from the 2.2 snapshot.
  The utility in DHIS 2 that checks that there are no duplicate field names or short codes etc. etc. is not working. You do not find out that there is an existing field name in the database until you try to save and then get an error. Was it disabled or just a bug?
  Thanks


Follow ups

References