Dynamics 365 F&O/AX Dynamics 365 CE / CRM Dynamics GP Business Central / NAV UG Dynamics SL Power Platform Fabric UG MS Copilot UG

[Trish Robertson]

Is it possible to set a range for the document dates that can be used in Great Plains?

 

For example, some payables documents have been entered with a document date listing a year of 2106 and other future dated items. This causes an issue on the AP aging. It is a manual date that is entered by AP in the transaction entry screen in the Purchasing Module. Is it possible to limit this date so they cannot date things so far in the future? Or to create some kind of prompt that says “this date is in a future period. Are you sure you would like to proceed?” – this way they are having to double check their work?

——————————
Trish Robertson
Helpdesk Supervisor
CFRLTD
Greenville SC
——————————

[Matthew Arp]

Unfortunately no, your best bet would be a VBA customization or a .NET AddIn (the latter would be the recommended). This does sounds like an excellent idea for MS Connect though!

——————————
Matthew Arp
Business Systems Developer
Hunton Group
Houston TX
——————————
——————————————-

[Charles Allen]

Trish,

 

Install the Professional Services Tools Library.

 

One of the options is called Doc Date Verify. It will only allow you to enter dates that are set up in Fiscal Period Setup.

 

Using Doc Date Verify

When Doc Date Verify is activated, and a document date is entered, a check will be

performed to determine whether the document date is in a valid fiscal period or if

the fiscal period is closed.

 

• If the date does not fall within a valid fiscal period, a message will be displayed

and the user will not be allowed to continue until the date is in a valid period.

 

• If the Document Date falls within a period that is closed, a message will be

displayed that will allow the user to correct the date or continue on leaving the

date.

 

Charles Allen

Senior Managing Consultant | BKD, LLP

BKD Technologies

Office 713.499.4629

Cell 713.494.2104

 

 

****** BKD, LLP Internet Email Confidentiality Footer ******

Privileged/Confidential Information may be contained
in this message. If you are not the addressee indicated in
this message (or responsible for delivery of the message
to such person), you may not copy or deliver this message to
anyone. In such case, you should destroy this message, and
notify us immediately. If you or your employer do not consent
to Internet email messages of this kind, please advise us
immediately. Opinions, conclusions and other information
expressed in this message are not given or endorsed by my
firm or employer unless otherwise indicated by an authorized
representative independent of this message.

Any tax advice contained in the body of this email was not
intended or written to be used, and cannot be used, by the
recipient for the purpose of avoiding penalties that may be
imposed under the Internal Revenue Code or applicable state
or local tax law provisions.

These discussions and conclusions are based on the facts
as stated and existing authorities as of the date of this
email. Our advice could change as a result of changes in the
applicable laws and regulations. We are under no obligation
to update this information if such changes occur. Our advice
is based on your unique facts and circumstances as you
communicated them to us and should not be used or relied
on by anyone else.

——Original Message——

Is it possible to set a range for the document dates that can be used in Great Plains?

 

For example, some payables documents have been entered with a document date listing a year of 2106 and other future dated items. This causes an issue on the AP aging. It is a manual date that is entered by AP in the transaction entry screen in the Purchasing Module. Is it possible to limit this date so they cannot date things so far in the future? Or to create some kind of prompt that says “this date is in a future period. Are you sure you would like to proceed?” – this way they are having to double check their work?

——————————
Trish Robertson
Helpdesk Supervisor
CFRLTD
Greenville SC
——————————

[Beat Bucher]

Hi Trish,
Charles pointed you in the right direction.
However, read this thread carefully, as there are some considerations involved:
https://www.gpug.com/communities/community-home/digestviewer/viewthread?MessageKey=22e8757f-fb62-4c62-8609-022819c8e518&CommunityKey=4754a624-39c5-4458-8105-02b65a7e929e&tab=digestviewer#bm22e8757f-fb62-4c62-8609-022819c8e518#bm0
If you’re not sure about how to do it, ask your partner.. and do a quick search here on GPUG forum about ‘PSTL doc date verify’.. I’m sure you’ll find plenty of hints.

——————————
Beat Bucher
Business Analyst, Dynamics GP MVP
Ultra-Electronics Forensic Technology Inc.
Montreal QC/Canada
+1-514-489-4267
@GP_Beat http://dyngpbeat.wordpress.com/
Montreal QC GPUG Chapter Leader
GP2013R2 / MR2012 CU14
——————————
——————————————-

[Loan Nguyen]

When you’re running AP Aging report, it’s better to choose GL Posting Date not by Document Date for Select Transactions For Report Using:

To minimize the wrong date being entered, you could require AP staff to run edit list and then check and correct any wrong dates.

Hope that helps.
Loan Nguyen

——————————
Loan Nguyen
XLN Accounting Solutions
Westminster CA
——————————
——————————————-