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

Matthew Clark 12 years ago updated by anonymous 9 years ago 4

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.

Assigned to Tony as discussed.

Assigning fix version

This has been confirmed complete locally and can be closed on the next regression test.

This has been confirmed in the latest installation on prdgrp-test3, and additionally in the past set of regression tests.