Setting up the import of data from Salesforce CRM

To set up and run the import of data to Salesforce CRM, you'll need to do the following:

  1. Create the Salesforce CRM source
  2. Create the ingest job

Learn more about correctly formatting source files and ingest jobs so that you can successfully import data:

  • Ensure source files are formatted correctly by reviewing CSV file standards for Oracle Unity and supported CSV parsers.

  • Review how to import empty or null data and the restrictions on empty/null data in the Oracle Unity data model.

Create the Salesforce CRM source

To set up the data import, you will first need to create a Salesforce CRM source, which provides all the details that Oracle Unity needs to run the ingest job and import data.

To create the Salesforce CRM source:

  1. Click the Oracle icon Image of the application navigation button. Use it to access the different parts of Oracle Unity. in the bottom-right corner to open the navigation menu.
  2. Select Sources.
  3. In the top-right corner, click Create source.

Step 1: Define source details

The job details section allows you to define the type of source and how it will display in Oracle Unity.

Enter the information for the source.

An image of the details for an Salesforce source

  • Type: Use the drop-down list to select Salesforce CRM.
  • Name: Enter a name. The name must be 1 or more characters, up to a maximum of 50. Use only letters (a–z and A–Z), numbers (0–9), underscores (_), hyphens (-), and spaces. The first character cannot be a space.
  • Source ID: When Oracle Unity ingests data using this source, it uses this value for the Source ID attribute of each object. The Source ID is auto-populated from the source name you enter. You can't change this value after you create the source.
  • Description: Enter a description. This field is optional, but it is highly recommended to add descriptions for any entity created. This helps all other users get additional context when using and navigating Oracle Unity. The description can have a maximum of 512 characters with no restrictions on characters used. You can use characters from all languages supported in the language settings.

Step 2: Configure authentication settings

Enter the information to allow Oracle Unityto access the required data from Salesforce.

An image of the authentication section

  • URL: Enter the base URL of your Salesforce account.
  • Client ID: Enter the Client ID of your Salesforce account.
  • Client Secret: Enter the client secret of your Salesforce account.
  • Security Token: Enter the security token of your Salesforce account.
  • Username: Enter the username of your Salesforce account.
  • Password: Enter the password of your Salesforce account.

Once you enter all the details, click Verify connection to ensure that Oracle Unity can access the server. If there are connection issues, confirm the server path and authentication settings entered are correct.

Step 3: Save and publish the new source

When finished defining the source, scroll to the top of the page and click Save or Save and close.

Once you create the source, you will need to publish the changes.

After creating and publishing the source, you can create the ingest job.

Create the ingest job

You can now create the ingest job that will use the Salesforce CRM source to transfer the data.

To create the ingest job:

  1. Click the Oracle icon Image of the application navigation button. Use it to access the different parts of Oracle Unity. in the bottom-right corner to open the navigation menu.
  2. Select Data feeds.
  3. In the top-right corner, click Create data feed, then select Ingest job.

The Create ingest job page is displayed.

Step 1: Define job details

The job details section allows you to define how the ingest job will display in Oracle Unity.

To define the job details:

  1. Enter the details for the ingest job.
    • Name: Enter a name. The name must be 1 or more characters, up to a maximum of 50. Use only letters (a–z and A–Z), numbers (0–9), underscores (_), hyphens (-), and spaces. The first character cannot be a space.
    • Job ID: The Job ID field is auto-populated from the job name you enter. You can change this value before the job is created.
    • Description: Enter a description. This field is optional, but it is highly recommended to add descriptions for any entity created. This helps all other users get additional context when using and navigating Oracle Unity. The description can have a maximum of 512 characters with no restrictions on characters used. You can use characters from all languages supported in the language settings.
    • Source:  Select the Salesforce CRM source you created previously. Review the authentication details and make sure they are accurate.
  2. Once you have confirmed that the details are correctly configured, click Continue.

An image of the job details section

Step 2: Field mapping

Field mapping allows you to define how fields from your source files are mapped to the attributes in the data model.

To set up field mapping, you will need to do the following:

  • Select a source object
  • Add a sample file of the source fields

To create a source object:

  1. Use the drop-down list for Source object to select a pre-defined source object.

    2. An image of the Source object drop-down list

  2. Confirm the selection and click Continue.

Based on the source object selected, pre-defined source fields will be populated for field mapping.

Mapping source object fields to data model attributes

