define weekly

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.

···

Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason

···

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.

···

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

the problem is that the date of December 28 2015 to January 3 2016 is considered both 2015W53 and 2016W1 in dhis2.

···

2016-01-04 15:55 GMT+00:00 papa alioune Sokhna sokhnapapa@gmail.com:

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

Hi Papa,

I am able to reproduce this. It is clearly a bug.

I think you should used 2015W53 for this period, but there could be a major problem if the weeks for 2016 are off.

Jan/Lars, could you comment?

Regards,

Jason

···

On Mon, Jan 4, 2016 at 4:55 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Hi Jason,
If that information can be useful I noticed that the dhis our Ministry of Health does not have this problem and they have version 2.15.

···

2016-01-04 16:16 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,

I am able to reproduce this. It is clearly a bug.

I think you should used 2015W53 for this period, but there could be a major problem if the weeks for 2016 are off.

Jan/Lars, could you comment?

Regards,

Jason

On Mon, Jan 4, 2016 at 4:55 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

Hi Jason,

we just started receiving emails from users reporting the same problem.

Will follow the evolution.

Cheers

···

On 4 January 2016 at 18:05, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
If that information can be useful I noticed that the dhis our Ministry of Health does not have this problem and they have version 2.15.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

2016-01-04 16:16 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,

I am able to reproduce this. It is clearly a bug.

I think you should used 2015W53 for this period, but there could be a major problem if the weeks for 2016 are off.

Jan/Lars, could you comment?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:55 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Hi Marta and Papa,
We identified the bug (we think) and Morten has updated the code with a fix, and backported it back to version 2.17. New builds are available here http://ci.dhis2.org/ .

I have tested this on one instance, and it seems to work OK now. Let us know if it works for you.

Best regards,

Jason

···

On Tue, Jan 5, 2016 at 5:14 PM, Marta Vila martavila@gmail.com wrote:

Hi Jason,

we just started receiving emails from users reporting the same problem.

Will follow the evolution.

Cheers

On 4 January 2016 at 18:05, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
If that information can be useful I noticed that the dhis our Ministry of Health does not have this problem and they have version 2.15.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

2016-01-04 16:16 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,

I am able to reproduce this. It is clearly a bug.

I think you should used 2015W53 for this period, but there could be a major problem if the weeks for 2016 are off.

Jan/Lars, could you comment?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:55 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Thanks Jason

···

On Thu, Jan 7, 2016 at 2:21 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

Hi Marta and Papa,
We identified the bug (we think) and Morten has updated the code with a fix, and backported it back to version 2.17. New builds are available here http://ci.dhis2.org/ .

I have tested this on one instance, and it seems to work OK now. Let us know if it works for you.

Best regards,

Jason


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

On Tue, Jan 5, 2016 at 5:14 PM, Marta Vila martavila@gmail.com wrote:

Hi Jason,

we just started receiving emails from users reporting the same problem.

Will follow the evolution.

Cheers


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

On 4 January 2016 at 18:05, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
If that information can be useful I noticed that the dhis our Ministry of Health does not have this problem and they have version 2.15.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

2016-01-04 16:16 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,

I am able to reproduce this. It is clearly a bug.

I think you should used 2015W53 for this period, but there could be a major problem if the weeks for 2016 are off.

Jan/Lars, could you comment?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:55 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Hi Jason,
As I understand it we must return to the version 2.17 and there is no sql script to run before returning to this version?

···

2016-01-07 13:25 GMT+00:00 Jan Henrik Øverland janhenrik.overland@gmail.com:

Thanks Jason


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

On Thu, Jan 7, 2016 at 2:21 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

Hi Marta and Papa,
We identified the bug (we think) and Morten has updated the code with a fix, and backported it back to version 2.17. New builds are available here http://ci.dhis2.org/ .

I have tested this on one instance, and it seems to work OK now. Let us know if it works for you.

Best regards,

Jason


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

On Tue, Jan 5, 2016 at 5:14 PM, Marta Vila martavila@gmail.com wrote:

Hi Jason,

we just started receiving emails from users reporting the same problem.

Will follow the evolution.

Cheers


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

On 4 January 2016 at 18:05, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
If that information can be useful I noticed that the dhis our Ministry of Health does not have this problem and they have version 2.15.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

2016-01-04 16:16 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,

I am able to reproduce this. It is clearly a bug.

I think you should used 2015W53 for this period, but there could be a major problem if the weeks for 2016 are off.

Jan/Lars, could you comment?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:55 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

The only thing you will need to do is to update you server with the latest build. For 2.17 it is available here.

