function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Andrew B 1Andrew B 1 

ERROR that baffles the mind - Approvals

I am working on the challenge labeled: 
Create an approval process that validates when a Prospect Account becomes a Customer.

I'm relatively confident I got everything right as I added Prospect, Customer, and Pending, named things properly etc. For some reason it is giving me the error:
User-added image
However when I check, Test3 no longer exists under Workflow Field Updates:
User-added image
Why is it still giving me this error?
jigarshahjigarshah
Andrew,

The error occurs because you have a field called Test3__c set as a required field. It seems that whenever, you are trying to create a new record of object Test__c the required field constraint on Test3__c is restricing the record creation. The field could also be a possible Master Detail which you may have created while playing around with your Salesforce org.

The solution to your problem would be to provide a Default value for the Test3__c field while you invoke the record creation or to remove the Required constraint from Test3__c. Once done, try repeating the steps and they should work.

Hope this helps you complete your challenge.

Please mark this thread as SOLVED and the answer that best helps you resolve your issue, as the BEST ANSWER.
Andrew B 1Andrew B 1
I am not using Test3 in the Approval though, I am using Account:Type. I removed the instance of Test3 so I dont know where else it exists? Where are you saying to do this? It doesnt appear in the second screenshot I listed because I clicked the "Del" button on the instances of it.
Andrew B 1Andrew B 1
When I delete again Test3 from object manager and run I get: First exception on row 0; first error: REQUIRED_FIELD_MISSING, missing required field: [nextApproverIds]: [nextApproverIds]
jigarshahjigarshah
Andrew,

The root cause is the same, only that it now occurs wiht the different field. YOu would need to remove the Required mandate from all fields that interfere with the record creation in consideration. You need not delete the field, only removing the Required constraint should help you get around this.

Also, you may want to check the possible options from where you have marked the field as required and accordingly address them.
1. Page layout
2. Field Level Required mandate

Hope this helps.

Please mark this thread as SOLVED and the answer that best helps you resolve your issue, as the BEST ANSWER.