[SalesForce] Display all error messages

Visualforce page is displaying one error message at a time not all error messages if validation is failed for all fields.Below is my code in the controller.I have apex:pagemessages in visualforce page is display error messages

if((newFR.Fleet_Vehicle_Maintained__c == 'No')&& (newFR.Fleet_Explanation__c == NULL )) {
          newFR.Fleet_Explanation__c.addError('If the fleet vehicle is not being maintained by the rep, an explanation is required.');
                        return null;
          }
         if((newFR.Rep_Policy__c == 'No')&& (newFR.Not_Policy_Explanation__c == NULL )) {
           newFR.Not_Policy_Explanation__c.addError('Not_Following_Policy_Explanation__c');

          return null;
          } 
          if((newFR.FR_Status__c == 'Send for Representative')&& (newFR.Review_Date__c > system.today() )) {
           newFR.Review_Date__c.addError('Review Date cannot be a future date when sending  for acknowledgement.');

          return null;
          }

Best Answer

The code you've produced is quitting after the first error (return null). A more usual scenario is to set a flag when validation fails, then check for the flag at the end of the validation to abort processing.

Here's a common example:

public PageReference doSomething() {
    Boolean okayToSave = true;
    if( condition1 ) {
        record.field1__c.addError(...);
        okayToSave = false;
    }
    if( condition2 ) {
        record.field2__c.addError(...);
        okayToSave = false;
    }
    if( conditionN ) {
        record.fieldN__c.addError(...);
        okayToSave = false;
    }
    if( !okayToSave ) {
        return null;
    }
    // Now save the data
    insert record;
    return Page.SuccessfulSave;
}

Of course, I left out the part where you use a try-catch block or other error handling for the actual save, because it's not relevant to what I'm trying to explain.

Related Solutions

[SalesForce] Difference between the multiple messaging options in Visualforce

Let me start off by explaining each of these in more detail.

apex:pageMessage is used to display a single custom message using the Salesforce formatting. You can specify the severity (which will control the display of the message box) and the strength (which will control the size of the box). Take the following code for example:

<apex:page >
  <apex:pageMessage summary="This is a pageMessage" severity="info" strength="3"/>
</apex:page>

Renders as:

pageMessage

Now let's tweak that code slightly:

<apex:page >
  <apex:pageMessage summary="This is a pageMessage" severity="error" strength="1"/>
</apex:page>

Notice how I changed the severity and the strength. This controls the size and the display of the message. This renders as:

apex:pageMessage error

This can be used to display any custom message that you always want to appear on the screen. There may be a case that whenever a user is on a form you may want a warning to appear to display important information to them.

apex:pageMessages is used to display all of the messages on a page. It will display Salesforce generated messages as well as custom messages added to the ApexPages class. Let's take a look at it in use:

<apex:page controller="TestMessageController">
  <apex:pageMessages />
</apex:page>

public class TestMessageController{
    public TestMessageController(){
         ApexPages.addMessage(new ApexPages.Message(ApexPages.Severity.ERROR, 'This is apex:pageMessages'));
    }
}

This renders as:

apex:pageMessages

Let's add some more messages and see how it reacts:

<apex:page controller="TestMessageController">
  <apex:pageMessages />
</apex:page>

public class TestMessageController{
    public TestMessageController(){
         ApexPages.addMessage(new ApexPages.Message(ApexPages.Severity.ERROR, 'This is apex:pageMessages'));
         ApexPages.addMessage(new ApexPages.Message(ApexPages.Severity.ERROR, 'This is apex:pageMessages still'));
         ApexPages.addMessage(new ApexPages.Message(ApexPages.Severity.INFO, 'This is apex:pageMessages info'));
         ApexPages.addMessage(new ApexPages.Message(ApexPages.Severity.INFO, 'This is apex:pageMessages warning'));
    }
}

This renders as:

apex:pageMessages more messages

Notice how that single instance of the apex:pageMessages handles all of the errors on the page. The use case for this object is to capture all errors on the page. It should be used on most custom Visualforce page as a catch all to let users know what errors occur (if no other messaging is used).