http://ci.dhis2.org/job/dhis2-2.17/lastSuccessfulBuild/artifact/dhis-2/dhis-web/dhis-web-portal/target/dhis.war

Regards,

Jason

···

On Thu, Jan 7, 2016 at 3:37 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
As I understand it we must return to the version 2.17 and there is no sql script to run before returning to this version?

2016-01-07 13:25 GMT+00:00 Jan Henrik Øverland janhenrik.overland@gmail.com:

Thanks Jason


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Thu, Jan 7, 2016 at 2:21 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

Hi Marta and Papa,
We identified the bug (we think) and Morten has updated the code with a fix, and backported it back to version 2.17. New builds are available here http://ci.dhis2.org/ .

I have tested this on one instance, and it seems to work OK now. Let us know if it works for you.

Best regards,

Jason


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

On Tue, Jan 5, 2016 at 5:14 PM, Marta Vila martavila@gmail.com wrote:

Hi Jason,

we just started receiving emails from users reporting the same problem.

Will follow the evolution.

Cheers


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

On 4 January 2016 at 18:05, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
If that information can be useful I noticed that the dhis our Ministry of Health does not have this problem and they have version 2.15.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

2016-01-04 16:16 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,

I am able to reproduce this. It is clearly a bug.

I think you should used 2015W53 for this period, but there could be a major problem if the weeks for 2016 are off.

Jan/Lars, could you comment?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:55 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Hello Jason,

thanks. We will update all offline servers us well as soon as we can.
Could you tell me, with the fix, what happens with the former W1?

The period is just removed and weeks are re-numbered? It is considered in the fix that it could be data already in that week or should we take care of removing it before updating ?

Thanks!

···

On 7 January 2016 at 17:09, Jason Pickering jason.p.pickering@gmail.com wrote:

The only thing you will need to do is to update you server with the latest build. For 2.17 it is available here.

http://ci.dhis2.org/job/dhis2-2.17/lastSuccessfulBuild/artifact/dhis-2/dhis-web/dhis-web-portal/target/dhis.war

Regards,

Jason


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

On Thu, Jan 7, 2016 at 3:37 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
As I understand it we must return to the version 2.17 and there is no sql script to run before returning to this version?


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

2016-01-07 13:25 GMT+00:00 Jan Henrik Øverland janhenrik.overland@gmail.com:

Thanks Jason


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Thu, Jan 7, 2016 at 2:21 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

Hi Marta and Papa,
We identified the bug (we think) and Morten has updated the code with a fix, and backported it back to version 2.17. New builds are available here http://ci.dhis2.org/ .

I have tested this on one instance, and it seems to work OK now. Let us know if it works for you.

Best regards,

Jason


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

On Tue, Jan 5, 2016 at 5:14 PM, Marta Vila martavila@gmail.com wrote:

Hi Jason,

we just started receiving emails from users reporting the same problem.

Will follow the evolution.

Cheers


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

On 4 January 2016 at 18:05, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
If that information can be useful I noticed that the dhis our Ministry of Health does not have this problem and they have version 2.15.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

2016-01-04 16:16 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,

I am able to reproduce this. It is clearly a bug.

I think you should used 2015W53 for this period, but there could be a major problem if the weeks for 2016 are off.

Jan/Lars, could you comment?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:55 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Hi Marta,

The bug seems to be only a display issue in the DHIS web application. The Javascript file in question is responsible for calculating the date ranges for weekly periods (i.e. 2015W52, 2015W53 etc.) and displaying them in the UI. When sending requests to the backend however, the web application seems to ignore the data range and only sends the period as 2016W1 etc.

As far as repercussions for your existing entered data, the data is being stored against the correct dates in the backend. So any data that has already been entered for 2016W1 is stored in the database against 2016/01/04 - 2016/01/10. The only thing you may want to consider is if any of your users accidentally entered data for 2016W1 thinking it was 2015/12/28 - 2016/01/03.

@Jason, Morten - can you please confirm the above?

Cheers,

···

-doh

On Thu, Jan 7, 2016 at 11:46 PM, Marta Vila martavila@gmail.com wrote:

Hello Jason,

thanks. We will update all offline servers us well as soon as we can.
Could you tell me, with the fix, what happens with the former W1?

The period is just removed and weeks are re-numbered? It is considered in the fix that it could be data already in that week or should we take care of removing it before updating ?

Thanks!


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

On 7 January 2016 at 17:09, Jason Pickering jason.p.pickering@gmail.com wrote:

The only thing you will need to do is to update you server with the latest build. For 2.17 it is available here.

