In a normal production environment, you would never want to delete a version set. If you accidentally delete a version set, there is no recovery plan in place.
If you delete the only version set associated with an indexed data file, you would no longer be able to view those documents.
If there are several version sets of a view and you delete the latest one, eaDirect uses the view published previous to the version set you deleted, which can result in the online statement being formatted incorrectly.
Warning: It is recommended that you not delete a version set for any reason, including when archiving old data. The only possible reasons you might want to delete a version set is when you know you made a mistake in publishing it, you are archiving old data (which removes references to the statements in the index) and the version set is associated with that old data, or you are working in a test environment. Be extremely careful if you choose to delete a version set for any reason. Deleting a version set deletes the version set files and any references to the version set in the database.
1. Click Delete on the Publisher menu. The Delete a Version Set screen appears.
2. Choose the application and job type associated with the version set you want to delete.
3. Click Yes if you want to delete the latest version set, or enter a date to display the last version set published before that day.
4. Click Search. If Publisher finds the version set, it displays the list of the design files in the set.
5. Click Delete Version Set.
6. eaDirect prompts you to verify that you want to delete the version set. Click OK. eaDirect lets you know if the deletion was successful.