Salesforce is a Customer Relationship Management (CRM) software solution that brings companies and customers together. It has many applications which support various features such as lead generation, lead acquisition, sales tracking, and deal closure. It is designed to manage the data of an organization around customers and sales.
Salesforce offers the following features:
•Contact management
•Opportunity management
•Customer engagement
•Lead management
•Partner management
•Email integration
•Sales forecasting
Salesforce provides version 53 of the REST API that the Salesforce catalog source uses.
Objects extracted
The Salesforce catalog source extracts the following objects from a Salesforce source system:
•Organization
- List View
▪ List View Column
- Trigger
- Object
▪ Field
Note: If there is a duplicate global list view that is not associated with a specific object in the source system, then only one global list view is extracted.
Prerequisites for configuring the Salesforce catalog source
•Use the Salesforce connector to connect to Salesforce source system. For information about configuring a connection in Administrator, see Connections in the Cloud Common Services help.
•To extract metadata from a Salesforce source system through REST API, verify that you have access to Salesforce REST API v53.
•To set up authorization to restrict access to your organization's protected resources, use the OAuth 2.0 Refresh Token Flow for Renewed Sessions. For more information about this authorization method, see the Salesforce documentation on OAuth 2.0 Refresh Token Flow for Renewed Sessions.
Configure permissions or access to Salesforce
Before you configure a Salesforce catalog source, configure the required permissions. Metadata Command Center uses OAuth authentication to connect to Salesforce.
Permissions to extract metadata
To extract metadata, assign the following permissions:
- Modify All Data. Allows you to extract all objects. If you don't want Salesforce to modify all data, select View All Data.
Note: If you select View All Data, you might not extract some objects. For more information, see the Knowledge Base article 000196069.
- API Enabled. Allows you to access the data of your organization through API requests to your Salesforce instance.
Permissions to run data profiles
You don't need additional permissions to run data profiles. You can run data profiles with permissions used to extract metadata.
Connection properties
When you create a connection to Salesforce in Administrator, connect using the OAuth connection type. After you configure the connection in Administrator, you can view the connection properties on the Registration page in Metadata Command Center.
OAuth connection type
The following table describes the Salesforce connection properties for an OAuth connection type:
Property
Description
Runtime Environment
The name of the runtime environment where you want to run tasks.
OAuth Consumer Key
The consumer key to generate a refresh token.
OAuth Consumer Secret
The consumer secret to generate a refresh token.
OAuth Refresh Token
The refresh token that you generated using the SFDC OAuth 2.0 tool.
For more information about how to generate the OAuth refresh token, see the Before you begin section.
Service URL
URL of the Salesforce service endpoint.
For example: https://login.salesforce.com/services/Soap/u/60.0
You can use any Salesforce API version up to 60.0, except the version 58.0.
Maximum length is 100 characters.
When you edit the service URL for an existing OAuth connection, you need to re-enter the consumer key, consumer secret, and refresh token.
Service End Point
URL pointing to the Salesforce instance.
OAuth Access Token
Specify the token generated using the Informatica OAuth utility.
Data profiling for Salesforce objects
Configure data profiling to run profiles on the metadata extracted from a Salesforce source system. You can run data profiles on the following Salesforce objects:
•Standard Objects
•Custom Objects
You can view the profiling statistics in Data Governance and Catalog. Data Governance and Catalog profiles only those Salesforce Standard objects that can be retrieved and queried.
Note: The data profiling task does not run profiles on List Views.
The data profiling task runs profiles on the following data types for Salesforce objects:
•URL
•STRING
•PHONE
•REFERENCE
•DATETIME
•BOOLEAN
•ID
•EMAIL
•DOUBLE
•TEXT AREA
•DATE
•CURRENCY
•PICKLIST
•INT
•PERCENT
•COMPLEX VALUE
•ANY TYPE
•JSON
•LONG
Sampling type
Determine the sample rows on which you want to run the data profiling task. You can choose one of the following sampling types for a Salesforce catalog source:
- All Rows
- Limit N Rows
- Custom Query
Data classification for Salesforce objects
Configure data classification for Salesforce catalog sources to classify and organize data in your organization.
You can choose one of the following options:
•Data Classification Rules. Choose from predefined or custom data classifications.
•Generated Data Classifications. CLAIRE automatically generates data classifications for the data elements.
Note: Salesforce source systems can contain ambiguous data with technical field names. To ensure that CLAIRE generates accurate data classifications, it uses the extracted Label attribute to generate data classifications.
You can view the data classification results in Data Governance and Catalog.
For more information about data classifications, see Data classification in the Administration help.
Glossary association
Enable glossary association and configure settings for the catalog source to automatically associate or recommend glossary terms as business names for data elements in technical assets.
The following table describes the settings:
Property
Description
Enable auto-acceptance
When enabled, this option automatically associates glossary terms with data elements based on the threshold limit that you specify. The automatically accepted glossary terms appear as business names of data elements in Data Governance and Catalog.
Confidence Score Threshold for Auto-Acceptance
Specify a percentage from 80 to 100 inclusive to set a threshold limit. If a glossary term matches a data asset within the threshold specified, Metadata Command Center automatically assigns the matching glossary term to the data element. The name and description of the glossary term with the highest confidence score appears as the name and description of the data element asset in Data Governance and Catalog.
Ignore Keywords
Choose to ignore specific parts of data elements when making recommendations. You can enter multiple unique prefix and suffix keywords. Keyword values are case insensitive.
Glossary Association Scope
Choose specific top-level business glossary assets to associate with technical assets. Selecting a top-level asset selects its child assets as well.
Note: Salesforce source systems can contain ambiguous data with technical field names. To generate accurate glossary associations, CLAIRE uses the extracted Label attribute for such technical field names.
For more information about the glossary association settings, see the Administrator help.
Troubleshooting the "FDC scanner fails with "Cannot retrieve the organization" in CDGC" error.
In Metadata Command Center, the Salesforce catalog source with the OAuth connection type fails during the Test connection stage with the following error:
Unexpected error occurred: Cannot retrieve the organization for \"https://login.salesforce.com/services/data/v53.0/query/? q=SELECT+Name+FROM+Organization\", no graphs created"
The following image shows the error on the user interface:
This issue occurs if you had provided login.salesforce.com as the service URL in the Salesforce catalog source connection configuration. You can use the service URL such as login.salesforce.com for testing connections, but not for REST API calls.
To resolve this issue, use the actual service URL in the Salesforce catalog source connection configuration.
To identify the actual service URL, perform the following steps:
The service URL is specific to the credentials that you use to connect to the Salesforce REST API, and based on which the standard login or OAuth keys are generated.
