I am wondering if anyone has run into an issue with a validation rule on one standard Object creating a problem on another. Specifically, our Org has a validation rule on the Account Object to ensure that the standard field entitled "Account Number" is always populated when a record is either created or modified by certain internal users. However, when those same internal users employ the standard "Convert" button on a lead record to create a new account, they are unable to complete the action due to the validation rule for the "Account Number" field. I have attempted to add the "Account Number" field to the layout for the standard "Convert" button on the Lead Object, but that does not seem to be possible. Thus, for the moment, I have had to deactivate the validation rule, as I was driving some of our internal users nuts.

Has anyone run into this issue, and how did you come up with a solution to ensure that validation rules can stay active?

Thank you,

Jordan Reil