Overview

Now that we have a OneCloud Workspace setup, connections to Workiva, and a running chain to load data to Wdesk, let's create a new chain by copying a chain for loading data to Wdata.

Primary Learning Objective

This exercise is designed to highlight the loading of data from a data file into Workiva.

Secondary Learning Objectives

This exercise also highlights using the HTTP BizApp and passing variables from one chain to another.

Prerequisites

Configure Workiva Connections

Configure Source Connections

Supporting Template

Load Data to Wdata


Step 1: Copy a Chain & Remove Commands

  • On the left-side panel, navigate to Build ➡️ Chains.

  • Copy the "Load Data to Wdesk" Chain by clicking the ellipse to the far-right side, then selecting "Copy".

  • Edit the newly-copied chain by selecting the pencil icon.

  • Delete all the Commands except the first two

    • Click on each Command, then select the garbage-icon.

  • Rename the Chain by clicking on "Chain Settings" and altering the name to "Load Data with Wdata".

  • Save the changes.

Step 2: Create a Wdata Table

Add a table in Wdata based upon the source data set.

📓 The columns in the target table need to match the source data. In the case of the SAMPLE_TRANS.csv data, the following fields are required:

Name

Value Type

Mode

INV_NUM

String

Required

REV_TYPE

String

Required

STATUS

String

Required

INV_DATE

Date

Required

PAY_DATE

Date

Required

AMOUNT

Number

Required

CUSTOMER

String

Required

  • Add the Create Table Command:

    • Search for Workiva ➡️ Table Management ➡️ Create Table

    • Click-and-drag the "Create Table" Command to the canvas.

  • Connect the "Preview Data" Command to "Create Table"

  • Double-click the "Create Table" Command to make the following changes:

    • Rename the Command "Create Wdata Table".

    • Name the table: "SAMPLE_TRANS_ChainExecutorID".

      • Type "SAMPLE_TRANS_".

      • Then use the variable picklist on the left-side to concatenate the Chain.ExecutorId.

        💡 Runtime 🔽 Chain.ExecutorId.
        📓 Adding the system variable Chain Executor Id, guarantees that the creation of the spreadsheet will be unique.

    • Optionally, provide a description of your choice. Here, "Sample Data" is listed.

    • Set the type to Data (default).

    • Add the required columns based upon the table above.

      📓 Value Type "Number" is not an available option. Users must select either "Integer" or "Float" for the variable "Amount".

    • Save the changes.

Step 3: Create File

  • Add the Create File Command:

    • Search for Workiva ➡️ File Management ➡️ Create Table

    • Click-and-drag the "Create File" Command to the canvas.

  • Connect the "Create Table" Command to "Create File"

  • Double-click the "Create File" Command to make the following changes:

    • Give the Command the name: "Wdata: Create File".

    • Set the Table ID to be the ID output from the prior command.

      • 💡 Create Wdata Table 🔽 Table 🔽 Id

    • Set the File to the Response from the Retrieve Data output.

      • Get Transactions 🔽 Response

    • Name the file: "SAMPLE_TRANS_ChainExecutorID.csv"

      • Type "SAMPLE_TRANS_"

      • Then use the variable picklist on the left-side to concatenate the Chain.ExecutorId

        💡 Runtime 🔽 Chain.ExecutorId
        📓 Adding the system variable Chain Executor Id, guarantees that the creation of the spreadsheet will be unique.

    • Save the changes.

Step 4: Import File into Wdata Table

Create a Workiva Spreadsheet in Wdesk to load the retrieved transaction data.

  • Add the Import File into Table Command:

    • Search for Workiva ➡️ Table Management ➡️ Create Table.

    • Click-and-drag the "Import File into Table" Command to the canvas.

  • Connect the "Create Table" Command to "Create File".

  • Double-click the "Create File" Command to make the following changes:

    • Set the Table ID to the output of the Command "Create wdata table".

      • 💡 Create Wdata Table 🔽 Table 🔽 ID.

    • Set the File ID to the output of the Command "Workiva: Create file".

      • Wdata: Create File 🔽 Result 🔽 ID.

    • Scroll down to Column Mappings and click the corresponding "+" icon to add seven (7) fields for the following keys and values:

    • Save the changes.

Key

Value

INV_NUM

INV_NUM

REV_TYPE

REV_TYPE

STATUS

STATUS

INV_DATE

INV_DATE

PAY_DATE

PAY_DATE

AMOUNT

AMOUNT

CUSTOMER

CUSTOMER

Step 5: Publish & Run the Chain

Publishing is an important feature in OneCloud. Chains must be published, before they can be run. A Chain and its respective Commands will not be executed otherwise. Whether making one alteration or many, the Chain must be published every time a Chain or Command is edited.

Publish ➡️ Execute ➡️ Run Chain.

  • To publish a Chain, click "Publish" near the upper-right corner.

  • Optionally, add a Publish Chain Comment. For this example, leave it blank.

  • Once published, the "Execute" button becomes active. Click it.

  • Once executed, the "Run Chain" button is activated. Click it.

  • The Chain will animated when it is running.

  • Click on the Anaplan Upload File Command.

  • When the Chain has been run, the outputs will be available to view.


📚 Related Topics from this Section:

Copy a Chain

Chain Variables


Did this answer your question?