Timeout When Changing Unique Field to Case Sensitive
Last updated 2021-05-26 ·Reference W-5459574 ·Reported By 6 users
When an org has a large volume of records, changing the status on a unique field from 'case insensitive" to "case sensitive" causes a timeout error after approximately 2 minutes.
1. Edit a unique field
2. Change the uniqueness from "case insensitive" to "case sensitive"
None at this time
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.