{"id":45994,"date":"2020-07-14T13:11:39","date_gmt":"2020-07-14T20:11:39","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/?p=45994"},"modified":"2020-11-17T13:37:38","modified_gmt":"2020-11-17T20:37:38","slug":"batch-class-with-global-document-type-failing-import","status":"publish","type":"post","link":"https:\/\/ephesoft.com\/docs\/batch-class-with-global-document-type-failing-import\/","title":{"rendered":"Batch Class with Global Document Type Failing Import"},"content":{"rendered":"
Applies to:\u00a0<\/strong>Ephesoft Transact 2020.1 and above<\/span><\/p>\n If you are importing a batch class that creates or updates global document types in the global batch class, the import process will fail if there is a local document type in the Global Batch Class (BC0).<\/span><\/p>\n The following error message will display:<\/span><\/p>\n \u201cThe import process has been aborted because the existing global batch class contains a local document type with the same name as an imported global document type. To fix this problem, change the local document type in the global batch class to a global document type, or use the Import as Local Batch Class option.\u201d<\/span><\/p>\n Important<\/strong>: This error message is incorrect. Perform the following steps to resolve the error.<\/span><\/p>\nIssue<\/strong><\/span><\/h2>\n