http://ci.dhis2.org/job/dhis2-2.17/lastSuccessfulBuild/artifact/dhis-2/dhis-web/dhis-web-portal/target/dhis.war

Regards,

Jason


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

On Thu, Jan 7, 2016 at 3:37 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
As I understand it we must return to the version 2.17 and there is no sql script to run before returning to this version?


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

2016-01-07 13:25 GMT+00:00 Jan Henrik Øverland janhenrik.overland@gmail.com:

Thanks Jason


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Thu, Jan 7, 2016 at 2:21 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

Hi Marta and Papa,
We identified the bug (we think) and Morten has updated the code with a fix, and backported it back to version 2.17. New builds are available here http://ci.dhis2.org/ .

I have tested this on one instance, and it seems to work OK now. Let us know if it works for you.

Best regards,

Jason


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

On Tue, Jan 5, 2016 at 5:14 PM, Marta Vila martavila@gmail.com wrote:

Hi Jason,

we just started receiving emails from users reporting the same problem.

Will follow the evolution.

Cheers


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

On 4 January 2016 at 18:05, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
If that information can be useful I noticed that the dhis our Ministry of Health does not have this problem and they have version 2.15.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

2016-01-04 16:16 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,

I am able to reproduce this. It is clearly a bug.

I think you should used 2015W53 for this period, but there could be a major problem if the weeks for 2016 are off.

Jan/Lars, could you comment?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:55 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Hi Jason, Morten,

We took a look at the code for the fix:

var startDate = this.calendar.newDate(year, 1, 1);

// startDate.add(-(startDate.dayOfWeek() - 1), 'd'); // rewind to start of week, might cross year boundary

var day = startDate.dayOfWeek();

if( day == 0 ) // Sunday (0), forward to Monday

{

  startDate.add(1, 'd');

}

else if( day <= 4 ) // Monday - Thursday, rewind to Monday

{

  startDate.add(( ( day - 1 ) * -1 ), 'd');

}

else

// Friday - Saturday, forward to Monday

{

  startDate.add(8 - day, 'd');

} 

We could actually revert back to the previous code of rewinding back to the start of the week. The only change needed is to set the initial startDate to this.calendar.newDate(year, 1, 4) because as per the Wikipedia page for ISO weeks, the first ISO week of each year always contains January 4th.

Let us know if you’d like us to send through a patch.

Cheers,

···

On Thu, Jan 7, 2016 at 6:51 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

Hi Marta and Papa,
We identified the bug (we think) and Morten has updated the code with a fix, and backported it back to version 2.17. New builds are available here http://ci.dhis2.org/ .

I have tested this on one instance, and it seems to work OK now. Let us know if it works for you.

Best regards,

Jason


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

-doh

On Tue, Jan 5, 2016 at 5:14 PM, Marta Vila martavila@gmail.com wrote:

Hi Jason,

we just started receiving emails from users reporting the same problem.

Will follow the evolution.

Cheers


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

On 4 January 2016 at 18:05, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
If that information can be useful I noticed that the dhis our Ministry of Health does not have this problem and they have version 2.15.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

2016-01-04 16:16 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,

I am able to reproduce this. It is clearly a bug.

I think you should used 2015W53 for this period, but there could be a major problem if the weeks for 2016 are off.

Jan/Lars, could you comment?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:55 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Sure that sounds great. Please feel free to sent the patch to Morten.

Regards,

Jason

···

On Fri, Jan 8, 2016 at 2:53 PM, David Siang Fong Oh doh@thoughtworks.com wrote:

Hi Jason, Morten,

We took a look at the code for the fix:

var startDate = this.calendar.newDate(year, 1, 1);

// startDate.add(-(startDate.dayOfWeek() - 1), 'd'); // rewind to start of week, might cross year boundary
var day = startDate.dayOfWeek();
if( day == 0 ) // Sunday (0), forward to Monday
{
  startDate.add(1, 'd');
}
else if( day <= 4 ) // Monday - Thursday, rewind to Monday
{
  startDate.add(( ( day - 1 ) * -1 ), 'd');
}
else
// Friday - Saturday, forward to Monday
{
  startDate.add(8 - day, 'd');
} 

We could actually revert back to the previous code of rewinding back to the start of the week. The only change needed is to set the initial startDate to this.calendar.newDate(year, 1, 4) because as per the Wikipedia page for ISO weeks, the first ISO week of each year always contains January 4th.

Let us know if you’d like us to send through a patch.

Cheers,

-doh

On Thu, Jan 7, 2016 at 6:51 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

Hi Marta and Papa,
We identified the bug (we think) and Morten has updated the code with a fix, and backported it back to version 2.17. New builds are available here http://ci.dhis2.org/ .

