Symptoms:
Root-cause chain:
Course__c, a lookup to Program) and was set to field-level Required ("Always require a value in this field in order to save a record").Note: this is org-specific custom configuration interacting with packaged code, not a defect in the managed package itself. A validation rule that enforces the same field at save time reproduces the identical silent failure, for the same reason.
Part 1 — Remove the field-level Required setting on the custom field
The "Add More Participants" button will now save normally. Confirm by clicking the button, adding a student, and clicking Save.
Part 2 — Keep the field required for manual entry, safely
Do not re-enforce the field with a field-level required flag or a save-time validation rule; either will silently break the packaged button again. Instead, mark it Required on the page layout, which only applies to the manual edit screen:
Manual creation now requires the field, while the packaged button continues to work.
005390224

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.