I have a workspace that builds areas from boundary lines. If it encounters any areas that can't be built, the boundary lines for that area are written to a separate feature class table. I've set the writer to INSERT and I've set the error table to Truncate Table First: Yes.
It all works fine, the error table is emptied and the new errors written. However, when the process completes successfully and no errors are written to the error table, the error table isn't truncated. As a result, the errors from the last run in which errors were detected are still found in the error table.
What is the best workaround to ensure that the error table is empty when no errors are encountered?
This will pass the first feature to sqlExecutor which has truncate table statement with DB credentials as parameters. After truncating all the features will go to processing as per the work bench.
