Could we please have the option to remove the Company Lookup on the User object. Our Users (i.e. SF licence holders - we use the connector to bring them in) are not related to a company in Gainsight, but when using reports any of the user related fields such as Created By, Modified By, Owner all have lookups to Company so if I search for a company field they also all come up, this is quite confusing and is a blocker to me opening up access to reporting to additional persons in the business (that are not aware of object structure etc) as they can easily pick the wrong field and get no results.
TBF this probably goes for other system/standard objets and fields - we should at least be able to choose to hide them in reporting (e.g. if we’re not loading anything to them).
Remove Company Lookup on User object
None
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.
Hi@HollySimmons ,
Let me know, if my understanding is correct. Because of standard and System lookups created, is it difficult for you to choose the right fields especially when the Custom lookups to same objects are defined?
If the above is true, we have some plans in the roadmap for the capability to edit certain attributes for our Standard and System fields. We will also check if we can also include the ‘hide in reporting’ attribute as well.
Thanks
Hi@soumitrasahu , yes because there is a lookup to company from the user object;
then in reports I can end up picking a field from the company associated to a user, but these will always be blank as we don’t associate our users (which are our internal staff) to companies.
thanks
Hi@HollySimmons ,
Thanks for the explanation. We have got the idea you have mentioned here. The post has been moved to ‘Under Consideration’.
but the side effect would be they ( SF license holder group ) cannot report on company as a standalone object. ( is that acceptable )
but the side effect would be they ( SF license holder group ) cannot report on company as a standalone object. ( is that acceptable )
FYI@darkknight and @zach_davis
but the side effect would be they ( SF license holder group ) cannot report on company as a standalone object. ( is that acceptable )
FYI@darkknight and @zach_davis
I agree with@bradley here. Couldn’t this be handled with field level permissions?
but the side effect would be they ( SF license holder group ) cannot report on company as a standalone object. ( is that acceptable )
FYI@darkknight and @zach_davis
I agree with@bradley here. Couldn’t this be handled with field level permissions?
Question
For each object + group, which lookups they have access too.
n@bradley - Wouldn't it become to granular to manage
Question
For each object + group, which lookups they have access too.
Hey@Azad great question, thanks for asking. To some extent you are correct, however, I would posit that isn’t inherently a bad thing.
Is there a way this could be designed so that admins can configure reports with as much, or little, granularity that they need? I think flexibility in complexity level would serve more orgs better, than trying to design to the lowest common denominator.