Skip to main content

Connecting Salesforce to Netsuite

User Guide: Configuring Source as Salesforce and Target as Netsuite.

 

This guide offers a detailed walkthrough for configuring Salesforce as the source and NetSuite as the target. By following these steps, you'll seamlessly establish a connection, retrieve desired data from the source, and efficiently transmit it to your chosen destination.

 

Data Source :

Step 1:

·       In the Data Source page, Select the source type as API

SS1.png

 

Step 2:

·       Now select the “Salesforce” as your product

salesforce1.png

Step 3:

·       Choose the appropriate business object based on your needs.

Salesforce 2.png


Note: In the event the desired product or business object isn't available, you have the option to select 'Create New' in the product name field. Provide the necessary details for the new product and the business object you intend to configure as the source.

Note: Opting for 'Create New' requires the user to furnish all necessary details essential for configuring the API as the source.

Step 4:

·       After selecting the business object (such as Account Information in this example), the system loads all prerequisites.

salesforce 3.png


·       Next, enter the instance identifier and Authorization details into the provided placeholders.

Salesforce 5.png

Salesfoce 6.png


Configuration Keys in Refresh Token Endpoint Body :

  1. grant_type: Specifies the grant type being used for authentication. Common types include "password" for resource owner password credentials and "client_credentials" for client credentials.

  2. client_id: Represents the unique identifier assigned to the client (application) by the authorization server during the registration process.

  3. client_secret: Serves as a confidential key known only to the application and the authorization server. It's used to authenticate the identity of the client application.

  4. username: Refers to the username or identifier of the user accessing the API. This is typically used in combination with the password grant type.

  5. password: Represents the user's password associated with the provided username for authentication purposes when using the password grant type.

These keys are utilized in constructing the API endpoint URL to exchange credentials securely and obtain an access token required for accessing protected resources through the API.


 Note : Various API endpoint URLs feature distinct placeholders, therefore, users need to input all relevant details based on their specific requirements. Please refer to the Salesforce API documentation for further information.


Data Operations :


Single Line to Multiline

This 'Single Line to Multiline' operation facilitates the transformation of JSON data from a single-line format to a multiline format. It's particularly beneficial when handling responses received in a single-line JSON structure. By converting it to multiline JSON, it separates and organizes records, enabling easier application of subsequent operations on each individual record.

Reference Link:   Single line to Multiline

Append

This operation allows for the addition of a new key-value pair within our dataset by providing a comma-separated list of key-value pairs enclosed in double quotes. The 'Append' feature facilitates mapping these keys to target keys, thereby composing the payload intended for transmission to the Data Target.

Here's an example illustrating the construction of a JSON payload by mapping keys, ensuring these keys are transmitted to the designated target.

"keyname": {
                "id": "{%id%}",
                "email": "{%email%}",
                "first_name": "{%first_name%}"
            }



Reference Link:   Append

Filter

     If else is called as the filter operation in eZintegrations, basically it has 1 parameter : Conditional Statement

  1. Source has the JSON data of the previous operation
  2. Target is the JSON data after performing the filter operation
  3. Conditional Statement is the parameter where we include logical operators (and ,or, not),Identity operators(is ,is not),membership operators (iin,not in),comparisional operators(==,!=,>, <,<=,>=)


Within this process, we apply a filter operation to sort and extract records based on specific user-defined conditions.

Note : 'data' is fixed in the statement, we can change name of key and value as per requirement.

List of Operators that can be used : [==, !=, <, >, =<, =>, or, and]

Example 1 : Filtering data where Order Status is pending

data['Order Status']=='pending'

Example 2 : Filtering data where vale of "id" is 5 or 6.

data['id']==5 or data['id']==6

Example 3 : Filtering data where order status is not failed and placed before a specific date.

data['Order Status']!= 'failed' and data['Date']<'6/03/2022'

       

       Reference Link:  Filter


Data Target :

Step 1:

·       Select Target Type as “API”

 

SS7.png

 

Step 2:

·       Select the Target Name as “Salesforce”

SS8.png

 

Step 3:

·       According to the business requirements select the business object

SS9.png

 

Step 4:

Once the business object is selected all the pre-requisites are loaded, if needed changes can be made to all the headers given.

SS10.png

 

Step 5:

Now you can navigate to Summary page and click on “Submit”.

Back to top