1.0.2025.0001

🐛 Bug Fix: RunAfterObjectExport now fires on delete exports (#31)

This release resolves an issue where post-export scripts (RunAfterObjectExport) were not executed during delete operations.
Previously, when objects were deleted, the export process would skip the post-export step, preventing any configured stored procedure or follow-up logic from being called.

🔧 What’s Changed

• Fixed the delete export path in Sql.MA.ExportDetached to ensure that RunAfterObjectExport executes for all modification types:
  • Add
  • Update
  • Delete ✅
• The export process now consistently triggers any defined post-export logic even after deletions.
• No configuration or schema changes are required.

💡 Why It Matters

Many SQL MA implementations rely on the post-export script to perform cleanup tasks, audit logging, or cascading updates after records are removed.
With this fix, those actions now run correctly for deletions as well, keeping behavior consistent across all export operations.

🧪 How to Verify

1. Configure a RunAfterObjectExport stored procedure that logs its execution.
2. Perform an export operation that deletes one or more connector space objects.
3. Confirm the stored procedure is invoked and logs the deletion event.

🙌 Thanks

Thanks to @mvaneijken for identifying and reporting the issue #31