Actions templates in Dashpivot have a fixed structure that the workflow engine depends on — they require exactly 3 specific fields in a set order: a Person (Assignee) field, an Action Due Date field, and 2 Approval Signature fields.
This article explains every error you may see when that structure is missing or out of order.
"Actions templates require exactly 2 approval signatures."
Why this happens
The Actions template must contain exactly 2 Approval Signature fields to function correctly — one for each stage of the action workflow. Having fewer or more than 2 will block saving. The two signatures map to the two stages of the action workflow: one for the person raising the action and one for the person closing it. Having fewer or more breaks the workflow engine.
How to fix it
Add or remove Approval Signature fields until there are exactly 2 in the template.
"Assignee field must appear before the first approval signature."
Why this happens
The Actions workflow engine reads fields in order — it expects to know who the action is assigned to before the first approval stage is reached. If the Assignee field appears after the first Approval Signature, the workflow can't correctly associate the assignee with the action.
If the template is also missing the correct number of approval signatures, this error may fire at the same time. Fix the signature count first, then recheck field order.
How to fix it
Drag the Assignee field to a position above the first Approval Signature field in the template.
"Due Date field must appear before the first approval signature."
Why this happens
The Due Date must be captured before the first approval stage so the workflow engine can enforce deadlines and trigger expiry notifications correctly. If it appears after the first Approval Signature, the workflow can't associate the due date with the action at creation time.
Same as above — if the signature count is also wrong, fix that first before rechecking order.
How to fix it
Drag the Due Date field to a position above the first Approval Signature field.
"Actions templates can have only one Action Due Date field."
Why this happens
Only one Action Due Date field is allowed per Actions template. A duplicate was detected.
How to fix it
Remove the duplicate Action Due Date field.
"Action Due Date field must also be an Expiry Date field."
Why this happens
The Action Due Date field requires the Expiry Date option to be enabled in its field settings.
How to fix it
Open the Action Due Date field in the template editor → go to Field Settings → enable the Expiry Date toggle. The field must function as both an Action Due Date and an Expiry Date simultaneously.
If the issue continues
If the template still won't save after following the steps above, check that the required fields haven't been renamed or replaced with a similar field type — for example, a plain Date field instead of an Action Due Date field, or a regular Signature instead of an Approval Signature. If you're still stuck, contact Sitemate support with a screenshot of the error and a link to the template.
Related articles: