{"id":50601,"date":"2022-03-16T09:34:15","date_gmt":"2022-03-16T16:34:15","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/?p=50601"},"modified":"2022-03-16T12:20:44","modified_gmt":"2022-03-16T19:20:44","slug":"updating-batch-instance-as-deleted","status":"publish","type":"post","link":"https:\/\/ephesoft.com\/docs\/updating-batch-instance-as-deleted\/","title":{"rendered":"Updating Batch Instance as Deleted"},"content":{"rendered":"
Applies to: <\/strong>Transact all versions<\/em><\/p>\n Updating the batch instances as DELETED in the Ephesoft <\/strong>database will cause duplicate jobs to be generated as NEW.<\/p>\n To expedite the deletion of batch instance jobs, users can update the batch_status<\/strong> column of the dbo.batch_instance<\/strong> table from the Ephesoft<\/strong> database with the condition of last_modified<\/strong> date.<\/p>\n Sample query:<\/strong><\/p>\n UPDATE Ephesoft.dbo.batch_instance<\/strong><\/p>\n set batch_status = ‘DELETED’<\/strong><\/p>\n WHERE last_modified < ‘2021-12-31 23:59’<\/strong><\/p>\n This will automatically update the selected batches chosen by the SQL script in the Ephesoft UI as expected. However, it will also cause the same batch instances to be recreated as NEW batch instance jobs.<\/p>\n To bypass this from happening, perform the following before running the UPDATE script or manually updating the batch_status<\/strong> column for individual batch instances to DELETED:<\/p>\n Note:<\/strong> Doing both of these actions before updating the SQL database table will ensure that you do not see any duplicate jobs.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Applies to: Transact all versions Updating the batch instances as DELETED in the Ephesoft database will cause duplicate jobs to […]<\/p>\n","protected":false},"author":93,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12382],"tags":[1430],"yoast_head":"\n<\/a>User Instructions<\/h2>\n
\n