I have tested this on one instance, and it seems to work OK now. Let us know if it works for you.

Best regards,

Jason


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

On Tue, Jan 5, 2016 at 5:14 PM, Marta Vila martavila@gmail.com wrote:

Hi Jason,

we just started receiving emails from users reporting the same problem.

Will follow the evolution.

Cheers


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

On 4 January 2016 at 18:05, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
If that information can be useful I noticed that the dhis our Ministry of Health does not have this problem and they have version 2.15.


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

2016-01-04 16:16 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,

I am able to reproduce this. It is clearly a bug.

I think you should used 2015W53 for this period, but there could be a major problem if the weeks for 2016 are off.

Jan/Lars, could you comment?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:55 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Dear all,

Any feedback on the previews bug?

did any one tried to fix it?

in Rwanda

We are also having the same issue on the weeks.

W1 - 2015-12-28 - 2016-01-03 is the same as W53 - 2015-12-28 - 2016-01-03

···

De : David Siang Fong Oh doh@thoughtworks.com
À : Marta Vila martavila@gmail.com
Cc : "dhis2-users@lists.launchpad.net" dhis2-users@lists.launchpad.net; DHIS 2 Developers list dhis2-devs@lists.launchpad.net
Envoyé le : Vendredi 8 janvier 2016 15h40
Objet : Re: [Dhis2-users] [Dhis2-devs] define weekly

Hi Marta,

The bug seems to be only a display issue in the DHIS web application. The Javascript file in question is responsible for calculating the date ranges for weekly periods (i.e. 2015W52, 2015W53 etc.) and displaying them in the UI. When sending requests to the backend however, the web application seems to ignore the data range and only sends the period as 2016W1 etc.

As far as repercussions for your existing entered data, the data is being stored against the correct dates in the backend. So any data that has already been entered for 2016W1 is stored in the database against 2016/01/04 - 2016/01/10. The only thing you may want to consider is if any of your users accidentally entered data for 2016W1 thinking it was 2015/12/28 - 2016/01/03.

@Jason, Morten - can you please confirm the above?

Cheers,

-doh

On Thu, Jan 7, 2016 at 11:46 PM, Marta Vila martavila@gmail.com wrote:

Hello Jason,

thanks. We will update all offline servers us well as soon as we can.
Could you tell me, with the fix, what happens with the former W1?

The period is just removed and weeks are re-numbered? It is considered in the fix that it could be data already in that week or should we take care of removing it before updating ?

Thanks!

On 7 January 2016 at 17:09, Jason Pickering jason.p.pickering@gmail.com wrote:

The only thing you will need to do is to update you server with the latest build. For 2.17 it is available here.

http://ci.dhis2.org/job/dhis2-2.17/lastSuccessfulBuild/artifact/dhis-2/dhis-web/dhis-web-portal/target/dhis.war

Regards,

Jason

On Thu, Jan 7, 2016 at 3:37 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
As I understand it we must return to the version 2.17 and there is no sql script to run before returning to this version?

2016-01-07 13:25 GMT+00:00 Jan Henrik Øverland janhenrik.overland@gmail.com:

Thanks Jason

On Thu, Jan 7, 2016 at 2:21 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

Hi Marta and Papa,
We identified the bug (we think) and Morten has updated the code with a fix, and backported it back to version 2.17. New builds are available here http://ci.dhis2.org/ .

I have tested this on one instance, and it seems to work OK now. Let us know if it works for you.

Best regards,

Jason

On Tue, Jan 5, 2016 at 5:14 PM, Marta Vila martavila@gmail.com wrote:

Hi Jason,

we just started receiving emails from users reporting the same problem.

Will follow the evolution.

Cheers

On 4 January 2016 at 18:05, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
If that information can be useful I noticed that the dhis our Ministry of Health does not have this problem and they have version 2.15.

2016-01-04 16:16 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,

I am able to reproduce this. It is clearly a bug.

I think you should used 2015W53 for this period, but there could be a major problem if the weeks for 2016 are off.

Jan/Lars, could you comment?

Regards,

Jason

On Mon, Jan 4, 2016 at 4:55 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


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


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

Hi Venuste,
As we have said a few times now on this thread, we have fixed the bug. You will need to update your server with the latest build for your version available here

http://ci.dhis2.org/

After that, be sure to clear your browser cache (and instruct users who are entering data to do the same).

Regards,

Jason

···

On Mon, Jan 11, 2016 at 3:49 PM, nsanzumuhire venuste vensanze@yahoo.fr wrote:

Dear all,

Any feedback on the previews bug?

did any one tried to fix it?

