---
schema_version: "1"
id: 7396fb14d9dfe226a85900d07ebe48e873b7f2cec256f8c0f92637dfa7b16efc
title: Finding and Interpreting the Statuses of Legacy Partner Connect Data Transactions
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/slack/264-0-0/prm_pc_transact.md
canonical_url: https://help.salesforce.com/s/articleView?id=slack.prm_pc_transact.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: b54172d6d0ac97a95c7c6efef54abd5bd8bb6f707a88f864adaef4a30b72b748
description: Before addressing Partner Connect export, import, and update issues, vendor admins and partner admins must first understand what makes a data transaction successful. Then admins can learn where failed transactions are shown and what details are provided to resolve issues.
products:
  - Sales
  - Slack
  - Cross Cloud
release: "264"
---
# Finding and Interpreting the Statuses of Legacy Partner Connect Data Transactions

Before addressing Partner Connect export, import, and update issues, vendor admins and partner admins must first understand what makes a data transaction successful. Then admins can learn where failed transactions are shown and what details are provided to resolve issues.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small "><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in Lightning Experience in <strong>Enterprise</strong> and <strong>Unlimited</strong> Editions with Sales or Service. Vendors must purchase a <a href="https://help.salesforce.com/s/articleView?id=slack.prm_support_license_template.htm&amp;type=5&amp;language=en_US" target="_blank">PRM add-on license</a> for the partner admin user and each partner user who exports records. Partners aren’t required to purchase PRM licenses to use Legacy Partner Connect.</td></tr></tbody></table>

## What Makes a Data Transaction Successful?

For Partner Connect to get data from one org to another, two successful data transactions are required.

- An outbound transaction. Outbound transactions include exports and updates. The status of an outbound transaction answers the question: Was record data sent successfully?
- An inbound transaction. Inbound transactions include imports and updates. The status of an inbound transaction answers the question: Was record data received successfully?

Here’s an example of how inbound and outbound transactions work when a batch of records is exported from the vendor org and imported to the partner org.

First, Partner Connect packages the record data from the vendor’s org, checks vendor object and field mappings to see what fields must be sent, and attempts an export. This end-to-end process is an outbound transaction, and can succeed, be skipped, or fail.

Next, Partner Connect attempts to import the records to the partner org. To import, Partner Connect interprets the vendor’s exported data, checks it against the partner object and field mappings, and creates the imported record or records in the partner org. This end-to-end process is an inbound transaction, and can succeed or fail.

