Internal Server Error when Disabling Community Usernames w/ Special Characters
Last updated 2016-12-08 ·Reference W-2883592 ·Reported By 2 users
Customer Community Users with special characters in their Usernames cannot be Disabled more than twice. On the third attempt, an Internal Server Error is encountered:
Error ID: XXXXXXXXXX-XXXXX (-1804535350)
In an org w/ Communities enabled:
1. Login as an Admin
2. Create a new Contact record.
3. Enable the contact as a Customer Community User. From the Contact record, click Manage External User | Enable Customer User, being sure that the username contains a + sign. Example: ‘email@example.com'
[Note: The '+' is important for this issue to reproduce.]
4. Return to Contact record and Disable the Community user. Click Manage External User | Disable Customer User.
5. Enable the contact as a customer Community user again, with the same username.
6. Disable the Community user again. Successful.
7. Enable the contact as a customer Community user once more.
8. Disable the Community user a final time.
Community User is disabled successfully, as in previous attempts.
Internal Server Error.
Affected Community Contacts can be successfully disabled by editing their *Usernames* so they do not contain special characters.
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.