Bug #23782
closed
FWG: Staging: Web app: Transaction Log: Export: Not getting the proper data in Export file In below 2 scenarios.
Added by Palash Tembhurnekar 2 months ago.
Updated about 1 month ago.
Start date:
January 30, 2025
Description
On Transaction Log Not getting the proper data in export file in below 2 scenarios:
1. After opening the Transaction Log page, without applying the filter directly clicked on the Export button to export the data. Later when opened the downloaded file then found that its displaying Incorrect data. (In Web app its displaying total rows as 806 where as in Excel file its displaying total rows as 813)
2. After opening the Transaction Log applied the filter of Current Holding Check as Yes & clicked on the Export button to export the data. Later when opened the downloaded file then found that its displaying Incorrect data. (In Web app its displaying total rows as 713 where as in Excel file its displaying total rows as 813)
- Description updated (diff)
- Tags changed from staging to InternalBugs
- Status changed from New to In Progress
- Status changed from In Progress to Resolved
1. After opening the Transaction Log page, without applying the filter directly clicked on the Export button to export the data. Later when opened the downloaded file then found that its displaying Incorrect data. (In Web app its displaying total rows as 806 where as in Excel file its displaying total rows as 813) - Fixed
2. After opening the Transaction Log applied the filter of Current Holding Check as Yes & clicked on the Export button to export the data. Later when opened the downloaded file then found that its displaying Incorrect data. (In Web app its displaying total rows as 713 where as in Excel file its displaying total rows as 813) - Fixed
Verified on staging web app, now on the Transaction Log page the data is now exporting properly based on the applied filters, selected columns, and search. Done, Marking it as closed.
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Go to top