Which action is necessary to pass a calculated value from a custom form to a project?

Question

Options

• AEnable auto-save on the form
• BUse mapping fields
• CModify group permissions
• DAdd a dependency to the project task

• A
  7% (3)
• B
  78% (35)
• C
  2% (1)
• D
  13% (6)

Explanation

Mapping fields (B) act as the bridge between a custom form and a project - they define which form field values get transferred to which project fields. Without mapping, calculated results stay isolated in the form and never reach the project record.

Why the distractors are wrong:

• A (Auto-save): Controls when form data is persisted, not where it goes - saving a form doesn't route values to a project.
• C (Group permissions): Governs who can access or edit records; it has no role in moving data between a form and a project.
• D (Project task dependency): Manages task sequencing/prerequisites, unrelated to data flow from a form.

Memory tip: Think of mapping fields as "address labels" on a package - without the label telling the system where the calculated value should land in the project, the data goes nowhere.

No community discussion yet for this question.