You are here:
Legacy Partner Connect Export, Import, and Update Statuses
See the outbound and inbound statuses for records that are exported, imported, or updated by using Partner Connect. If you’re a vendor admin, you see export and update issues only (because vendor orgs don’t import data). If you’re a partner admin, you can see import and update issues only (because vendor orgs don’t export data).
Outbound Statuses: Export and Update
| Status | What it Means | Action for Admin to Take |
|---|---|---|
| Duplicate Export Skipped | The record was skipped because it was previously exported to the partner org. | No further action is necessary. |
| Exported | The record was successfully exported. For the data to be successfully delivered to the partner org, the partner org must see a corresponding inbound transaction status of Imported. If the vendor admin has elected to send and receive record updates between orgs, a connected external record was also created in the partner’s org. |
No further action is necessary. |
| Exported: Connected Record Create Error | The record was successfully exported, but the corresponding connected external record failed to be created in the partner’s org. | If the issue occurs once or infrequently, no action is required. In most cases, the connected external record is eventually created in the partner org and updated accordingly when a vendor user edits an integrated field on the corresponding vendor record, realigning the connected records. If the issue occurs repeatedly, it indicates a configuration issue. Vendor and partner admins can verify that they followed the prerequisites for field mapping. See Planning Object and Field Integration for Legacy Partner Connect. If all prerequisites are met, the vendor admin must delete and recreate the field mappings for this object. After a vendor deletes and remaps their fields, the partner’s field mappings are also removed, and the partner must also remap their fields. |
| Exporting | The record is in the processing of exporting. | Wait for the export to complete or fail to discern if any further action is necessary. Exports that remain in progress for more than 60 seconds are no longer attempted, and the export is attempted again if a partner user manually retries from the vendor’s Experience Cloud partner site. If the same record continues to fail to move beyond the Exporting status, contact Salesforce Customer Support. |
| Not Exported: Connection Error | The export failed due to a connection authentication issue between the vendor and partner orgs. | Vendor and partner admins must delete their connections and step through the initial setup again. See Delete Connections and Turn Off Legacy Partner Connect. |
| Not Exported: External Error | The export failed because of an opportunity or lead save error in the partner’s org. | The vendor admin must contact the partner admin and ask them to check their email for any import issues around the date and time listed in the Last Modified Sent field for this transaction. The partner admin can rely on their IT professional for help with interpreting any technical descriptions in the csv file attached to the email. If additional help is needed, the partner admin must contact Salesforce Customer Support. |
| Not Exported: External Export Error | The export failed because Partner Connect encountered an issue with the partner’s ability to receive the transaction data from the vendor org. | If the issue occurs once or infrequently, no action is required. If the issue occurs repeatedly, the vendor admin must contact the partner admin and ask them to check their email for any import issues around the date and time listed in the Last Modified Sent field for this transaction. The partner admin can rely on their IT professional for help with interpreting any technical descriptions in the csv file attached to the email. If additional help is needed, the partner admin must contact Salesforce Customer Support. |
| Not Exported: External Field Mapping Error | The export failed because Partner Connect encountered an issue with the partner’s field mappings for this connection. | Vendor and partner admins can verify that they followed the prerequisites for field mapping. See Planning Object and Field Integration for Legacy Partner Connect. If all prerequisites are met, the vendor admin must delete and recreate the field mappings for this object. After a vendor deletes and remaps their fields, the partner’s field mappings are also removed, and the partner must also remap their fields. |
| Not Exported: Internal Error | The export failed because of an unknown error in the vendor org. | If the issue occurs once or infrequently, no action is required. If the issue occurs repeatedly, we recommend that the vendor org contacts Salesforce Customer Support. |
| Not Exported: Internal Field Mapping Error | The export failed because Partner Connect encountered an issue with the vendor’s field mappings for this connection. | Vendor and partner admins can verify that they followed the prerequisites for field mapping. See Planning Object and Field Integration for Legacy Partner Connect. If all prerequisites are met, the vendor admin must delete and recreate the field mappings for this object. After a vendor deletes and remaps their fields, the partner’s field mappings are also removed, and the partner must also remap their fields. |
| Update Not Sent: Can’t Find External Record | Your org can’t send this update because Partner Connect can’t find the parent lead or opportunity record in the external org. | You must contact the admin at the external org and ask them to check that the corresponding parent lead or opportunity record exists, and either admin can contact Salesforce Customer Support. |
| Update Not Sent: Connection Error | Your org can’t send this update due to a connection authentication issue occurring in your org. | If the issue occurs once or infrequently, no action is required. If the issue occurs repeatedly, vendor and partner admins must delete their connections and step through the initial setup again. Delete Connections and Turn Off Legacy Partner Connect. |
| Update Not Sent: External Delivery Error | Your org can’t send this update because Partner Connect encountered an issue with the external org’s ability to receive the transaction data you’re sending. | If the issue occurs once or infrequently, no action is required. If the issue occurs repeatedly, you must alert the admin at the external org. Recommend that they check that the PRM External Integration User has Create, Read, Update, and Delete access to the platform event External Record Share Event (ExtlRecShrEvent). The admin at the external org can rely on their IT professional for help. If the PRM External Integration User has the necessary access, we recommend that the admin at the external org contacts Salesforce Customer Support. |
| Update Not Sent: External Field Mapping Error | Your org can’t send this update because Partner Connect identified an issue with the field mappings for this object in the external org. | Vendor and partner admins can verify that they followed the prerequisites for field mapping. See Planning Object and Field Integration for Legacy Partner Connect. If all prerequisites are met, the vendor admin must delete and recreate the field mappings for this object. After a vendor deletes and remaps their fields, the partner’s field mappings are also removed, and the partner must also remap their fields. |
| Update Not Sent: Internal Field Mapping Error | Your org can’t send this update because Partner Connect identified an issue with your field mappings for this object. | Vendor and partner admins can verify that they followed the prerequisites for field mapping. See Planning Object and Field Integration for Legacy Partner Connect. If all prerequisites are met, the vendor admin must delete and recreate the field mappings for this object. After a vendor deletes and remaps their fields, the partner’s field mappings are also removed, and the partner must also remap their fields. |
| Update Not Sent: Internal Unknown Error | Your org can’t send this update because of an unknown error in your org. | If the issue occurs once or infrequently, no action is required. If the issue occurs repeatedly, we recommend that you contact Salesforce Customer Support. |
| Update Sending | Your org is in the process of sending an update. | Wait for the update to complete or fail to discern if any further action is necessary. Most updates that remain in the Update Sending status eventually resolve the next time one of your users edits an integrated field on the same record, and both the missed and new updates are saved to the corresponding connected record in the external org at the same time. You or another user in your org can check whether the issue resolves automatically by attempting another update on the record and running the report again. |
| Update Sent | Your org sent a record update to the external org. For the update to be successfully delivered to the external org, the external org must see a corresponding inbound transaction status of Update Received. | No further action is necessary. |
Inbound Statuses: Import and Update
| Status | What It Means | Action for Admin to Take |
|---|---|---|
| Imported | The record was successfully imported. If the vendor admin has elected to send and receive record updates between orgs, a connected external record was also created in the partner’s org. |
No further action is necessary. |
| Imported: Save Error on Connected External Record | The record was successfully imported, but the corresponding connected external record failed to be saved in the partner’s org. | If the issue occurs once or infrequently, no action is required. In most cases, the connected external record is eventually created in the partner org and updated accordingly when a vendor user edits an integrated field on the corresponding vendor record, realigning the connected records. If the issue occurs repeatedly, we recommend that you contact Salesforce Customer Support. |
| Update Not Received: Field Mapping Error | Your org can’t receive this update because Partner Connect can’t map the external org’s field mappings to your field mappings. | Vendor and partner admins can verify that they followed the prerequisites for field mapping. See Planning Object and Field Integration for Legacy Partner Connect. If all prerequisites are met, the vendor admin must delete and recreate the field mappings for this object. After a vendor deletes and remaps their fields, the partner’s field mappings are also removed, and the partner must also remap their fields. |
| Update Not Received: Save Error on Connected External Record | Your org can’t receive this update because the corresponding connected external record failed to save the changes. | If the issue occurs once or infrequently, no action is required. In most cases, updates that were missed are sent the next time a user in the external org updates an integrated field on the same record. Both the missed and new updates are saved to the corresponding connected record in your org at the same time. If the issue occurs repeatedly, compare the connected external object for this record and verify that you configured each field to exactly match the corresponding field on the parent object (lead or opportunity). You could also get more information by having a partner user attempt to export a different but similar record as a test. If you’re able to trigger the same issue, the resulting import notification email sent to the partner admin includes a detailed error message in the attached csv file. |
| Update Not Received: Unknown Error | Your org can’t send this update because of an unknown error. | If the issue occurs once or infrequently, no action is required. If the issue occurs repeatedly, we recommend that you contact Salesforce Customer Support. |
| Update Received | Your org received a record update sent from the external org and saved it to the corresponding connected external record. | No further action is necessary. |
