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
Step 2:
· Now select the “Salesforce” as your product
Step 3:
· Choose the appropriate business object based on your needs.
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.
· Next, enter the instance identifier and Authorization details into the provided placeholders.
Configuration Keys in Refresh Token Endpoint Body :
-
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. -
client_id
: Represents the unique identifier assigned to the client (application) by the authorization server during the registration process. -
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. -
username
: Refers to the username or identifier of the user accessing the API. This is typically used in combination with the password grant type. -
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.
· Give the username and password for accessing the Bizdata universal API (For username and password connect with the Bizdata support team.)
The above mentioned username and password should be passed in the format shown below inside the Request Token Endpoint Body.
{"username":"xxxxxx","password":"xxxxxxxxxxxx"}
Step
Data 5:Operations :
·Single Now,Line selectto Multiline
This 'Single Line to Multiline' operation facilitates the Bodytransformation header. Configure theof JSON data usingfrom followinga steps
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
Configuration KeysAppend:
jdbc_string:
Thiskeyoperationrepresentsallows for theJDBCadditionconnectionofstringausednew 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 toconnecttarget keys, thereby composing the payload intended for transmission to theSQL Server database. The connection string has the following format: jdbc:sqlserver://{{host_ip}}:{{port_number}};databaseName={{schema_name}};encrypt=true;trustServerCertificate=true;
{{host_ip}}: Replace this with the IP address or hostname of the SQL Server machine.{{port_number}}: Replace this with the port number on which SQL Server is listening.{{schema_name}}: Replace this with the name of the database schema or catalog you want to connect to.
Note: The "encrypt=true;trustServerCertificate=true;" part of the connection string enables SSL encryption for secure communication with the SQL Server. If your SQL Server is not configured for SSL encryption, you can remove this part from the connection string.
jdbc_path: This key represents the path to the JDBC driver file on your system. It should point to the location where you have stored the "mssql-jdbc-10.2.0.jre8.jar" driver file. Ensure that the path is correctly specified to enable the application to load the JDBC driver.jdbc_driver: This key specifies the fully qualified class name of the JDBC driver for SQL Server. In this case, the value is "com.microsoft.sqlserver.jdbc.SQLServerDriver". It is important to have the correct driver class name to ensure that the JDBC driver is properly loaded and registered with the Java application.username: This key represents the username or login credentials required to access the SQL Server database. Replace the placeholder "{{Username}}" with the actual username or login name associated with your SQL Server database.password: This key represents the password associated with the provided username or login credentials. Replace the placeholder "{{Password}}" with the actual password associated with your SQL Server database.query:This key represents the SQL query that you want to execute on the database. In this example, the query is set to "Select * from tablename". Replace "tablename" with the actual name of the table or the desired SQL query that you want to execute.
Data OperationsTarget.
Reference :
· According to the business needs Operations can be applied, For more information on operations you can visit the Bizdata Help page.Append
Data Target :
Step 1:
· Select Target Type as “API”
Step 2:
· Select the Target Name as “Salesforce”
Step 3:
· According to the business requirements select the business object
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.
Step 5: