FinancialForce Connector

• Starter
• Business
• Enterprise
• On-Premise
• Add-on

Overview

Etlworks FinancialForce connector allows the fastest and easiest way to connect to real-time FinancialForce data. The connector works just like any other database connector.

Etlworks partnered with CData to provide access to FinancialForce using industry-standard JDBC protocol. Read about CData FinancialForce JDBC connector.

When to use FinancialForce connector

Use this connector to create Flows that extract data and load data into FinancialForce.

Prerequisites

Enable FinancialForce connector for your Etlworks account. Contact support@etlworks.com to enable the connector.

Create a Connection

Here's how you can create a Connection in two easy steps:

Step 1. In the Connections window, click +, and type in financialforce.

Step 2. Enter Connection parameters:

• Authentication type: select authentication type, either OAuth (default) or Security token.

When using OAuth authentication (default):

• OAuth Token: sign in with SalesForce.

When using Security token authentication:

• User: the email address of the Salesforce user.
• Password: the password (do not append security token to the password).
• Security Token: the security token. Read what a Salesforce security token is and how to find it.

Use Other parameters to specify the Connection string options. Read about available Connection string options.

Work with FinancialForce

FinancialForce Data Model

You can use the connector to work with all of the tables in your account. The driver connects to FinancialForce and gets the list of tables and the metadata for the tables by calling the appropriate web services. Any changes you make to your FinancialForce account, such as adding a new table, adding new columns, or changing the data type of a column, are immediately reflected when you connect using the driver.

Read about the FinancialForce data model.

Stored procedures

Stored procedures are available to complement the data available from the Data Model. It may be necessary to update data available from a view using a stored procedure because the data does not provide for direct, table-like, two-way updates. In these situations, the data retrieval is done using the appropriate view or table, while the update is done by calling a stored procedure. Stored procedures take a list of parameters and return back a dataset that contains the collection of tuples that constitute the response.

Read about available stored procedures in the data model.  

To call stored procure from the SQL Flow or Before/After SQL, use EXEC sp_name params=value. Example:

EXECUTE my_proc @second = 2, @first = 1, @third = 3;

SQL Compliance

The connector supports several operations on data, including querying, deleting, modifying, and inserting.

Read about SQL Compliance.

Extract data from FinancialForce

Extracting data from FinancialForce is similar to extracting data from the relational database.

Here's how you can do this:

Step 1. Create FinancialForce Connection which will be used as a source (FROM).

Step 2. Create a destination Connection, for example, a Connection to the relational database, and if needed, a Format (Format is not needed if the destination is a database or well-known API).

Step 3. Create a Flow where the source is a database and the destination is a Connection created in step 2, for example, a relational database.

Step 4. Add a new source-to-destination transformation.

Step 5. Select the FinancialForce Connection created in step 1 as a source Connection and select the data object you are extracting data from.

Step 6. Select TO Connection, Format (if needed), and object (for example database table) to load data into.

Step 7. Click MAPPING and optionally, enter Source query (you don't need a query if you are extracting data from the FinancialForce data object unconditionally).

Step 8. Optionally, define the per-field Mapping.

Step 9. Add more transformations if needed.

Load data in FinancialForce

Loading data in FinancialForce is similar to loading data into a relational database.

Here's how you can do this:

Step 1. Create a source Connection and a Format (if needed).

Step 2. Create a destination FinancialForce Connection.

Step 3. Create a Flow where the destination is a database.

Step 4. Add new source-to-destination transformation.

Step 5. Select FROM and TO Connections and objects (also a FROM Format if needed).

Step 6. Optionally define the per-field Mapping.

Step 7. Add more transformations if needed.

Browse data in FinancialForce

You must have a FinancialForce Connection to browse objects and run SQL queries.

Use the Etlworks Explorer to browse data and metadata in FinancialForce as well as execute DML and SELECT queries against the FinancialForce Connection.