While it's not ideal, the following workaround is available for user fields
Requirements: Have a static user account that can be used as a temporary assignee in a user field. Add secondary custom user field to layout of record you are wanting to modify. I've added an "Automations" tab to my records to accomplish this and made this field read-only on that tab. In order for a custom field to be used in an automation - it MUST be on the associated record's layout.
Configure the following automation actions:
Update Field [TEMP CUSTOM USER FIELD] add [STATIC TEMP ACCOUNT]
Update Field [TARGET CUSTOM USER FIELD] to be the same as [TEMP CUSTOM USER FIELD]
Update Field [TEMP CUSTOM USER FIELD] remove [STATIC TEMP ACCOUNT]
Update Field [TARGET CUSTOM USER FIELD] remove [STATIC TEMP ACCOUNT]
Update Field [TARGET CUSTOM USER FIELD] add [TARGET USER]
Summary: This set of automation actions will set a single known user in a temporary field and then mirror the target user field after the temporary field; essentially wiping any unknown users out of the field and setting the target user field to include only the single known user. You then remove the single known user out of both fields; rendering both fields blank for re-use and/or assignment of one or more users.
We have this issue as well ... we have a multi-value single-select custom field that I can't clear via automation, i can only set it to one of the pre-defined values.
We have a custom field that we utilize for the assigned individual to respond yes, no, or partial to completing the feature within the aspirational release. we would like to have an automation that cleared this field whenever it was moved to a different release for those features that have a response of no. Right now we can only select one of yes, no, or partial but cannot clear the field entirely to reset it for next iteration.
While it's not ideal, the following workaround is available for user fields
Requirements:
Have a static user account that can be used as a temporary assignee in a user field.
Add secondary custom user field to layout of record you are wanting to modify. I've added an "Automations" tab to my records to accomplish this and made this field read-only on that tab. In order for a custom field to be used in an automation - it MUST be on the associated record's layout.
Configure the following automation actions:
Update Field [TEMP CUSTOM USER FIELD] add [STATIC TEMP ACCOUNT]
Update Field [TARGET CUSTOM USER FIELD] to be the same as [TEMP CUSTOM USER FIELD]
Update Field [TEMP CUSTOM USER FIELD] remove [STATIC TEMP ACCOUNT]
Update Field [TARGET CUSTOM USER FIELD] remove [STATIC TEMP ACCOUNT]
Update Field [TARGET CUSTOM USER FIELD] add [TARGET USER]
Summary:
This set of automation actions will set a single known user in a temporary field and then mirror the target user field after the temporary field; essentially wiping any unknown users out of the field and setting the target user field to include only the single known user. You then remove the single known user out of both fields; rendering both fields blank for re-use and/or assignment of one or more users.
We have this issue as well ... we have a multi-value single-select custom field that I can't clear via automation, i can only set it to one of the pre-defined values.
We have a custom field that we utilize for the assigned individual to respond yes, no, or partial to completing the feature within the aspirational release. we would like to have an automation that cleared this field whenever it was moved to a different release for those features that have a response of no. Right now we can only select one of yes, no, or partial but cannot clear the field entirely to reset it for next iteration.