Budget management functionality that FOLIO needs to stay competitive (UXPROD-3442)

[UIF-334] Duplicate entries in Transactions list in Finance app Created: 22/Apr/21  Updated: 03/Feb/22  Resolved: 03/Feb/22

Status: Closed
Project: ui-finance
Components: None
Affects versions: None
Fix versions: None
Parent: Budget management functionality that FOLIO needs to stay competitive

Type: Bug Priority: P3
Reporter: Doreen Herold Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: acquisitions, finances
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: File Finance app Duplicate Entry after clicking Load more.mp4    
Issue links:
Defines
defines UXPROD-3221 Thunderjet - Lotus Enhancements/Bugfixes Closed
Sprint: ACQ Sprint 133
Development Team: Thunderjet
Release: Lotus R1 2022
Affected Institution:
Lehigh
Tester Assignee: Dennis Bridges
Epic Link: Budget management functionality that FOLIO needs to stay competitive

 Description   

Overview: A long results list of Transactions in the Finance app prompts using the "Load more" button and sorting by "Amount" to find the desired entry. A duplicate entry is seen though it does not seem to be a duplicate in the database, just a duplicate in the results list. This experience has not been able to be consistently reproduced; however, it has been seen more than once.
Steps to Reproduce:

  1. Log into FOLIO environment as User X
  2. Click the Finance app
  3. Click a Fund
  4. Click Actions -> View transactions for current budget
  5. Click column header "Amount"
  6. Scroll to bottom of list and click "Load more" (we needed to perform this step more than once
  7. Review list for duplicate entry

.mp4 file is included to see an example of this experience

Expected Results: a single entry for each transaction should appear
Actual Results: a duplicate entry has appeared. This experience is not consistent.



 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 04/Oct/21 ]

Hi Dennis Bridges I found this over on the FOLIO project and moved it to UIF. Probably needs review to see if it's still reproducing.

Comment by Dennis Bridges [ 04/Oct/21 ]

Could this be related to the invoice duplication issue we recently discussed with Mikita Siadykh? If we continue to use the load more component is it possible this issue persists for transactions. The difference here is that I wouldn't think multiple users could be impacting a single transaction at the same time. Maybe an encumbrance I suppose. Makita what do you think?

Comment by Mikita Siadykh [ 05/Oct/21 ]

Dennis Bridges it can be the same issue, it's possible to fix on UI side, but based on attached video there is a chance BE returns duplicated rows in one portion

 

can we have the API responses with duplicated items to identify root cause?

Comment by Doreen Herold [ 06/Oct/21 ]

Hi Mikita Siadykh! I had reported this issue and will help as much as I can. You had asked for the API responses. I'm so sorry–I don't know about API responses and how to provide them. I'd be interested in learning and helping if you could provide me with details on how but I understand if it might be too time consuming to explain. If it would help to get on a video call, I can do that.  

Comment by Mikita Siadykh [ 07/Oct/21 ]

hi Doreen Herold

if you still can reproduce it and show, yep we can have a call

Comment by Dennis Bridges [ 02/Feb/22 ]

Hi Doreen Herold, we are having trouble reproducing this issue and we believe it is because the app now uses paginated lists. Are you still observing this issue? If not, I will resolve this ticket. thx!

Comment by Doreen Herold [ 03/Feb/22 ]

Hi Dennis Bridges! It looks like everything is fine. We don't have pagination for long lists (we might not be on that version yet or I could be overlooking it). But I don't see any examples of this being a problem. Thank you for checking back in!

Comment by Dennis Bridges [ 03/Feb/22 ]

No problem, thank you for bringing this to our attention Doreen Herold. Closing as can not reproduce.

Generated at Thu Feb 08 23:25:50 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.