If the vendor org elected to send and receive record updates between orgs, a connected external record is also created in the partner org during import. The first time a partner user updates an imported parent record, a connected external record is also created in the vendor org. The vendor’s connected external record is also paired as a child to the vendor’s original parent record. See [How Legacy Partner Connect Exports, Imports, and Integrates Records Across Orgs](https://help.salesforce.com/s/articleView?id=slack.prm_pc_overview_how_biz_tracked.htm&release=264.0.0&type=5 "Learn about how Partner Connect lets vendors and partners work on shared leads and opportunities independently while still providing cross-org visibility into how each record is progressing.").

Outbound and inbound transactions for updates work similarly to the way they do for exports and imports. After a parent record is updated, an outbound transaction occurs in the org that initiates the update, and an inbound transaction occurs in the org that receives the update.

If the outbound or inbound transaction on an export, import, or update process is skipped or fails, Partner Connect fails to complete one of these actions.

- Create a record in the partner org with data exported from the vendor org.
- Create a connected external record in either org with data from the external org.
- Send data updates to an org.
- Receive data updates from an org.

## Identifying Failed Data Transactions

Because each export, import, or update requires several end-to-end processes to successfully transfer data between orgs, one-off transaction failures can occur. One-off failures aren’t indicative of a deeper problem, and in many cases Partner Connect resolves one-off failures on your behalf. But recurring failures are indicative of configuration or connection issues that the vendor admin, partner admin, or an IT professional at the partner company must address.

Transaction failures are presented to users and admins in several ways.

- For export issues that occur immediately after the partner user attempts an export, Partner Connect show an error to partner users so that they can try again or contact an admin for help.
- For import issues, Partner Connect sends an import status email to the last partner admin who updated field mappings from the Partner Connect page in Setup. The email summarizes the number of successful imports, plus any failed or skipped import attempts. Any details known about import failures are attached to the email as a csv file so partner admins can troubleshoot issues. Partner admins must sometimes work with an IT professional at their company or the vendor admin for the connected org to resolve issues.
- To get more information about recurring export, import, and update issues, vendor and partner admins can build and run a Partner Connect status report from their respective orgs. Then admins can follow Partner Connect recommendations for diagnosing and addressing issues. In some cases, vendor and partner admins must work together to resolve issues.

## Tracking Outbound and Inbound Data Transactions With a Status Report

To observe the status of record exports, imports, and updates, vendor and partner admins can build a Partner Connect Status Report on the External Record Share Record Mapping object. See [Build and Run a Legacy Partner Connect Status Report](https://help.salesforce.com/s/articleView?id=slack.prm_pc_fix_exp_imp_up_report.htm&release=264.0.0&type=5 "Vendor and partner admins can build a report to see the status of the export, import, and update transactions sent between orgs. Doing so lets admins address recurring issues, such as failed exports, imports, or updates.").

The External Record Share Record Mapping object stores outbound and inbound transaction data for attempted and successful exports, imports, and updates.

After building the report, admins can run it to identify recurring failed data transactions. Then admins can then resolve the issues described by outbound and inbound failure statuses. See [Finding and Interpreting the Statuses of Legacy Partner Connect Data Transactions](https://help.salesforce.com/s/articleView?id=slack.prm_pc_transact.htm&release=264.0.0&type=5 "Before addressing Partner Connect export, import, and update issues, vendor admins and partner admins must first understand what makes a data transaction successful. Then admins can learn where failed transactions are shown and what details are provided to resolve issues.").

When building their reports, we recommend that admins add these External Record Share Record Mapping fields and lookup fields to get the information they must diagnose issues.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:25%">
          <col style="width:75%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d2201e177">Field</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d2201e180">What It Tells You</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d2201e177 ">External Record Share Connection: Connection Name</td>

            <td data-label="What It Tells You" class="slds-cell-wrap" style="vertical-align:top;" headers="d2201e180 ">
              <p>The vendor or partner connection that pertains to each transaction. Adding this
                field to your Partner Connect status report is helpful if you maintain connections
                with multiple companies, so you can narrow down which connection configuration is
                causing issues. </p>
              <p style="margin-bottom:0;">Connection Name is a field from the External Record Share
                Connection object, but you can add this related field to your External Record
                Share Record Mapping report type to incorporate it into your reports.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d2201e177 ">Internal Record: Full Name</td>

            <td data-label="What It Tells You" class="slds-cell-wrap" style="vertical-align:top;" headers="d2201e180 ">
              <p>The name of the internal lead in your org that your company uses to track lead
                data, which Partner Connect has either exported or imported. </p>
              <p style="margin-bottom:0;">To see the name of a
                lead in the external org that’s connected to your internal lead, open the internal
                lead and check the record name or names shown on the Connected External Leads
                related list.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d2201e177 ">Internal Record: Opportunity Name</td>

            <td data-label="What It Tells You" class="slds-cell-wrap" style="vertical-align:top;" headers="d2201e180 ">
              <p>The name of the internal opportunity in your org that your company uses to
                track opportunity data, which Partner Connect has either exported or imported. </p>
              <p style="margin-bottom:0;">To
                see the name of an opportunity in the external org that’s connected to your
                internal opportunity, open the internal opportunity and check the record name or
                names shown on the Connected External Opportunities related list.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d2201e177 ">Outbound Status</td>

            <td data-label="What It Tells You" class="slds-cell-wrap" style="vertical-align:top;" headers="d2201e180 ">
              <p>The status of the most recent outbound transaction that your org sent. </p>
              <p>Outbound statuses are always either exports or outbound updates that your org
                sent to the external org. Because partner orgs don’t export data, export
                transactions don’t show in a partner’s report.</p>
              <p style="margin-bottom:0;">The inbound status that correlates with each of your outbound statuses occurred
                in the external org. If you want to track the end-to-end journey of an export or
                outbound update, ask your peer admin to build their own version of the Partner
                Connect status report and share the findings.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d2201e177 ">Inbound Status</td>

            <td data-label="What It Tells You" class="slds-cell-wrap" style="vertical-align:top;" headers="d2201e180 ">
              <p>The status of the most recent inbound transaction that your org received. </p>
              <p>Inbound statuses are always either imports or inbound updates that your org
                received from the external org. Because vendor orgs don’t import data, import
                transactions don’t show in a vendor’s report.</p>
              <p style="margin-bottom:0;">The outbound status that correlates with each of your inbound statuses occurred
                in the external org. If you want to track the end-to-end journey of an import or
                inbound update, ask your peer admin to build their own version of the Partner
                Connect status report and share the findings.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d2201e177 "> Last Modified Sent</td>

            <td data-label="What It Tells You" class="slds-cell-wrap" style="vertical-align:top;" headers="d2201e180 ">The data and time of the most recent outbound transaction that your org sent to
              the external org. </td>

          </tr>
        </tbody>
      </table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-slack-salesforce_prm-264-0-0-production-enus/35cdbed0-3c5d-4ddb-94ea-c7445aa90b95/images/icon_note.png)

Note On the External Record Share Record Mapping object, Last Modified Date tells you the date and time of the most recent transaction that your org performed on the pair of records mapped across orgs. Last Modified Date could pertain to either an outbound or inbound transaction that occurred to a record, whichever happened to have occurred most recently. Because Last Modified Date doesn’t offer the specificity necessary to assess transaction issues, we recommend using Last Modified Sent when building your Partner Connect status report.

#### See Also

- [ExtlRecShrCnct](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_extlrecshrcnct.htm)
- [ExtlRecShrFieldMap](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_extlrecshrfieldmap.htm)