apex:message is used to display an error on only a very specific field. It is used to allow the developer to place field specific errors in a specific location. Take the following code for example:

<apex:page controller="TestMessageController">
<apex:form >
  <apex:outputLabel value="Test String" /><apex:inputText value="{!test.Name}" id="test"/>
  <br/><apex:message for="test"/>
</apex:form>

public class TestMessageController{
    public Account test{get;set;}
    public TestMessageController(){

    }
}

renders as:

enter image description here

Notice how this currently doesn't have a message displayed. Also notice how this particular element is specified specifically for one field. The error will only occur on that one field. Let's change the code a bit and take a look at this with an error on the Name field:

<apex:page controller="TestMessageController">
    <apex:form >
      <apex:outputLabel value="Test String" /><apex:inputField value="{!test.Name}" id="test"/>
      <br/><apex:message for="test"/>
    </apex:form>
</apex:page>

public class TestMessageController{
    public Account test{get;set;}
    public TestMessageController(){
        test = new Account();
        test.Id.addError('Correct');
        test.Name.addError('Wrong');
    }
}

This renders as:

apex:message

Notice how only the Name error is shown because that is the only field that has an apex:message associated to it. Also notice that although this does have some styling, the styling is minimalistic and Salesforce expects the developer to handle the styling as necessary in this situation.

The final thing to look at is apex:messages. apex:messages is similar to apex:message, but it displays all of the errors. These errors are displayed as a list with no styling. Let's take the last example we used in the apex:message and simply add the apex:messages tag to the Visualforce. The code:

<apex:page controller="TestMessageController">
    <apex:messages />
    <apex:form >
      <apex:outputLabel value="Test String" /><apex:inputField value="{!test.Name}" id="test"/>
      <br/><apex:message for="test"/>
    </apex:form>
</apex:page>

public class TestMessageController{
    public Account test{get;set;}
    public TestMessageController(){
        test = new Account();
        test.Id.addError('Correct');
        test.Name.addError('Wrong');
    }
}

renders as:

apex:messages

This provides no formatting for the errors, however, it does display them all. The use case for using apex:messages is to display all errors on the page while providing your own styling.

Now, to close it all out, let's take a look at them all together. The code:

<apex:page controller="TestMessageController">
    <apex:pageMessages />
    <apex:pageMessage summary="This is apex:message" severity="info" strength="2"/>
    <apex:messages />
    <apex:form >
      <apex:outputLabel value="Test String" /><apex:inputField value="{!test.Name}" id="test"/>
      <br/><apex:message for="test"/>
    </apex:form>
</apex:page>

public class TestMessageController{
    public Account test{get;set;}
    public TestMessageController(){
        ApexPages.addMessage(new ApexPages.Message(ApexPages.Severity.ERROR, 'This is apex:pageMessages'));
        test = new Account();
        test.Id.addError('Correct');
        test.Name.addError('Wrong');
    }
}

renders as:

All together now!

As expected, apex:pageMessages shows all of the errors with formatting, apex:pageMessage only shows the specified message, apex:messages shows all of the errors with no formatting, and apex:message shows only the error for the specified field.

Note: I have reposted this question and answer on my website. It can be found here.

[SalesForce] When do validation failures automatically generate an Apex.PageMessage

You may need to include showDetails="{!showDetails}" on apex:pageMessages.

I'm probably like you - errors can be raised by validation rules, apex class logic using .addError() and general exceptions caught by try - catch.

I tend to always use a Utility method to emit an ApexPages.Message that exploits: ApexPages.Message myMsg = new ApexPages.Message(ApexPages.severity, summary, detail);

The utility method will 'friendlify' the exception message, stripping out unnecessary SFDC verbosity from raised validation errors before outputting the ApexPage.Message

I also use a separate controller method getShowDetails() that decides whether to 'showDetails'. The method checks to see if the text in the detail portion is the same as the text in the summary portion of ApexPages.Message. This works around some VF issues when the summary and detail are essentially the same.

Best Answer

Related Solutions

[SalesForce] Difference between the multiple messaging options in Visualforce

[SalesForce] When do validation failures automatically generate an Apex.PageMessage

Related Topic