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
Best answer by Wayne
There 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.