Fail to create a new territory if Default Internal Access is more open than Default External Access
Last updated 2022-02-10 ·Reference W-2512133 ·Reported By 1 users
Summary
Fail to create a new territory if Default Internal Access is more open than Default External Access
Repro
Steps to reproduce the issue:
1. Enable Territory Management 2.0
2. In Setup, go to Security Controls > Sharing Settings. Edit “Organization-Wide defaults”. For object “Case”, set Default Internal Access equals to “Public Read Only”, and Default External Access equals to “Private”. Save.
3. In Setup, go to Manage Territories > Settings
=> You’ll see three access level items shown in Case Access section. The first item (Not access cases that they do not own that are associated with accounts in the territory) is selected.
4. Go to create a new territory. In the Territory Access Levels section, you’ll see only 2 items shown in Case Access Level and none is selected (the first item shown in Territory Settings does not show up here).
5. Click Save button. "An Internal server error has occurred" page returns.
Workaround
Set the default internal access and default external access to be the same
Reported By (1)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.