A customer sets up a calculated field on a request form. A user manually converts the request to a project and selects a template from the available active templates. How should the administrator configure the Project custom form to make sure the value is passed to the project on conversion?

When converting a request to a project in Adobe Workfront, data from custom forms can be automatically mapped if the fields on both the source (request) and destination (project) custom forms share the exact same name. For a calculated field, the value is computed on the request form. To transfer this computed value to the project, the corresponding field on the project's custom form must exist with the same name but without a calculation. This ensures the project field acts as a container to store the static value passed from the request, rather than recalculating and overwriting it.

A. Add a new field with the same name but make it a text field. This is incorrect because changing the field type can lead to data type mismatches and is not the standard procedure. The field types should match for proper data transfer.
B. Add the same field will a different calculation. This is incorrect because any calculation on the destination project field will execute upon project creation, overwriting the value that was passed from the request.

1. Adobe Experience League Documentation - Transfer custom form data when converting an issue:

Section/Content: The documentation, while referencing issues, outlines the identical principle for requests. It states, "To transfer information stored in a calculated custom field, you must add the same field to a custom form on the other object, but you must remove the calculation. Otherwise, the calculation of the field on the project or task overwrites any information transferred from the issue."

Source: Adobe Workfront Documentation, "Transfer custom form data when converting an issue," in Create and manage issues.

2. Adobe Experience League Documentation - Add a custom form to an object:

Section/Content: This document explains the fundamentals of custom forms and fields. The behavior described in the question is a specific application of how custom fields interact during object conversion, a core concept in Workfront system administration. The principle of matching field names for data transfer is a foundational element of this process.

Source: Adobe Workfront Documentation, "Add a custom form to an object," in Create and manage Custom Forms.