Share
Report
5Hello,
I have a client who is trying to decide on how to best "split" the out-of-the-box Account Table so that distinct users only see/can edit what pertains to their role.
As an example, one role is for general sales (Sales Manager) and the other is for specific product sales (Product Manager). Both require access to the Account Table but only want to see their specific information in order to manage their pipelines and Opportunities separately while still having connections to common data elements like Activities and Products.
We have explored creating multiple Model Driven Apps based on Account Type that would only be accessible by the roles listed above but they thought that was too clunky. They then asked whether or not we should actually have two instances of CE with two separate Account Tables but I have basically refused to do that for the many obvious reasons that duplicating and keeping that data siloed would introduce (not to mention the additional costs and configuration/integration).
What are some best practices that I could leverage in order to explain this to them in a more palatable way? Or am I missing anything structural that would be "deal breakers" enough for them to adopt the Model Driven App approach (which is still what I believe we should do in the first place)?
Thanks in advance!
All responses (
Answers (
