I've got a client with an odd thing going on. For a long time now they've been using "External Document No." to store customer payment data (seems to be credit card type and last 4 digits).
They've recently upgraded to 5.0 sp1 and now, when they do a bank rec., it is grouping all payments by matching External Document No.'s (customer credit cards) into one line, with a document no. = external document no.
Besides checking if the External Doc. No. is mandatory or not, I wasn't aware of that field really doing anything at all.
Any reason this is happening, any way of turning it off?
Thanks in advance!
0
Answers
here is the code in our database to stop the bank rec lines from being collapsed which is the standard, I am not the programmer, but the end user, and we had the same problem this was the fix from our solution center. I think back in 2.0 you had an option to set somewhere on collapse or expand, and then in 4.0 it went away and it defualted to collapse lines. we discoved the problem, when we upgraded to 4.0 from 2.0. al the sudden our bank rec were a nightmare.
IF RecordTypeToProcess IN [RecordTypeToProcess::Both,RecordTypeToProcess::Deposits] THEN BEGIN
Window.OPEN(Text008);
WITH BankRecLine DO BEGIN
RESET;
SETCURRENTKEY("Bank Account No.","Statement No.","Record Type");
SETRANGE("Bank Account No.","Bank Rec. Header"."Bank Account No.");
SETRANGE("Statement No.","Bank Rec. Header"."Statement No.");
SETRANGE("Record Type","Record Type"::Deposit);
SETRANGE("Collapse Status","Collapse Status"::"Expanded Deposit Line");
IF FIND('-') THEN
REPEAT
BankRecLine2 := BankRecLine;
CollapseLines(BankRecLine2);
UNTIL NEXT = 0;
RESET;
END;
Window.CLOSE;
END;
@themave - This sounds like what's going on, thanks for the pointer.
We've just discovered the Expand/Collapse functionality(Line -> Expand Deposit Line), this appears to be exactly what the user wants
Thanks for the help!