-
Type: Testing Defect
-
Status: Done (View Workflow)
-
Priority: Major
-
Resolution: Won't Fix
-
Affects Version/s: CFA 2019R2
-
Fix Version/s: None
-
Component/s: customerSales
-
Labels:
-
Sprint:CFAMX 2019R3 Sprint 2
When an invoice that has a Collection applied has been marked as Uncollectible from the Customer Management page and then the user unapplies the Collection from the Collected Sales page, the Invoice status of Uncollectible is removed (unchecked on the History page). This should not happen. The logic should simply remove the collection and leave the Invoice as Uncollectible
Reproduction Steps
- Login to MXC and navigate to Customer Management for store 00642 in testing on April 4
- Search for Franko's Pizza
- View History and make sure they are not marked as uncollectible
- Navigate to Collected Sales page
- Change date to April 4
- Search for Franko's Pizza
- Apply a collection to 1 of the invoices
- Navigate to MXC Customer Management and view the History for Franko's Pizza
- Mark both Invoices as Uncollectible
- Navigate back the Collected Sales page
- Change the Date to April 4
- Search for Franko's Pizza
- Unapply the Collection from the one invoice displayed
- Navigate back to Customer Management History
- View Franko's Pizza
Expected Results
- Both Invoices should be checked as Uncollectible. Unapplying a Collection should not drive the Uncollectible being unchecked
Actual Results
- An Invoice is now displayed as unchecked as Uncollectible
Notes from Stacy Privalova
I was able to reproduce using Franco's pizza account with following steps:
- Remove Uncollectible flag from both invoices in History page
- Apply collected sale from Collected Sales to one of the invoices
- Mark both Invoices as Uncollectible in History page
- Un-apply collected sale from Customer sales page
- Go to History, the invoice that had a payment un-applied doesn't have Uncollectible flag checked
- Clones
-
CFAMX-3727 Uncollectible Invoice logic when Collection is Unapplied
- Done