Can anyone tell me what the purpose of the following code is when doing a payment journal:
OnValidate - Shortcut Dimension 1 Code
TESTFIELD("Check Printed", FALSE);
I don't mean the literal purpose, as in what does TESTFIELD do. I mean why is it there. The check has been printed, but the journal is not posted. It doesn't look like any ledger entries have been created. I checked Bank, Vendor, and G/L.
Why can't I change a dimension after a check has been printed? Looking for a reason not to comment it out, or at the very least not execute for a payment journal. Thanks.
Comments
RIS Plus, LLC
My Blog - nav.education
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
I can understand limiting the majority of the fields, but this one seems wrong. Any other ideas?
My Blog - nav.education
I agree with you if you're only going to be changing dimensions. But I wouldn't make ANY changes on the Gen. Journal Line table.
We use 2 options when we run into dimensions with Checks:
1. Modify the check report so the dimensions are checked before printing.
2. If no modification, then ask the client to simply void the check, update the dimension code, then reprint the check on blank paper (assuming they printed the checks on check paper).
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book