Bug #23784
closed
FWG: Staging: Web app: Transaction: Log Feeder: Not getting the proper data in Export file in below 2 sceanrios.
0%
Description
On Transaction Log Not getting the proper data in export file in below 2 scenarios:
1. After opening the Log Feeder 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 48 where as in Excel file its displaying total rows as 236)
2. After opening the Log Feeder page 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 34 where as in Excel file its displaying total rows as 236)
Updated by Palash Tembhurnekar about 1 month ago
- Tags changed from staging to InternalBugs
Updated by Dinesh Pedagada
Updated by Palash Tembhurnekar 29 days ago
1. After opening the Log Feeder 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 48 where as in Excel file its displaying total rows as 236) -Fixed
2. After opening the Log Feeder page 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 34 where as in Excel file its displaying total rows as 236) - Fixed
Verified on staging web app, now on the Log Feeder page the data is now exporting properly based on the applied filters, selected columns, and search. Done, Marking it as closed.