in Rwanda

We are also having the same issue on the weeks.

W1 - 2015-12-28 - 2016-01-03 is the same as W53 - 2015-12-28 - 2016-01-03


De : David Siang Fong Oh doh@thoughtworks.com
À : Marta Vila martavila@gmail.com
Cc :dhis2-users@lists.launchpad.netdhis2-users@lists.launchpad.net; DHIS 2 Developers list dhis2-devs@lists.launchpad.net
Envoyé le : Vendredi 8 janvier 2016 15h40
Objet : Re: [Dhis2-users] [Dhis2-devs] define weekly

Hi Marta,

The bug seems to be only a display issue in the DHIS web application. The Javascript file in question is responsible for calculating the date ranges for weekly periods (i.e. 2015W52, 2015W53 etc.) and displaying them in the UI. When sending requests to the backend however, the web application seems to ignore the data range and only sends the period as 2016W1 etc.

As far as repercussions for your existing entered data, the data is being stored against the correct dates in the backend. So any data that has already been entered for 2016W1 is stored in the database against 2016/01/04 - 2016/01/10. The only thing you may want to consider is if any of your users accidentally entered data for 2016W1 thinking it was 2015/12/28 - 2016/01/03.

@Jason, Morten - can you please confirm the above?

Cheers,

-doh

On Thu, Jan 7, 2016 at 11:46 PM, Marta Vila martavila@gmail.com wrote:

Hello Jason,

thanks. We will update all offline servers us well as soon as we can.
Could you tell me, with the fix, what happens with the former W1?

The period is just removed and weeks are re-numbered? It is considered in the fix that it could be data already in that week or should we take care of removing it before updating ?

Thanks!

On 7 January 2016 at 17:09, Jason Pickering jason.p.pickering@gmail.com wrote:

The only thing you will need to do is to update you server with the latest build. For 2.17 it is available here.

http://ci.dhis2.org/job/dhis2-2.17/lastSuccessfulBuild/artifact/dhis-2/dhis-web/dhis-web-portal/target/dhis.war

Regards,

Jason

On Thu, Jan 7, 2016 at 3:37 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
As I understand it we must return to the version 2.17 and there is no sql script to run before returning to this version?

2016-01-07 13:25 GMT+00:00 Jan Henrik Øverland janhenrik.overland@gmail.com:

Thanks Jason

On Thu, Jan 7, 2016 at 2:21 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

Hi Marta and Papa,
We identified the bug (we think) and Morten has updated the code with a fix, and backported it back to version 2.17. New builds are available here http://ci.dhis2.org/ .

I have tested this on one instance, and it seems to work OK now. Let us know if it works for you.

Best regards,

Jason

On Tue, Jan 5, 2016 at 5:14 PM, Marta Vila martavila@gmail.com wrote:

Hi Jason,

we just started receiving emails from users reporting the same problem.

Will follow the evolution.

Cheers

On 4 January 2016 at 18:05, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
If that information can be useful I noticed that the dhis our Ministry of Health does not have this problem and they have version 2.15.

2016-01-04 16:16 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,

I am able to reproduce this. It is clearly a bug.

I think you should used 2015W53 for this period, but there could be a major problem if the weeks for 2016 are off.

Jan/Lars, could you comment?

Regards,

Jason

On Mon, Jan 4, 2016 at 4:55 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


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


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


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Hi David, Jason,

thanks for the explanation and for sharing the information about the fix. Itr is very useful for us to send the fix only.

Venuste, we will share the feedback if we find any issue.

Thank you all,

Marta

···

On 11 January 2016 at 16:35, Jason Pickering jason.p.pickering@gmail.com wrote:

Hi Venuste,
As we have said a few times now on this thread, we have fixed the bug. You will need to update your server with the latest build for your version available here

http://ci.dhis2.org/

After that, be sure to clear your browser cache (and instruct users who are entering data to do the same).

Regards,

Jason

On Mon, Jan 11, 2016 at 3:49 PM, nsanzumuhire venuste vensanze@yahoo.fr wrote:

Dear all,

Any feedback on the previews bug?

did any one tried to fix it?

in Rwanda

We are also having the same issue on the weeks.

W1 - 2015-12-28 - 2016-01-03 is the same as W53 - 2015-12-28 - 2016-01-03


De : David Siang Fong Oh doh@thoughtworks.com
À : Marta Vila martavila@gmail.com
Cc : "dhis2-users@lists.launchpad.net" dhis2-users@lists.launchpad.net; DHIS 2 Developers list dhis2-devs@lists.launchpad.net
Envoyé le : Vendredi 8 janvier 2016 15h40
Objet : Re: [Dhis2-users] [Dhis2-devs] define weekly

