Hello team!
Currently there’s no clear-cut way to replace or remove deactivated users in multi-select user properties in bulk from the index view.
Removed/deactivated users don’t appear in the value picker.
See the screenshots below for reference:
Hey @Naarias,
Thanks for posting in the Community!
I’m not seeing any documentation of a means by which we can bulk remove these deactivated users from user properties in the index page, so I’d like to tag in @TomM2, @Ben_M, and @GRajput. Do any of you have knowledge on how this can be achieved?
Shane, Senior Community Moderator
This is a known gap in the UI. The value picker for user properties only surfaces active users, so deactivated users become invisible in bulk edit even though their values still exist on records. There’s no native way to clear them from the index view.
The workaround that might work is by using a workflow. Set the enrollment trigger to the property containing the deactivated user, then use a “Clear property value” action to wipe it, or a “Set property value” action to replace it with an active user. You can enroll existing records in bulk by using the re-enrollment trigger on your full contact or company list.
The other route which I persoanlly recommend is the API. A PATCH request to the CRM objects endpoint lets you set the property value to null or to a new user ID across records programmatically. If the volume is large enough, this is cleaner than the workflow approach.
This is just a Ui limitation not a data limitation
Thanks @STierney and @Abhishek_Singh for your replies.
I realized “replacing” current values with a deactivated/removed user won’t really make sense, so you can dismiss that from my original ask.
That being said, the issue still arises with the “Remove from current value(s)” option. Inability to select deactivated/removed users prevents you from removing them without incurring one-by-one manual work or clearing the entire property, which results in losing all other selected values.
The possibility to show deactivated and removed users already exists when filtering, for example:
Is there a way to propose this as a UI-based feature update? If so, is this the right channel to do so?
Hey @Naarias,
Great follow-up question! We actually recommend posting ideas directly in our Ideas Forum. This would allow other users to upvote your idea, expand on it, and present the need directly to our Product team. If you do so, please feel free to post the URL to your idea directly in this thread so that we can start upvoting it for you!
Shane, Senior Community Moderator