Secure Data Connector (Deprecated)

Secure Data Connector Developer's Guide Tutorial: Spreadsheets

This tutorial shows how to import and display data in Google Spreadsheets. The first section uses public data so that you can test this use of Spreadsheets. The second section requires that you first install Secure Data Connector (SDC) as described in Installing, which requires additional time and resources to complete. Thereafter, you can test the use of SDC and Spreadsheets using data that is private to your network and resides on a web server in your corporate network.

Contents

  1. Importing Public Data to Google Spreadsheets
  2. Importing Private Data to Google Spreadsheets

Importing Public Data to Google Spreadsheets

You can import a data source to a spreadsheet as follows:

  1. Create or open Google Spreadsheets and click in any cell.
  2. Enter an equal sign (=) and enter the following importData command to import data from a web site. Google provides test data for this tutorial as a comma-separated value (CSV) file:
    =importData("http://code.google.com/securedataconnector/docs/tutorials/contacts.csv")

    The spreadsheet lists the function names as you type:

    Spreadsheet hint text lists import commands

    After you enter the importData command, Google Spreadsheets requests the data from the file and loads the information into the spreadsheet.

    The spreadsheet then lists the contents of the CSV file:

    Spreadsheet displays imported CSV file

Importing Private Data to Google Spreadsheets

The next section imports private data. Private data means data that resides behind a firewall and is accessed with a URL from a web server in your intranet.

Note: This section assumes you have Installed the SDC. If SDC is not currently installed, you should complete that activity before returning to this tutorial to complete the remaining sections.

After completing an import using a public feed source, create a private data file by installing Secure Data Connector (SDC), copying the CSV file to a web server on your network, and then creating a spreadsheet by importing the data file from your network.

Note: Comma-separated value (CSV) files must have a .csv file type to work correctly with Google Spreadsheets.

To import private data:

  1. Download the Google CSV file and put the CSV file on a web server in your corporate network.

    You can also use a CSV file that you create by exporting a Google Spreadsheet as a CSV file:
    Create a comma-separated value file from Google Spreadsheets from the File > Export > CSV file option
  2. Create a rule in resourceRules.xml for the location and access of the CSV file (or add the <rule> code block to the existing resourceRules.xml file). See Configuring for more information. For example, if Polly Hedra wants to access the CSV file, specify the following resource rule:
    <resourceRules>
      <rule repeatable="true">
        <ruleNum>1</ruleNum>
        <agentId>sdc42-agent</agentId>
        <viewerEmail repeatable="true">pollyhedra@example.com</viewerEmail>
        <url>http://corp.example.com/contacts.csv</url>
        <urlMatch>URLEXACT</urlMatch>
        <apps>
          <service>Spreadsheets</service>
          <allowAnyAppId>true</allowAnyAppId>
        </apps>
      </rule>
    </resourceRules>

    SDC uses resource rules to limit which users can access which corporate resources. The <resourceRules> element defines a source of information that is made available from a web server. The <rule> element defines what resources or applications that a Google App can access. This rule states that this is the first resource rule to be processed (by the <ruleNum>1 statement), that Polly Hedra may access the contacts.csv file at example.com (<url> statement).


  3. Perform the import again using Google Spreadsheets and the URL of the CSV file on your corporate network. In the previous example, the command would be:
    =importData("http://corp.example.com/contacts.csv")

    The data appears just the same as when you imported public data.

Authentication required

You need to be signed in with Google+ to do that.

Signing you in...

Google Developers needs your permission to do that.