Hi Marta,

The bug seems to be only a display issue in the DHIS web application. The Javascript file in question is responsible for calculating the date ranges for weekly periods (i.e. 2015W52, 2015W53 etc.) and displaying them in the UI. When sending requests to the backend however, the web application seems to ignore the data range and only sends the period as 2016W1 etc.

As far as repercussions for your existing entered data, the data is being stored against the correct dates in the backend. So any data that has already been entered for 2016W1 is stored in the database against 2016/01/04 - 2016/01/10. The only thing you may want to consider is if any of your users accidentally entered data for 2016W1 thinking it was 2015/12/28 - 2016/01/03.

@Jason, Morten - can you please confirm the above?

Cheers,

-doh

On Thu, Jan 7, 2016 at 11:46 PM, Marta Vila martavila@gmail.com wrote:

Hello Jason,

thanks. We will update all offline servers us well as soon as we can.
Could you tell me, with the fix, what happens with the former W1?

The period is just removed and weeks are re-numbered? It is considered in the fix that it could be data already in that week or should we take care of removing it before updating ?

Thanks!

On 7 January 2016 at 17:09, Jason Pickering jason.p.pickering@gmail.com wrote:

The only thing you will need to do is to update you server with the latest build. For 2.17 it is available here.

http://ci.dhis2.org/job/dhis2-2.17/lastSuccessfulBuild/artifact/dhis-2/dhis-web/dhis-web-portal/target/dhis.war

Regards,

Jason

On Thu, Jan 7, 2016 at 3:37 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
As I understand it we must return to the version 2.17 and there is no sql script to run before returning to this version?

2016-01-07 13:25 GMT+00:00 Jan Henrik Øverland janhenrik.overland@gmail.com:

Thanks Jason

On Thu, Jan 7, 2016 at 2:21 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

Hi Marta and Papa,
We identified the bug (we think) and Morten has updated the code with a fix, and backported it back to version 2.17. New builds are available here http://ci.dhis2.org/ .

I have tested this on one instance, and it seems to work OK now. Let us know if it works for you.

Best regards,

Jason

On Tue, Jan 5, 2016 at 5:14 PM, Marta Vila martavila@gmail.com wrote:

Hi Jason,

we just started receiving emails from users reporting the same problem.

Will follow the evolution.

Cheers

On 4 January 2016 at 18:05, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
If that information can be useful I noticed that the dhis our Ministry of Health does not have this problem and they have version 2.15.

2016-01-04 16:16 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,

I am able to reproduce this. It is clearly a bug.

I think you should used 2015W53 for this period, but there could be a major problem if the weeks for 2016 are off.

Jan/Lars, could you comment?

Regards,

Jason

On Mon, Jan 4, 2016 at 4:55 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


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


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


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Thank you all.i’m also testing and will let you know if any issue.

Regards

venuste

···

De : Marta Vila martavila@gmail.com
À : Jason Pickering jason.p.pickering@gmail.com
Cc : nsanzumuhire venuste vensanze@yahoo.fr; David Siang Fong Oh doh@thoughtworks.com; "dhis2-users@lists.launchpad.net" dhis2-users@lists.launchpad.net; DHIS 2 Developers list dhis2-devs@lists.launchpad.net
Envoyé le : Lundi 11 janvier 2016 20h49
Objet : Re: [Dhis2-devs] [Dhis2-users] define weekly

Hi David, Jason,

thanks for the explanation and for sharing the information about the fix. Itr is very useful for us to send the fix only.

Venuste, we will share the feedback if we find any issue.

Thank you all,

Marta

On 11 January 2016 at 16:35, Jason Pickering jason.p.pickering@gmail.com wrote:

Hi Venuste,
As we have said a few times now on this thread, we have fixed the bug. You will need to update your server with the latest build for your version available here

http://ci.dhis2.org/

After that, be sure to clear your browser cache (and instruct users who are entering data to do the same).

Regards,

Jason

On Mon, Jan 11, 2016 at 3:49 PM, nsanzumuhire venuste vensanze@yahoo.fr wrote:

Dear all,

Any feedback on the previews bug?

did any one tried to fix it?

in Rwanda

We are also having the same issue on the weeks.

W1 - 2015-12-28 - 2016-01-03 is the same as W53 - 2015-12-28 - 2016-01-03


De : David Siang Fong Oh doh@thoughtworks.com
À : Marta Vila martavila@gmail.com
Cc : "dhis2-users@lists.launchpad.net" dhis2-users@lists.launchpad.net; DHIS 2 Developers list dhis2-devs@lists.launchpad.net
Envoyé le : Vendredi 8 janvier 2016 15h40
Objet : Re: [Dhis2-users] [Dhis2-devs] define weekly

