![]() |
VOOZH | about |
The CData API Server enables you to access CSV data from cloud-based applications like the Salesforce console and mobile applications like the Salesforce1 Mobile App. In this article, you will use the API Server and Salesforce Connect to access CSV external objects alongside standard Salesforce objects.
If you have not already done so, download the CData API Server. Once you have installed the API Server, follow the steps below to begin producing secure CSV OData services:
To work with CSV data from Salesforce Connect, we start by creating and configuring a CSV connection. Follow the steps below to configure the API Server to connect to CSV data:
CData Drivers let you work with CSV files stored locally and stored in cloud storage services like Box, Amazon S3, Google Drive, or SharePoint, right where they are.
Set the URI property to local folder path.
To connect to CSV file(s) within Amazon S3, set the URI property to the URI of the Bucket and Folder where the intended CSV files exist. In addition, at least set these properties:
To connect to CSV file(s) within Box, set the URI property to the URI of the folder that includes the intended CSV file(s). Use the OAuth authentication method to connect to Box.
To connect to CSV file(s) within Dropbox, set the URI proprerty to the URI of the folder that includes the intended CSV file(s). Use the OAuth authentication method to connect to Dropbox. Either User Account or Service Account can be used to authenticate.
To connect to CSV file(s) within SharePoint with SOAP Schema, set the URI proprerty to the URI of the document library that includes the intended CSV file. Set User, Password, and StorageBaseURL.
To connect to CSV file(s) within SharePoint with REST Schema, set the URI proprerty to the URI of the document library that includes the intended CSV file. StorageBaseURL is optional. If not set, the driver will use the root drive. OAuth is used to authenticate.
To connect to CSV file(s) within Google Drive, set the URI property to the URI of the folder that includes the intended CSV file(s). Use the OAuth authentication method to connect and set InitiateOAuth to GETANDREFRESH.
π Connecting to a datasource (SQLite is shown)Next, create a user to access your CSV data through the API Server. You can add and configure users on the Users page. Follow the steps below to configure and create a user:
Having created a user, you are ready to create API endpoints for the CSV tables:
Having configured a connection to CSV data, created a user, and added resources to the API Server, you now have an easily accessible REST API based on the OData protocol for those resources. From the API page in API Server, you can view and copy the API Endpoints for the API:
π API EndpointsFollow the steps below to connect to the feed produced by the API Server.
URL: Enter the URL to the OData endpoint of the API Server. The format of the OData URL is https://your-server:your-port/api.rsc.
Note that plain-text is suitable for only testing; for production, use TLS.
Select JSON in the Format menu.
After you have created the external data source, follow the steps below to create CSV external objects that reflect any changes in the data source. You will synchronize the definitions for the CSV external objects with the definitions for CSV tables.
After adding CSV data as an external data source and syncing CSV tables with CSV external objects, you can use the external objects just as you would standard Salesforce objects.
Create a new tab with a filter list view:
π A filtered list view shown on a custom tab. (NetSuite Invoices are shown.)Display related lists of CSV external objects alongside standard Salesforce objects:
π A related list that shows an indirect lookup relationship, which links a child external object to a parent standard object. (Salesforce accounts and associated NetSuite invoices are shown.)You can use the following checklist to avoid typical connection problems:
Ensure that the server you are hosting the API Server on is using TLS 1.1 or above. If you are using the .NET API Server, you can accomplish this by using the .NET API Server's embedded server.
If you are using IIS, TLS 1.1 and 1.2 are supported but not enabled by default. To enable these protocols, refer to the how-to on MSDN and the Microsoft technical reference.
If you are using the Java edition, note that TLS 1.2 is enabled by default in Java 8 but not in Java 6 or 7. If you are using these earlier versions, you can refer to this this Oracle how-to.
Learn more or sign up for a free trial:
CData API Server