Challenges with multi-org shared tables
Refer to Product Ideas
Within multi-org environments, many configuration tables are shared by all organizations. Occasionally this can result in conflicts between orgs.
Harvard University recently onboarded the Treehouse Convention Center as a new organization in Enterprise. Unlike other groups at Harvard (which focus on internal events), Treehouse has a Sales team for external events. As such, they need to track the Sales Pipeline very closely with Event Statuses. During implementation, they added 5 new Event Statuses to the list. They were unaware that Event Status is a shared table between orgs.
After the statuses were added, other Orgs complained that these changes resulted in disruptions to reporting and created confusion in team processes.
Does anyone know if it is possible to obfuscate statuses from specific users/roles/orgs in order to mitigate these challenges?
Do we have any plans to improve controls over shared tables between Orgs?
-
Anthony Costantino and Martin Wooding can you share your thoughts here
-
No it's not possible. My suggestion would be to use another field as a sales status, and keep the original statuses.
-
Thanks Martin Wooding
Martin Stephens could you submit a Pendo enhancement request and post here for reference
-
Seth Halvaksz Submitted. I did not see a ‘Product Area’ for Multi-Org, so I put this with Enterprise Sales & CRM. We might want to consider a Multi-Org product option.
The Event Status field is one of the most problematic multi-org fields, however their are many others. For example, Contract Lists are also shared between orgs, which is almost never required.
Ideally, for multi-org clients, we would have the option to hide/show items on shared lists between orgs.
-
Thanks Martin. I think the Sales & CRM product area is appropriate.
Noting the link to enhancement request for reference:
Please sign in to leave a comment.
Comments
5 comments
Date Votes