Hi Marta,

The bug seems to be only a display issue in the DHIS web application. The Javascript file in question is responsible for calculating the date ranges for weekly periods (i.e. 2015W52, 2015W53 etc.) and displaying them in the UI. When sending requests to the backend however, the web application seems to ignore the data range and only sends the period as 2016W1 etc.

As far as repercussions for your existing entered data, the data is being stored against the correct dates in the backend. So any data that has already been entered for 2016W1 is stored in the database against 2016/01/04 - 2016/01/10. The only thing you may want to consider is if any of your users accidentally entered data for 2016W1 thinking it was 2015/12/28 - 2016/01/03.

@Jason, Morten - can you please confirm the above?

Cheers,

-doh

On Thu, Jan 7, 2016 at 11:46 PM, Marta Vila martavila@gmail.com wrote:

Hello Jason,

thanks. We will update all offline servers us well as soon as we can.
Could you tell me, with the fix, what happens with the former W1?

The period is just removed and weeks are re-numbered? It is considered in the fix that it could be data already in that week or should we take care of removing it before updating ?

Thanks!

On 7 January 2016 at 17:09, Jason Pickering jason.p.pickering@gmail.com wrote:

The only thing you will need to do is to update you server with the latest build. For 2.17 it is available here.

http://ci.dhis2.org/job/dhis2-2.17/lastSuccessfulBuild/artifact/dhis-2/dhis-web/dhis-web-portal/target/dhis.war

Regards,

Jason

On Thu, Jan 7, 2016 at 3:37 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
As I understand it we must return to the version 2.17 and there is no sql script to run before returning to this version?

2016-01-07 13:25 GMT+00:00 Jan Henrik Øverland janhenrik.overland@gmail.com:

Thanks Jason

On Thu, Jan 7, 2016 at 2:21 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

Hi Marta and Papa,
We identified the bug (we think) and Morten has updated the code with a fix, and backported it back to version 2.17. New builds are available here http://ci.dhis2.org/ .

I have tested this on one instance, and it seems to work OK now. Let us know if it works for you.

Best regards,

Jason

On Tue, Jan 5, 2016 at 5:14 PM, Marta Vila martavila@gmail.com wrote:

Hi Jason,

we just started receiving emails from users reporting the same problem.

Will follow the evolution.

Cheers

On 4 January 2016 at 18:05, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
If that information can be useful I noticed that the dhis our Ministry of Health does not have this problem and they have version 2.15.

2016-01-04 16:16 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,

I am able to reproduce this. It is clearly a bug.

I think you should used 2015W53 for this period, but there could be a major problem if the weeks for 2016 are off.

Jan/Lars, could you comment?

Regards,

Jason

On Mon, Jan 4, 2016 at 4:55 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


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


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


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Hello,

After an upgrate to DHIS 2.21 v20998, it’s seems that the problem is solve for Data Entry, but not in reporting Rate summary (53 weeks for 2015).

I tried to produce the same error with EPI-STOCK Form in Demo

https://play.dhis2.org/demo/dhis-web-reporting/displayViewDataCompletenessForm.action

···

=========================
EKANI Guy

Le Mardi 12 janvier 2016 7h44, nsanzumuhire venuste vensanze@yahoo.fr a écrit :

Thank you all.i’m also testing and will let you know if any issue.

Regards

venuste


De : Marta Vila martavila@gmail.com
À : Jason Pickering jason.p.pickering@gmail.com
Cc : nsanzumuhire venuste vensanze@yahoo.fr; David Siang Fong Oh doh@thoughtworks.com; "dhis2-users@lists.launchpad.net" dhis2-users@lists.launchpad.net; DHIS 2 Developers list dhis2-devs@lists.launchpad.net
Envoyé le : Lundi 11 janvier 2016 20h49
Objet : Re: [Dhis2-devs] [Dhis2-users] define weekly

Hi David, Jason,

thanks for the explanation and for sharing the information about the fix. Itr is very useful for us to send the fix only.

Venuste, we will share the feedback if we find any issue.

Thank you all,

Marta

On 11 January 2016 at 16:35, Jason Pickering jason.p.pickering@gmail.com wrote:

Hi Venuste,
As we have said a few times now on this thread, we have fixed the bug. You will need to update your server with the latest build for your version available here

http://ci.dhis2.org/

After that, be sure to clear your browser cache (and instruct users who are entering data to do the same).

Regards,

Jason

