hola Tinashe! Check if this is happening for charges or other types of behavior like interest posting in case of Savings schedules. If this is happening across all types of date posted by the system(as in system defined), check if enumerations of ids like txn ids, (in case of loan schedule, paycycle ids) are getting enumerated well in the relevant database table. Think Is there a binding relationship between enumeration of event id and date? >>>If it is a loan scheduler specific issue then the loan scheduler requires re-engineering, but will we get there later?
Anyway, see if it is a generic event, in that case maintaining the tenant time zones and other relevant dependencies like database clock, will fix this for the time being. Remember, each time the server restarts, the tenant's clock may reset the time zone. Hope this guide helps- https://research.muellners.org/fineract-common-deployment-issues/ Read below item: A. Timezone Tenant Configuration: Each date in a loan schedule, loan product date or charges payment date posted may jump one date back or more if the Time Zone of the Tenant is not properly set up. On Tue, Dec 7, 2021 at 4:51 PM Francis Guchie <francisguc...@gmail.com> wrote: > Dear All, > > I had this issue at one point in time and I thought it was a bug. I do > encourage all of us to always document our findings and anything we think > is an issue. > Kindly find my detailed findings here > https://issues.apache.org/jira/browse/FINERACT-1309 > > If this helps you please let everyone in this noble family know > > My Kind Regards > > Francis Guchie Kirago > *Skype:* francisguchie > *Telegram: *232 79 19 44 07 > *Whatsapp: *232 79 19 44 07 > *LINKEDIN:* https://www.linkedin.com/in/francis-guchie-kirago-a4379617/ > twitter: @FrancisGuchie > > > > > > > > > > On Tue, Dec 7, 2021 at 4:15 PM Tinashe Muchenje <tmuche...@gmail.com> > wrote: > >> Still having the same issue of date. I checked the time zone and it is >> correct. Still wondering why the system is posting using the previous >> working date. >> >> Regards >> >> On Thu, Dec 2, 2021 at 4:56 PM ISRAEL OLUFEMI <ioluf...@ymail.com> wrote: >> >>> Hi Tinashe, >>> >>> I am also experiencing this issue. Can you confirm the timezone on your >>> windows instance is the timezone you want it to be? I suspect that might be >>> the issue. I will also try this out in my Linux instance. >>> >>> On 2 Dec 2021, at 12:12, Tinashe Muchenje <tmuche...@gmail.com> wrote: >>> >>> >>> Good day >>> >>> Thank you for the support on Mifos. We really appreciate it. >>> >>> I have this date issue on Mifos MIFOSX-21.07.02_PATCH_RELEASE >>> <https://github.com/openMF/community-app/tree/MIFOSX-21.07.02_PATCH_RELEASE> >>> on Windows. All transactions posted in the database are using the previous >>> working date. Even if I change the on date picker, the system will post >>> using the previous date. >>> >>> I also noted this error when mifos server is starting >>> >>> java.sql.SQLException: The server time zone value 'Coordinated Universal >>> Time' is unrecognized or represents more than one time zone. You must >>> configure either the server or JDBC driver (via the 'serverTimezone' >>> configuration property) to use a more specifc time zone value if you want >>> to utilize time zone support. >>> >>> Please Help >>> >>> >>> Regards >>> -- >>> Tinashe Muchenje >>> >>> >> >> -- >> Tinashe Muchenje >> _______________________________________________ >> Mifos-users mailing list >> Mifos-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/mifos-users >> > _______________________________________________ > Mifos-users mailing list > Mifos-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mifos-users > -- Ankit Managing Partner Muellners ApS, Denmark Impressum- Muellners® Inc; Copenhagen, Denmark CVR: 41548304; New Delhi, India CIN: U72900DL2019PTC344870; Foundation EU CVR:41008407 This mail is governed by Muellners® IT policy. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
_______________________________________________ Mifos-users mailing list Mifos-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mifos-users
