Key columns in integration job fails with false "disable" error #552
Description
Summary
When creating or editing an integration job in DynamicWeb, setting a mapping as a key column sometimes fails with an incorrect error message claiming the user is trying to disable a key column, when they are actually trying to create/enable one.
Steps to reproduce
- Create or edit an integration job with 2 key columns 2. Try to add or remove a key column mapping
- Click save
Expected: The key column mapping is saved successfully.
Actual: An error message appears saying the key column cannot be disabled — even though the user is trying to enable/create it.
Additional context
- The bug is intermittent — it doesn't reproduce consistently.
- A workaround exists: recreate the integration job from scratch.
- The bug also occurs when removing one of two existing key columns.
Screenshots
