Hi devs,
I’ve set up a tracker program (with registration) in 2.22 with one stage. For the stage I’ve selected “auto-generate” and “report date to use”: Date of enrollment.
However, when I enroll a new person with the default date (today), the report date is set to yesterday, i.e. the event date is always set to the date before the enrollment date. Is this a bug or is there a reason for this??
This is a problem we are aware of for quite sometime. It has nothing to do with program / program stage setting and(or) event generation. It is related with server date and the way dates are handled there. We are hoping to come with a solution for 2.24.
···
On Mon, Apr 18, 2016 at 10:24 PM, Olav Poppe olav.poppe@me.com wrote:
Hi devs,
I’ve set up a tracker program (with registration) in 2.22 with one stage. For the stage I’ve selected “auto-generate” and “report date to use”: Date of enrollment.
However, when I enroll a new person with the default date (today), the report date is set to yesterday, i.e. the event date is always set to the date before the enrollment date. Is this a bug or is there a reason for this??
This is.a.real.problem for us too.and are confusing data capturers since they select one date but another date is displayed. I also saw in.one instance that it is not possible to select the.same date for a repeatable stage but have not tested this on later versions. Is this intended?
One consolation is that the date selected is stored correctly in the table it is just displayed incorrectly on the server.
Hi devs,
I’ve set up a tracker program (with registration) in 2.22 with one stage. For the stage I’ve selected “auto-generate” and “report date to use”: Date of enrollment.
However, when I enroll a new person with the default date (today), the report date is set to yesterday, i.e. the event date is always set to the date before the enrollment date. Is this a bug or is there a reason for this??
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
Yes, it is a problem. We are trying to find a proper solution.
We do not have that kind of restriction on repeatable stages. The only restriction we have on repeatable stages is that one can not create a new event if there exists another scheduled event of the same stage.
As to dates, one restriction we have is whether to allow or not future enrollment / incident dates for programs. This can be controlled under program setting. For events, while it is possible to have future due dates, it is not possible to have future “execution” or “report” dates.
Let us know if you see a different behavior than this.
···
On Tue, Apr 19, 2016 at 6:31 AM, Elmarie Claasen elmarie@hisp.org wrote:
Hi.all,
This is.a.real.problem for us too.and are confusing data capturers since they select one date but another date is displayed. I also saw in.one instance that it is not possible to select the.same date for a repeatable stage but have not tested this on later versions. Is this intended?
One consolation is that the date selected is stored correctly in the table it is just displayed incorrectly on the server.
Hi devs,
I’ve set up a tracker program (with registration) in 2.22 with one stage. For the stage I’ve selected “auto-generate” and “report date to use”: Date of enrollment.
However, when I enroll a new person with the default date (today), the report date is set to yesterday, i.e. the event date is always set to the date before the enrollment date. Is this a bug or is there a reason for this??
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.