Currently recurring general journal entries will not post if the posting date of the recurring journal line(s) are a date after the work date of the user. This is great behaviour and good protection against accidentally posting these entries too far into the future.
I would like it, however, if the error message thrown when there's no valid lines was improved. I've had several end-users attempting to post entries a few days ahead to prepare for month and and get confused from the error message thrown. Currently it reads: "There is nothing to post because the journal does not contain a quantity or amount.", which is helpful if the issue with the entry is a quantity or amount based concern. It falls short if there's a date based issue.
Can the message be modified to something like: "There is nothing to post because the journal does not contain a quantity or amount or all lines with quantities and amounts are dated after your work date."?
Comments
I have a similar issue where allowed posting dates were used. I didn't want these to change or to be removed. The message the recurring general journal shows is not clear what the error is. The only way of knowing what the error(s) is by looking at the Test report. Instead of the error being “There is nothing to post because the journal does not contain a quantity or amount” – which is hard coded. It should be something like “Nothing to Post – Run Test Report for further details”. This is because the errors could be different for every line.
Category: General
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team