- Issue created by @DamienMcKenna
Sometimes changes are made on either the Salesforce side or the Webform side and the person forgets to either make the change in both places, or forgets to notify the people responsible that the change needs to be made in the other location. When the form is submitted afterwards it is likely that SF will fail to submit and instead logs a message containing the string "bad value for restricted picklist field:". Once the field disconnect is fixed the site is left with records that have not been sent over to SF.
Create a Webform and map it to Salesforce.
Modify one of the fields in the form so it has a discrepancy between what's in the form vs what's in SF, e.g. a maximum on an integer field is changed from 5 to 10.
Submit the form with the limit allowed by the form.
Notice that the SF submission will fail.
Provide a means to resubmit data to SF.
Work out how to resubmit data and either build the necessary functionality or document the process.
A method will exist for submitting records to SF that failed.
TBD
n/a
Active
5.1
salesforce_mapping.module