This is caused by an Administrator having previously created a Custom Field, via the Programme Builder, with the same name as an already existing field. Unfortunately, we are unable to remove these fields completely from the system, although functionality has since been introduced into the product to stop such fields from being created.

If requested, Aptem Support can label unused duplicate fields with a *Do Not Use* post fix, which can help to easily identify which fields should or shouldn’t be used.