What We Fixed
When editing forms, if you deleted a field that had been mapped to a CRM property, the old mapping could stick around in the background. Later, when you tried to publish the form, you might see a confusing “duplicate mapping” error even though your form looked correct.
What Changed
- Orphaned field mappings are now automatically cleaned up when you delete fields from a form
- This includes fields inside nested sections
- Publishing forms now works smoothly without false duplicate mapping errors
Thank you for reporting this issue!