Custom task fields and task edit forms
Altus Tasks supports two task edit options from the task menu:
| Menu option | Purpose | Best used for |
|---|---|---|
| Edit | The out-of-the-box scheduler task edit experience. | Standard task and scheduling fields. |
| Custom Edit | A Dynamics-based task edit experience used where the standard Edit form cannot support the required field behaviour. | Advanced custom fields, business rules, formulas, workflows, or related/nested data. |
The Edit option opens the standard task edit form. This is the primary task edit experience for scheduler-supported task fields.
The Custom Edit option opens the Dynamics task edit form. This is used where organisations need to maintain more advanced custom task data that cannot be handled by the standard Edit form.
Why two edit forms exist
The standard Edit form is part of the scheduler experience. It supports standard task fields and basic supported custom fields, such as text, number, date, choice, lookup, or picker fields.
Some organisations extend the Task table with more complex configuration. These fields may need Dynamics behaviour that is not available in the standard scheduler edit form.
Examples include:
- Business rules
- Formula fields
- Calculated fields
- Workflow or Power Automate populated fields
- Related tables
- Nested tables
- Complex lookup behaviour
- Fields that require Dynamics form logic
- Fields that require users to select or maintain values from related data
Where users need to maintain this type of advanced custom task information, they should use Custom Edit.
Where users need to maintain standard scheduling information, they should use Edit.
Important: Scheduling fields must remain in the standard Edit form because they are managed by the scheduler. This includes start date, finish date, duration, effort, resource assignments, and dependencies.
Custom Edit is not a replacement for the standard scheduler edit form. It is an additional option for maintaining advanced custom task information that cannot be supported in the standard Edit experience.
Showing reference-only custom task information
Some custom task fields may be populated by another process or system and only need to be visible for reference. In these cases, the person configuring the task page may choose to show the value in the task grid or standard Edit form as a read-only field.
This approach may be suitable where:
- The field value is populated by another process, calculation, integration, workflow, or flow
- The user does not need to manually update the value
- The value is useful to see while reviewing or updating the task
- The field can be safely displayed as read-only
This approach is not suitable where the user needs to actively enter, select, or maintain the value. If the user needs to edit the field, and the field cannot be supported by the standard Edit form, use Custom Edit.
For example:
- A custom field is populated by another process, such as a calculation, workflow, flow, or integration.
- The value is exposed in a field that can be shown on the task grid or standard Edit form.
- The field is configured as read-only, so users can view the value but cannot overwrite it.
The more complex source field, related data, or supporting logic can remain on the Custom Edit form, or potentially be hidden, depending on how the field is updated and whether users need to interact with it.
Guidance by scenario
| Scenario | Recommended approach |
|---|---|
| User needs to update standard scheduling information | Use Edit. |
| User needs to update a basic supported custom field | Use Edit, where supported. |
| User needs to select or maintain values from related or nested data | Use Custom Edit. |
| Field is populated by another process and only needs to be viewed | Show the value in a read-only field in the grid or standard Edit form, where supported. |
| Field is populated by a workflow or flow and does not need user input | Consider whether the source field needs to be shown at all. |
| User wants one form for all task updates, including schedule fields and complex custom fields | Not supported. Scheduling fields must remain in Edit. |
Questions for development review
The following items need developer confirmation before this guidance is finalised.
1. Fields populated by another process
If a field is populated by another process, such as a workflow, flow, calculation, or integration, does the source field need to be visible on the Custom Edit form?
Or can it be hidden entirely, with only a read-only value shown in the grid or standard Edit form?
1a. Dependency on schedule values
Does the answer change if the workflow, calculation, or other update process depends on schedule values?
For example, if a schedule value changes in the scheduler, can the custom value update without the source field being visible on the Custom Edit form?
Summary
Altus Tasks includes a standard Edit option for scheduler-supported task fields, and a Custom Edit option for more advanced custom task data.
Use Edit for scheduling information and basic supported task fields. Use Custom Edit where custom fields rely on Dynamics behaviour, such as business rules, formulas, workflows, or related tables.
Scheduling fields must remain in the standard scheduler experience. Custom Edit is not intended to replace Edit.
Where custom task information only needs to be viewed, the value may be shown as read-only in the grid or standard Edit form, where supported. Where users need to actively maintain advanced custom task information, use Custom Edit.