1,030
Is there a leap year/Feb 29 issue in the current GP 2010 product?
A user was trying to enter a Miscellaneous Log Batch Entry today with a Posting Date of 2/29/2012 and sees the error. Using 2/28/2012 works
The following errors were found while validating distributions...The reporting period is missing or invalid.
GP 2010 R2
*This post is locked for comments
I think I have the behavior nailed down
- The Miscellaneous Log Setup screen has 03/01/2011 as the "First Date for Reporting Period 1".
- "No of Reporting Periods per Year" in setup is 365 and
- "Reporting Periods" is set to daily
On the Miscellaneous Log Entry screen, the Rep. Period count gets messed up on Feb 29 with a count of 366. Pushing one more day by setting the Period Begin Date on this screen with the arrow changes the date to 03/01/2012 and the Rep. Period number back to 1.
I believe it is a subtle bug that you would likely only see on leap years with these specific settings.
Seems similar to
Article ID: 891212 - Last Review: July 25, 2011 - Revision: 3.0
"The Reporting Period is missing or invalid" error message when you try to post a Project
timesheet transaction in Great Plains 7.5 and in Great Plains 8.0
But in a different area and in the latest version.
Any ideas other than not to use the date?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
