Adding a relational transformation with an existing field name stops transformation manipulation

After adding a schema field with the same name as an existing field using a relational and date relational transformation, I was unable to modify any transformations, with the reason being "An item with the same key has already been added". Manually removing the transformation from the config and restarting the service resolved the issue.