Notes: You cannot access or search for hidden data objects and attributes for field mapping. Learn more about Hidden data model items in ingest jobs.

To map source object fields to data model attributes:

  1. For each of the pre-defined source fields, click EditAn image of the edit button. Use it to complete field mapping for ingestion jobs. to start adding attributes from the data model.

    2. Click the pencil icon to start adding attributes

  2. A list of recommended attributes may display for you to add. You can also use the search field to find attributes to add. You can search by data object name, attribute name, or attribute description.

    3. An image showing recommended attributes and the search field

  3. If you need to add an attribute that is not currently part of the data model, click Create attribute. Attributes you create will need to be published before the ingest job runs. You can review attributes that need to be published by clicking the checkbox for Show unpublished attributes. Learn more about Creating attributes and Publishing changes.

    4. An image showing the Create attribute button and checkbox for viewing unpublished attributes

  4. To add the attribute, click the CheckmarkAn image of the checkmark button. Use it to confirm field mapping for ingestion jobs..
  5. To add a transformation on an attribute, click Transform.

    6. An image showing the data transformation link

    Learn more about the different transformations available:

Important notes about configuring field mapping

  • A single source field can be mapped to one or more data model attributes. Conversely, one or more source fields can be mapped to a single data model attribute. If you map multiple source fields to a single data model attribute, you want Oracle Unity to store multiple values in that one data model attribute. Because of this, you need to ensure you select the appropriate transformation, so that Oracle Unity can correctly combine those multiple values.

  • A notification will display if not every data object used in a mapping has its source mapped to an incoming field. Mapping all source data object IDs ensures that duplicate data is removed before it is stored in the system. Review the Source data object IDs not mapped notification before completing field mapping. The notification will identify each unmapped data object with a color.

    •  An image showing the notification of unmapped source data object IDs

    • A red circle indicates that the unmapped source data object ID (SourceXID attribute) will cause the ingest job to not import the data successfully, even if the ingest job successfully completes. This is because the Incoming records flag for the data object is set to No (insertOnly parameter set to false). Learn more about the Incoming records flag.

      • Example: You map the First name attribute from the Customer data object to the FirstName source field in the sample file. You must also map the corresponding SourceCustomerID attribute in the Customer data object to a source field in the sample file so that the data can be successfully imported. This is because the Incoming records flag for the Customer data object is set to No.

    • A yellow circle indicates that the source data object ID (SourceXID attribute) is unmapped, but the ingest job will still successfully import the data. This is because the Incoming records flag for the data object is set to Yes (insertOnly parameter set to true). If the SourceXID attribute is not mapped, Oracle Unity will automatically add a unique identifier to the SourceXID attribute when the data is imported. Learn more about the Incoming records flag.

      • Example: You map the Order Total attribute from the Event data object to the OrderTotal source field in the sample file, but you don’t map the SourceEventID attribute to a source field. You will receive a warning the source data object ID is unmapped, but the ingest job will still be able to import the data successfully. This is because the Incoming records flag for the Event data object is set to Yes.

Step 3: Schedule and notify

You will need to configure the schedule and notification settings for the ingest job.

An image of the Schedule and notify section

To schedule the ingest job and define the notification settings:

  1. Configure the schedule for the ingest job:
    • Click Recurring to automatically run the job on a regular schedule. If a job is still running while the next one is scheduled to run, the next scheduled run will not start until the current one completes. Two scheduled instances of the same ingest job can't run simultaneously.
    • Click On demand to run the job as needed.
  2. If the job is recurring, select the Frequency, Start time, and Days it will run.
  3. In the field for Notify, enter the email addresses of people to be notified when the job runs. You can use characters from all languages supported in the language settings. Separate multiple emails with a comma.

    4. Please note that the metrics for ingest jobs in notification emails are approximations and will not always be 100% accurate.

  4. If you only want a notification if the job fails, click the checkbox for Only notify on failure.

Step 4: Save and publish the ingest job

After saving the ingest job you will need to publish the changes before it can run.

To save and publish the ingest job:

  1. Scroll to the top of the page and click Save or Save and close.
  2. Follow the steps for Publishing changes.

Run the ingest job

After the publish job successfully completes, you can run the ingest job, either as a scheduled job or manually from the Data feeds page. You can then monitor its progress from the Jobs dashboard.

Once the ingest job successfully completes, you can review the imported data from the Data viewer.

Learn more

Creating sources

Creating ingest jobs

integrate, integration, salesforce, how to integrate, salesforce crm, import