Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DataTable date fields: datepicker disables dates before 1st Jan of this year #3001

terencemo opened this Issue Aug 10, 2018 · 2 comments


3 participants
Copy link

terencemo commented Aug 10, 2018


When editing a datatable having date fields, the date field may need to have values of previous years, e.g for a Next of Kin datatable, the date of birth of the next of kin can be several years before. Hence we need to be able to select dates of previous years. Currently, the datepicker only enables dates from 1st Jan, 2018 (as 2018 is the current year).

Steps to Reproduce

Create a client datatable for example Next of Kin and add a date column to it e.g date of birth. Then go to a client and try to enter this datatable data. Select the date field created earlier. You will see a calendar popup (datepicker).

Expected Behaviour

You should be able to select any date in the past in a previous year.

Actual Behaviour

Previous years are disabled and cannot be selected via datepicker.


  • Mifos X version: 18.03.01
  • Browser used: Google Chrome

Screenshots, if any


This comment has been minimized.

Copy link

Hackingforlife commented Mar 25, 2019

hello, I'm an applicant for outreachy, I would love to fix this.i have already set up the community app locally.I seek further guidance on how to solve this issue


This comment has been minimized.

Copy link
Contributor Author

terencemo commented Mar 27, 2019

@Hackingforlife this has already been fixed by PR #3008 but there is a related issue #3092 which I suggest you can fix instead. Otherwise you can copy-paste the changes from the above PR and add changes that fix both issues 3008 and 3092 since the reviewer of the above PR stated desire was that fixes for both issues be combined into a single PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.