[SalesForce] OnClick JavaScript Validation Rule Help

I have a button that when clicked will update a checkbox field in the back end of a custom object that will then fire a workflow to send out a company wide email. I want to make it so the user can only click that button if certain criteria is met.

I created two validation rules that make this work, but the only issue is that the error message doesn't display. So the user would be unable to tell that their email was not sent out. Below is all the detail about the button and the validation rules I have created. My question is do I need to code some validation into the button itself? Or am I missing something with the VR rules?

Button:

{!REQUIRESCRIPT("/soap/ajax/29.0/connection.js")} 
var ss = new sforce.SObject('Success_Story__c'); 
ss.id = "{!Success_Story__c.Id}"; 
ss.Send_Email__c = "TRUE"; 
result = sforce.connection.update([ss]); 
location.reload(true);

Validation Rule 1:

AND( 
ISBLANK(Amount__c), 
RecordType.Id = "01231000001Idj3", 
Send_Email__c = TRUE)

Validation Rule 2:

AND( 
ISBLANK(Number_of_Hired_Drivers__c), 
RecordTypeId = "01231000001Idj8", 
Send_Email__c = TRUE)

Also I should add that Send_Email__c is the checkbox that is being updated to true by the button.

Thanks,

Best Answer

You have to options:

do the validations on the fly using javascript; or
handle the salesforce update call like this:

{!REQUIRESCRIPT("/soap/ajax/29.0/connection.js")} 
var ss = new sforce.SObject('Success_Story__c'); 
ss.id = "{!Success_Story__c.Id}"; 
ss.Send_Email__c = "TRUE"; 
result = sforce.connection.update([ss]);

if (result[0].getBoolean("success")) {
  log("Success story with id " + result[0].id + " updated");
  location.reload(true);
} else {
  alert("failed to update Success story " + result[0]);
}

You can take a look at the Ajax Toolkit Developer Guide for more examples.

Related Solutions

[SalesForce] How to send Mass Email from List View in Contact Or Lead using custom button

Assuming you have this button on a related list/list view, you can use the {!GETRECORDIDS} javascript function to get the list/array of id of the selected records. You can then send this array to your apex class and then query the email field to get the email. YOu can do something like this:

{!REQUIRESCRIPT("/soap/ajax/28.0/connection.js")}
{!REQUIRESCRIPT("/soap/ajax/28.0/apex.js")}
var recordIdArray = {!GETRECORDIDS($ObjectType.Contact)};
console.log('the record Ids are' + recordIdArray);
var retStr = sforce.apex.execute("outbound_Emails", "SendEmailNotification",{conId: recordIdArray});

global class outbound_Emails{
        webservice static void SendEmailNotification (list<id> conId){
            list<contact> conList = [SELECT name,email FROM contact WHERE id IN : conId];
            system.debug('the selected contacts are  ' + conList);
            //you can iterate over this list to get the email and send the mail
        }
}

[SalesForce] Bypass validation rule on parent object while updating parent object from Child object trigger

The problem looks clear to me as you are facing a challenge with the small point in order of execution of salesforce.

To understand this you need to refer to order of execution in salesforce.

Triggers and Order of Execution

If you go to the link you'll find out in step 4 the custom validations are run once again after the before triggers which fails your logic.

STEP 4: Runs most system validation steps again, such as verifying that all required fields have a non-null value, and runs any user-defined validation rules. The only system validation that Salesforce doesn't run a second time (when the request comes from a standard UI edit page) is the enforcement of layout-specific rules.

To avoid the problem I would request you to not make the checkbox BypassCloseddateValRule, you created to bypass the validation rule to FALSE in the trigger.

You should do this change in a later step after which custom validations are not called, i.e. in STEP 7 (After Trigger) or STEP 11 (Workflow field Update).

Because custom validation rules will not be called after those steps.

STEP 12: If the record was updated with workflow field updates, fires before update triggers and after update triggers one more time (and only one more time), in addition to standard validations. Custom validation rules and duplicate rules are not run again.

I believe this will solve your problem. Let us know if you face any other challenge.

Thank You.

Related Topic