Status: Open (View Workflow)
During data import testing in PTF, we came up with a PostgreSQL query that will give all instanceId that does not have any holdings and items. This will be helpful to troubleshoot and create holdings and items for those instances with missing holdings and items.
This is just an example - below Postgresql query gives all instanceIds that does not have any holdings and items. This Postgresql query will be different for different job profiles.
select id as instanceId from fs09000000_mod_inventory_storage.instance ins where creation_date > '2021-04-01 15:00:00.00+00' AND not exists ( select jsonb->>'instanceId' from fs09000000_mod_inventory_storage.holdings_record hr where hr.instanceId=ins.id);
My point is we should show these failed instances in UI logs which will be helpful in troubleshooting.
So in data import, when you select the filename which open logs in UI, should first show all failed instance with details as to why it failed. This feature will be helpful when loading large data import jobs such as 50K, 100K or 500K. That way, we don't have to find a needle in a haystack.
- Data import UI log shows failed instance, holdings, items after data import job fails or completes with an error
UXPROD-3363 Data Import Log - refine error handling, part 2