C360 Attributes: Allow ability to filter at the field level
None
Our managers assign CSMs manually, based on workload, and we have a user lookup field on C360 from which they make the assignment. Unfortunately, every user shows up in that list. It would be great if we could filter that field so that only users with a specific profile are displayed. This would likely be valuable for other fields as well.
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
I am not sure if I understood this completely. Can you attach some screenshots of where you need the filter?
Regards,
Jitin
In example below Julie Richards is a CSM - the other 3 are not. I'd like to be able to restrict this list to only users that have a specific profile:
Is it possible to add a filter to the C360 layout?
Additionally, inactive users show in the field as well. So we need the ability (in Salesforce edition as well as NXT) to be able to filter users out as appropriate.
We tried leveraging Salesforce field filtering, but the users still show up in the search list:
@andrew_biehle - I forgot I already posted this to the community a few months back.
Hello Everyone!
Happy to announce that your request has been considered and included as part of the v6.11 release (Feb). Admins can now select Lookup Fields when configuring filters for the R360 Attributes section, to better control the type of data displayed within the R360.
You can find the relevant information in our v6.11 Release Notes.
This feature is implemented only in the SFDC version.
Thanks for posting!
Hello@shannon ,
The issue where users were not able to access the editable fields is not related to this functionality. It is all together a different issue which has been fixed. Please try checking it now. Let us know in case you are still facing it.