Cannot Reproduce
Details
Assignee
Oleksandr BozhkoOleksandr BozhkoReporter
Tatsiana HryhoryevaTatsiana HryhoryevaLabels
Priority
P3Story Points
1Sprint
NoneDevelopment Team
FirebirdRelease
Sunflower (R1 2025)RCA Group
TBDTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Oleksandr Bozhko
Oleksandr BozhkoReporter
Tatsiana Hryhoryeva
Tatsiana HryhoryevaLabels
Priority
Story Points
1
Sprint
None
Development Team
Firebird
Release
Sunflower (R1 2025)
RCA Group
TBD
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created November 5, 2024 at 8:57 AM
Updated January 28, 2025 at 7:42 AM
Resolved January 23, 2025 at 9:48 PM
Overview:
Bulk edit of MARC fields for the large amount of records (~100.000) takes time to commit changes. In current implementation while committing changes UI requests are sent to check if DI job was completed. As the result, bulk edit job can’t be completed without User to have Confirmation screen opened while committing changes.
The issue was reproduced when for the large number of records (82.345) bulk edit of MARC fields was done. “Commit changes“ button was clicked, and after some time User saved the link to open “Confirmation screen“ and switched off the computer. On the next day when User opened saved link - only then bulk edit job was completed after some time
Steps to Reproduce:
Go to “Bulk edit“ app
Select “Inventory - instances“ record type
Select “Instance UUIDs“ record identifier
Click “or choose file“ button => Upload file with large amount (~100.000) of MARC Instances UUIDs
Click “Actions“ > “Instances with source MARC (POC)“
Select any options/actions to edit MARC fields of Instance records (e.g. add 500 field)
Click “Confirm changes“
Click “Commit changes“
Expected Results:
Bulk edit job is completed in background without User to have Confirmation screen opened while committing changes
Actual Results:
Bulk edit job is not completed without User to have Confirmation screen opened while committing changes
Approach:
There are 2 possible ways how to avoid this problem.
Workaround. Implementing polling mechanism to retrieve status of importing until it will be completed. And automatically start preparing preview after importing completion.
Right way. Implement notification mechanism on data-import side and handle notification on mod-bulk-operations side to start preview preparation.