Can anyone help with getting around entering monthly data for future periods beyond what is available by default?
I have a use case where users need to enter data for months in 2014 (these are advance monthly payments) but currently the future periods allowed do not extend beyond December 2013. The “Next Year” function does not make a difference here.
It is critical that the data is entered monthly rather than yearly. It is also important that users can enter data in (theoretically) unlimited periods in the future if the case arises that payment is made up until tim “t”.
I have added 2014 monthly data to the Period table. I still can’t see the periods in the data entry screen (see file attached) but when I use the “Get pdf for Data Entry” function in the data set module, I can see the future periods displayed (see attached).
Any insight would be much appreciated.
Many thanks.
Regards,
Busoye
···
On 29 Sep 2013, at 09:17, Adebusoye Anifalaje busoye@hisp.org wrote:
Hi all,
Can anyone help with getting around entering monthly data for future periods beyond what is available by default?
I have a use case where users need to enter data for months in 2014 (these are advance monthly payments) but currently the future periods allowed do not extend beyond December 2013. The “Next Year” function does not make a difference here.
It is critical that the data is entered monthly rather than yearly. It is also important that users can enter data in (theoretically) unlimited periods in the future if the case arises that payment is made up until tim “t”.
Hi Busoye,
I think the problem is that these periods have not been generated yet. In the past, we have generated them using SQL. Something like
INSERT INTO period
SELECT nextval(‘hibernate_sequence’::regclass) as periodid ,
(SELECT periodtypeid from periodtype where name = ‘Monthly’) periodtypeid,
(startdate + ‘1 year’::interval)::date as startdate,
(enddate + ‘1 year’::interval)::date as enddate
from period
where periodtypeid = (SELECT periodtypeid from periodtype where name = ‘Monthly’)
and startdate >= ‘2013-01-01’ and enddate <=‘2013-12-31’
This is a really basic statement, and would not check for things like periods which already exist so you might need to tweak it a bit.
There should really be a method to pre-generate future periods, but I am not sure this exists.
Regards,
Jason
···
On Sun, Sep 29, 2013 at 5:20 PM, Adebusoye Anifalaje busoye@hisp.org wrote:
Just an update
I have added 2014 monthly data to the Period table. I still can’t see the periods in the data entry screen (see file attached) but when I use the “Get pdf for Data Entry” function in the data set module, I can see the future periods displayed (see attached).
Any insight would be much appreciated.
Many thanks.
Regards,
Busoye
On 29 Sep 2013, at 09:17, Adebusoye Anifalaje busoye@hisp.org wrote:
Hi all,
Can anyone help with getting around entering monthly data for future periods beyond what is available by default?
I have a use case where users need to enter data for months in 2014 (these are advance monthly payments) but currently the future periods allowed do not extend beyond December 2013. The “Next Year” function does not make a difference here.
It is critical that the data is entered monthly rather than yearly. It is also important that users can enter data in (theoretically) unlimited periods in the future if the case arises that payment is made up until tim “t”.
I had populated the period table with the months I needed and can actually see this in the pdf data entry version (see attachments from previous email). The problem I am having is that I can’t see these months in the data entry screen. Is there a way around this or anything else I need to do to allow the later periods to be visible for data entry?
Hi Busoye,
I think the problem is that these periods have not been generated yet. In the past, we have generated them using SQL. Something like
INSERT INTO period
SELECT nextval(‘hibernate_sequence’::regclass) as periodid ,
(SELECT periodtypeid from periodtype where name = ‘Monthly’) periodtypeid,
(startdate + ‘1 year’::interval)::date as startdate,
(enddate + ‘1 year’::interval)::date as enddate
from period
where periodtypeid = (SELECT periodtypeid from periodtype where name = ‘Monthly’)
and startdate >= ‘2013-01-01’ and enddate <=‘2013-12-31’
This is a really basic statement, and would not check for things like periods which already exist so you might need to tweak it a bit.
There should really be a method to pre-generate future periods, but I am not sure this exists.
Regards,
Jason
On Sun, Sep 29, 2013 at 5:20 PM, Adebusoye Anifalaje busoye@hisp.org wrote:
Just an update
I have added 2014 monthly data to the Period table. I still can’t see the periods in the data entry screen (see file attached) but when I use the “Get pdf for Data Entry” function in the data set module, I can see the future periods displayed (see attached).
Any insight would be much appreciated.
Many thanks.
Regards,
Busoye
On 29 Sep 2013, at 09:17, Adebusoye Anifalaje busoye@hisp.org wrote:
Hi all,
Can anyone help with getting around entering monthly data for future periods beyond what is available by default?
I have a use case where users need to enter data for months in 2014 (these are advance monthly payments) but currently the future periods allowed do not extend beyond December 2013. The “Next Year” function does not make a difference here.
It is critical that the data is entered monthly rather than yearly. It is also important that users can enter data in (theoretically) unlimited periods in the future if the case arises that payment is made up until tim “t”.
as you observe we have some restrictions on future periods even though the “allow future periods” setting is enabled.
We could of course lift all these restrictions and allow any future period when the setting is enabled. This comes at the risk of users inadvertently selecting a future year.
Any opposition against doing this out there?
Lars
···
On Tue, Oct 1, 2013 at 10:58 AM, Busoye Anifalaje busoye@hisp.org wrote:
Hi Jason,
Your reply was much appreciated.
I had populated the period table with the months I needed and can actually see this in the pdf data entry version (see attachments from previous email). The problem I am having is that I can’t see these months in the data entry screen. Is there a way around this or anything else I need to do to allow the later periods to be visible for data entry?
Hi Busoye,
I think the problem is that these periods have not been generated yet. In the past, we have generated them using SQL. Something like
INSERT INTO period
SELECT nextval(‘hibernate_sequence’::regclass) as periodid ,
(SELECT periodtypeid from periodtype where name = ‘Monthly’) periodtypeid,
(startdate + ‘1 year’::interval)::date as startdate,
(enddate + ‘1 year’::interval)::date as enddate
from period
where periodtypeid = (SELECT periodtypeid from periodtype where name = ‘Monthly’)
and startdate >= ‘2013-01-01’ and enddate <=‘2013-12-31’
This is a really basic statement, and would not check for things like periods which already exist so you might need to tweak it a bit.
There should really be a method to pre-generate future periods, but I am not sure this exists.
Regards,
Jason
On Sun, Sep 29, 2013 at 5:20 PM, Adebusoye Anifalaje busoye@hisp.org wrote:
Just an update
I have added 2014 monthly data to the Period table. I still can’t see the periods in the data entry screen (see file attached) but when I use the “Get pdf for Data Entry” function in the data set module, I can see the future periods displayed (see attached).
Any insight would be much appreciated.
Many thanks.
Regards,
Busoye
On 29 Sep 2013, at 09:17, Adebusoye Anifalaje busoye@hisp.org wrote:
Hi all,
Can anyone help with getting around entering monthly data for future periods beyond what is available by default?
I have a use case where users need to enter data for months in 2014 (these are advance monthly payments) but currently the future periods allowed do not extend beyond December 2013. The “Next Year” function does not make a difference here.
It is critical that the data is entered monthly rather than yearly. It is also important that users can enter data in (theoretically) unlimited periods in the future if the case arises that payment is made up until tim “t”.
I would not suggest removing the restrictions completely. A suggestion for monthly period types would be to have no more than 36 months into the future. If you consider use cases that deal with monthly subscriptions, it is possible to have a scenario where a year or two is paid in advance.
If there are no objects, could you do this fairly quickly?
Many thanks.
Regards,
Busoye
···
On Tue, Oct 1, 2013 at 10:58 AM, Busoye Anifalaje busoye@hisp.org wrote:
Hi Jason,
Your reply was much appreciated.
I had populated the period table with the months I needed and can actually see this in the pdf data entry version (see attachments from previous email). The problem I am having is that I can’t see these months in the data entry screen. Is there a way around this or anything else I need to do to allow the later periods to be visible for data entry?
Hi Busoye,
I think the problem is that these periods have not been generated yet. In the past, we have generated them using SQL. Something like
INSERT INTO period
SELECT nextval(‘hibernate_sequence’::regclass) as periodid ,
(SELECT periodtypeid from periodtype where name = ‘Monthly’) periodtypeid,
(startdate + ‘1 year’::interval)::date as startdate,
(enddate + ‘1 year’::interval)::date as enddate
from period
where periodtypeid = (SELECT periodtypeid from periodtype where name = ‘Monthly’)
and startdate >= ‘2013-01-01’ and enddate <=‘2013-12-31’
This is a really basic statement, and would not check for things like periods which already exist so you might need to tweak it a bit.
There should really be a method to pre-generate future periods, but I am not sure this exists.
Regards,
Jason
On Sun, Sep 29, 2013 at 5:20 PM, Adebusoye Anifalaje busoye@hisp.org wrote:
Just an update
I have added 2014 monthly data to the Period table. I still can’t see the periods in the data entry screen (see file attached) but when I use the “Get pdf for Data Entry” function in the data set module, I can see the future periods displayed (see attached).
Any insight would be much appreciated.
Many thanks.
Regards,
Busoye
On 29 Sep 2013, at 09:17, Adebusoye Anifalaje busoye@hisp.org wrote:
Hi all,
Can anyone help with getting around entering monthly data for future periods beyond what is available by default?
I have a use case where users need to enter data for months in 2014 (these are advance monthly payments) but currently the future periods allowed do not extend beyond December 2013. The “Next Year” function does not make a difference here.
It is critical that the data is entered monthly rather than yearly. It is also important that users can enter data in (theoretically) unlimited periods in the future if the case arises that payment is made up until tim “t”.