RE: GLPostings causing hard stop when called
After investigation and noticing a significant performance drop (log in can take up to 7 seconds), I found out that we actually have 12017 periods defined in our system, going up to year 3019.
Looking at the audit trail, it appears that the damage was caused by one single user within a 5 second timeframe.
What could possibly cause almost 17000 periods being created?
If a user types 04/30/3019 in a bank transaction instead of 2019, I'm assuming it creates all periods between 2019 and 3019, correct?
|