AGFs associated with retired features and migrated through a template fail to run

Problem or error: This problem can occur if generated fields (previously known as Affinium Generated Fields) are associated with features that have been retired in Unica Campaign. If the generated fields are used in a migrated template, the template does not run successfully.

Solution: The references to the AGFs in the template continue to exist in the new environment, but must be modified to reference current objects for the templates to run successfully.

For example, if tracking codes from Unica Campaign 6.x are referenced in a derived field calculation, that derived field must be modified to use the new treatment code or modified in some other way to remove the reference to obsolete tracking codes. Likewise, if the tracking code or any other retired AGF is mapped to an output field for a vendor file or to contact history, the retired AGF must be removed and replaced with a different field before the template can run successfully.