Ran into this in production. We have a contact for our patients and the customer entered "Smith (Jones)" as the contact name. This created a contact successfully, but when they tried to edit the contact to update other fields on the patient, the updates always failed.
Has anybody else run into something like this? I'm looking into excluding parenthesis from the field, but I'm also digging through legacy code to try and figure out how this could be causing problems. (My guess is some soql that uses the name)
Removing the parenthesis did allow the updates to go forward. Basically, having them in the last name precluded updates, not inserts.
There was indeed a code block hidden away that silently failed updates with parentheses in them for first name or last name of the contact update. This is from a contractor long gone, with the comment :
//added for security vulnerability - Contractor 9/9/2015
I was unaware that there was a security risk on parentheses in SFDC's field names. Google searches do not reveal any that I can find.
Is this a real issue?