Update to Opportunity field validation behaviour

Salesforce frequently makes changes and updates on different Orgs and Objects. In the Spring ‘22 release, there is a change on the Opportunity object. Salesforce has changed its layout for the New Opportunity screen and has changed the page validation message on the Opportunity object. You will notice this change when you create a New Opportunity in Salesforce. Earlier, the page error messages were displayed as messages right above the form. Please refer to the screenshot given below.

Above: Page validation error messages as displayed earlier in the “New Opportunity” screen.

With the change in the Salesforce layout in Spring ‘22, it is now displayed as a pop-up at the bottom of the screen. Please refer to the screenshot below.

Above: Page validation error messages as displayed in the “New Opportunity” screen as on date.

How do I resolve this?

To ensure your legacy test cases continue to work with the new page validation messages on the New Opportunity screen, you might need to update your test cases.  Please see the examples given below for more information.

Steps to update the page error assertion on the Opportunity object

The steps to update the page error assertion are explained with the help of examples. As a user, if you come across the page assertion messages, you may have to update your test cases as mentioned below.

Example 1:  

In Salesforce, when an error occurs on the New Opportunity screen; the error message is displayed as “Review the following fields whereas previously the error message was displayed as “Review the errors on this page”. 

In the existing test case, on the Test Builder, right-click on the UI Assert test step and click Edit the Test Step.

Above: Editing the UI Assert test step.

An Edit Test Step section in the Test Builder is displayed. In the Expected Page Message section you can see “Review the errors on this page” text; you have to edit this text to “Review the following fields”. Please refer to the screenshot below.

Above: Screenshot displays updating the “Expected Page Message”.

Click Save and execute the test case again. It will be executed successfully.

Example 2:

In Salesforce, if an error occurs on the New Opportunity screen, when required field(s) are missing then it is displayed as a bulleted list as given below:

  • Close Date
  • Opportunity 
  • Name
  • Stage 
  • Account name 

whereas previously it was displayed as “These required fields must be completed: Account Name, Close Date, Opportunity Name, Stage”.

Above: Updating the old error message in the “Expected Page Message” with the new error message.

In your existing test case, on the Test Builder, right-click on the UI Assert test step and then click Edit the Test Step.

An Edit Test Step section in the Test Builder is displayed. In the Expected Page Message section you will see “These required fields must be completed: Account Name, Close Date, Opportunity Name, Stage” text; edit this text to “Close Date”. 

So, when this test case is executed, the UI Assert test step will basically check (i.e. search the page message string) from the bulleted field list as listed below, for the “Close Date”. 

  • Close Date
  • Opportunity Name 
  • Stage,
  • Account Name

Above: Updating the “Expected Page Message” with “Close Date”.

Click Save and execute the test case again. It will be executed successfully. Please refer to the screenshot below.

Above: Screenshot displaying the assertion is successful. 

Similarly, you can map and assert each of these fields separately i.e. (Opportunity Name, Stage, Account Name).

Where can I learn more?

If you need more information on this issue or if you are experiencing any other unexpected errors, please get in touch with our Customer Success team via the Provar Success Community or email [email protected].

Review Provar on G2
Documentation library

Other available resources

Looking for something different?

We use cookies to better understand how our website is used so we can tailor content for you. For more information about the different cookies we use please take a look at our Privacy Policy.

Scroll to Top