45
FYI: After updating to GP 2018 our client running on a remote app was getting this error when trying to post a Bank Deposit.
The problem is the GLPOSTDATE in the CM10100 table was not being populated.
The resolution was to give additional read / write permissions to the GP install folder.
Chip Reed
The bug is on the latest release of GP18 since the function to attach documents to bank Deposits was added.
The known issue is:
93685 – Unable to attach documents in Bank Deposit entry window and Doc Attach “You cannot post. The fiscal period that contains this posting date has not been set up.”
DESCR: Users not able to post deposits due to the GL posting date is getting set to 00/00/0000 in the CM10100 table. The blue expansion window is missing to be able to change it before posting.
Target fix date: not set yet, watching customer count
Thanks Chip for posting the work-around and the solution.
I don't remember that bug, but must confess that it is a very particular situation..
On which minor build version of GP was that bug noted ? Do you know if Microsoft has published a fix for that ?
Beat Bucher and others
Update and Correction to this post.
Our mistake was the user kept getting the error until we changed the local drive rights, but in fact he stopped attaching documents after we change the rights.
It turns out it is not related to computer rights, but the document attachments. There is a known bug in GP2018 when attaching documents to a bank deposit that it will reset the posting date to 01/01/1901.
To make matters worse, if Multi-currency is not enabled, the Drill down button to the Posting date window is hidden and you cannot get the GL Posting Date.
The work around (if multi-currency is not activated) is to attach the documents, then change the document date to a different date and then change is back to the correct document date.
Sorry for the confusion.
Thank you for your time,
Chip Reed
Beat,
We just took the Accounting AD group and gave them standard Read / write access to the GP install folder.
This is on a Term Server using remote desktop app.
This was very odd and the first time I have experienced it. Plus the users should have tested this in the pre-upgrade
The GL posting date would not set to the transaction date. We absolutely verified that it was not a setting in GP.
I don't know what changed in right's between testing and live as the client app was the same. There is no 3rd party app. I can only assume that some file, or dll or something in the GP in stall folder changed and the users did not have read write access.
Chip
Hi Chip,
Not sure I follow you... I don't see the relationship between the read/write permissions on the GP folder with the fact that a fiscal period is missing or not open... nor what this would have to do with the fact that the CM table GLPOSTDATE field is blank...
What "additional" read/write permissions are you talking about ? Regular users should already have the necessary permissions to run GP properly...
Hi,
Thank you for this information on your scenario with this information message.
Margi Jandro
Microsoft Dynamics GP Support Engineer
This might be due to the batch doesn't have valid batch date and posting date coming from batch date. Please try to change the setup-posting-posting-posting date from Transaction instead of batch and try again.
#1
André Arnaud de Cal...
291,391
Super User 2024 Season 2
#2
Martin Dráb
230,445
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
