+2Hi Everyone,
I am curious to know what people’s best practices are for having multiple CSM’s or resources on 1 R360. The situation is the exception and not the rule in our environment. I do not want to create additional fields to capture the resource name as that will cause havoc on reporting, etc. If you have a solution in place, I would love to hear everyones’ ideas. TIA Jessica
+1There is no other solution to do. You have to add additional fields.
Your only other solution is to duplicate the Relationship multiple times, but that in itself will cause problems.
Having a Team Member object would be ideal. And yes sure you can create that concept. However, that will cause issues when you go to dashboard/report filters and displaying them.
+13There is no other solution to do. You have to add additional fields.
Your only other solution is to duplicate the Relationship multiple times, but that in itself will cause problems.
Having a Team Member object would be ideal. And yes sure you can create that concept. However, that will cause issues when you go to dashboard/report filters and displaying them.
This is exactly it. Just have multiple lookups to the User object. It will be easier rather than harder to report on, to be honest. We’ve got multiple types of CSMs on the Company and then different Relationship Types (which could be an option but still causes equivalent difficulty/complexity).
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.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