On Mon, Jan 11, 2016 at 3:49 PM, nsanzumuhire venuste vensanze@yahoo.fr wrote:

Dear all,

Any feedback on the previews bug?

did any one tried to fix it?

in Rwanda

We are also having the same issue on the weeks.

W1 - 2015-12-28 - 2016-01-03 is the same as W53 - 2015-12-28 - 2016-01-03


De : David Siang Fong Oh doh@thoughtworks.com
À : Marta Vila martavila@gmail.com
Cc : "dhis2-users@lists.launchpad.net" dhis2-users@lists.launchpad.net; DHIS 2 Developers list dhis2-devs@lists.launchpad.net
Envoyé le : Vendredi 8 janvier 2016 15h40
Objet : Re: [Dhis2-users] [Dhis2-devs] define weekly

Hi Marta,

The bug seems to be only a display issue in the DHIS web application. The Javascript file in question is responsible for calculating the date ranges for weekly periods (i.e. 2015W52, 2015W53 etc.) and displaying them in the UI. When sending requests to the backend however, the web application seems to ignore the data range and only sends the period as 2016W1 etc.

As far as repercussions for your existing entered data, the data is being stored against the correct dates in the backend. So any data that has already been entered for 2016W1 is stored in the database against 2016/01/04 - 2016/01/10. The only thing you may want to consider is if any of your users accidentally entered data for 2016W1 thinking it was 2015/12/28 - 2016/01/03.

@Jason, Morten - can you please confirm the above?

Cheers,

-doh

On Thu, Jan 7, 2016 at 11:46 PM, Marta Vila martavila@gmail.com wrote:

Hello Jason,

thanks. We will update all offline servers us well as soon as we can.
Could you tell me, with the fix, what happens with the former W1?

The period is just removed and weeks are re-numbered? It is considered in the fix that it could be data already in that week or should we take care of removing it before updating ?

Thanks!

On 7 January 2016 at 17:09, Jason Pickering jason.p.pickering@gmail.com wrote:

The only thing you will need to do is to update you server with the latest build. For 2.17 it is available here.

http://ci.dhis2.org/job/dhis2-2.17/lastSuccessfulBuild/artifact/dhis-2/dhis-web/dhis-web-portal/target/dhis.war

Regards,

Jason

On Thu, Jan 7, 2016 at 3:37 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
As I understand it we must return to the version 2.17 and there is no sql script to run before returning to this version?

2016-01-07 13:25 GMT+00:00 Jan Henrik Øverland janhenrik.overland@gmail.com:

Thanks Jason

On Thu, Jan 7, 2016 at 2:21 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

Hi Marta and Papa,
We identified the bug (we think) and Morten has updated the code with a fix, and backported it back to version 2.17. New builds are available here http://ci.dhis2.org/ .

I have tested this on one instance, and it seems to work OK now. Let us know if it works for you.

Best regards,

Jason

On Tue, Jan 5, 2016 at 5:14 PM, Marta Vila martavila@gmail.com wrote:

Hi Jason,

we just started receiving emails from users reporting the same problem.

Will follow the evolution.

Cheers

On 4 January 2016 at 18:05, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hi Jason,
If that information can be useful I noticed that the dhis our Ministry of Health does not have this problem and they have version 2.15.

2016-01-04 16:16 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,

I am able to reproduce this. It is clearly a bug.

I think you should used 2015W53 for this period, but there could be a major problem if the weeks for 2016 are off.

Jan/Lars, could you comment?

Regards,

Jason

On Mon, Jan 4, 2016 at 4:55 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

I noticed in the function given before he repeated in the W53 2015 with W1 2016. When you try to enter data we have the following error:
One or more data sets for data element does not allow future periods: O6ZD3CjKywK .

In attached the screenshots.

2016-01-04 15:31 GMT+00:00 Jason Pickering jason.p.pickering@gmail.com:

Hi Papa,
Could you be more specific?

December 28th - Jan 3rd should be 2015W53. Usually years have 52 weeks, but this happens from time to time, due to how ISO weeks are defined.

Are you seeing this in the analysis modules for last 52 weeks?

Regards,

Jason

On Mon, Jan 4, 2016 at 4:18 PM, papa alioune Sokhna sokhnapapa@gmail.com wrote:

Hello team
how to define the numbers of weeks on dhis2 because the marking is not correct it there’s a repitition of the week of December 28, 2015 to January 4, 2016.

Best regards.


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Papa Alioune SOKHNA
**Informaticien **

Spécialité: développement d’application web, mobile et logiciels surs

Tel: +221 77 442 16 22


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


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


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


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp


Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049


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