This article addresses save and update exceptions in Salesforce Life Sciences Cloud automation when working with Contact Point Address (CPA) records for Healthcare Providers (HCPs) and Healthcare Organizations (HCOs).
The exact errors customers report are: "You can't update the field on a record that has related Contact Point Address", "Attempt to de-reference a null object", and an error preventing record creation from the Search Before Create component when the related Contact Point Address field is populated.
A related symptom is "We couldn't perform the action because there are unprocessed sync transactions. Try again later or ask your Salesforce admin for help" when unlocking a Visit that has sample disbursement or DTP order records.
These errors occur when you run the standard documented flow that invokes the [Process Contact Point Address Records] invocable action to clone CPA records, when you download an account list of records, or when you create an Office/Contact Person account from the Search Before Create component on web and iPad.
The issue affects non-administrator users more often because of field-level security gaps, and orgs with two Person Account record types enabled. Customers describe this as: "the flow that copies HCP contact point address fails", "unable to create an account from search before create", and "de-reference a null object error while downloading the account list".
Work through the cause that matches your symptom.
Cause 1: "You can't update the field on a record that has related Contact Point Address" when the flow clones HCP/HCO addresses, especially with two Person Account record types enabled (KI-20001).
1. Open Setup > Flows and locate the flow that invokes the [Process Contact Point Address Records] action.
2. In the flow, after opening it, re-select the Person Account field references in the assignment/update elements, then save the flow again. This re-binds the field references that break when two Person Account record types exist.
3. If you are deploying this flow rather than editing in place, edit the Person Account field references directly in the flow Metadata, then deploy.
4. Confirm the [Process Contact Point Address Records] action only sets fields on the new (cloned) [ContactPointAddress] record and does not attempt to update locked parent fields on the existing record.
Cause 2: Record creation fails from the Search Before Create component when the related Contact Point Address field is populated, often for non-admin users (KI-69017 pattern).
1. Go to Setup > Profiles or Setup > Permission Sets for the affected users.
2. Under Object Settings > Contact Point Address [ContactPointAddress], set Read and Edit to enabled.
3. Under Field-Level Security, set [Field Permissions] for the address fields used by the component (including Billing/Shipping Address fields on related objects) to Visible = checked and Read-Only = unchecked.
4. Reassign the permission set or re-save the profile, then have the user log out and back in.
Cause 3: "Attempt to de-reference a null object" when downloading the account list.
1. Identify the formula field or trigger handler referenced during the download. In Life Sciences Cloud sample-limit setups this is the custom formula field mapping the sample limit template API name and the [NewAccountSampleLimitInitHandler] / [NewAccountSampleLimitInitHandlerforHCO] trigger handlers.
2. Open Setup > Object Manager > Account > Fields & Relationships and confirm the custom formula field returns a non-null value (wrap the mapping in a null-safe formula such as BLANKVALUE or IF(ISBLANK(...),"",...)).
3. Verify the Account records being downloaded have the related [ContactPointAddress] populated; null related records cause the de-reference error.
Cause 4: "We couldn't perform the action because there are unprocessed sync transactions. Try again later or ask your Salesforce admin for help" when unlocking a Visit with sample disbursement or DTP order records.
1. Go to Setup > Object Manager and review the sync transaction object tied to the Visit.
2. Confirm there are no records in a Pending or Failed sync state for that Visit; reprocess or clear any stuck transactions before retrying the unlock.
3. If no pending transactions exist, this matches a known row-lock condition (KI-20078 / KI-20001 reference resolution patterns); retry the unlock after sync processing completes.
Confirm the issue is resolved by re-running the HCP contact point address copy flow and verifying a cloned [ContactPointAddress] record is created without the "You can't update the field" error, by creating an account from Search Before Create with the related Contact Point Address populated, by downloading the account list without the de-reference error, and by unlocking a Visit with sample disbursement records successfully.
005387936

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.