Data-flo
Data-floSource CodeCGPS
  • INTRODUCTION
    • What is Data-flo
    • Getting Started - Sign In
    • Privacy and Terms Of Service
    • Contact - Help & reporting errors
    • Change log
  • USING DATA-FLO
    • Data-flo site navigation
      • Transformations Page
      • Run Page
      • Canvas
    • Data
      • Bringing data in to Data-flo
      • Getting data out of Data-flo
      • Data Types
        • Boolean
        • Datatable
        • File
        • Graph
        • List
        • Map
        • Number
        • Text
    • Regular Expressions (RegEx)
    • Adaptors overview
      • Components of an adaptor
      • Binding types
        • Bind to Data-flo input
        • Bind to value
        • Bind to another transformation
    • Specific adaptors
      • add-column
      • append-to-list
      • calculate-time-difference
      • change-column-case
      • columns-concatenation
      • concatenate-text
      • create-microreact-project
      • csv-file-to-datatable
      • csv-to-datatable
      • datatable-columns
      • datatable-to-csv-file
      • datatable-to-graph
      • datatable-to-list
      • datatable-to-map
      • datatable-to-sqlite-file
      • date-to-text
      • dbf-file
      • dot-to-graph
      • download-file
      • dropbox-file
      • epicollect-project
      • extend-datatable
      • figshare-file
      • file-to-text
      • filter-blank-values
      • filter-columns
      • filter-list
      • filter-rows
      • filter-rows-numerically
      • force-directed-layout
      • format-date-column
      • forward-geocoding
      • ftp-file
      • gather-rows
      • google-drive-file
      • google-spreadsheet
      • graph-to-dot
      • join-datatables
      • list-to-datatable
      • lookup-map-value
      • merge-datatables
      • merge-lists
      • microreact-project
      • mysql-database
      • newick-leaf-labels
      • oracle-database
      • postgress-database
      • prepend-to-list
      • remove-columns
      • remove-duplicate-rows
      • rename-columns
      • replace-blank-values
      • replace-column-values
      • replace-text
      • replace-text-in-list
      • replace-value
      • reverse-geocoding
      • row-column-value
      • s3-file
      • select-columns
      • send-email-message
      • slice-datatable
      • slice-list
      • smb-file
      • sort-datatable
      • sort-list
      • split-column
      • split-datatable-rows
      • split-list
      • split-text
      • spread-rows
      • spreadsheet-file
      • sql-server-database
      • sqlite-database
      • sum-rows
      • text-template
      • text-to-file
      • unique-list-items
      • update-epicollect-entries
      • update-microreact-project
      • update-smb-file
      • upload-file-to-google-drive
      • upload-files-to-google-drive
      • url-builder
      • yaml-to-json
    • Building a data-flo
      • Debugging mode
      • Show detailed errors on Run Page
      • Permissions - Access Control
    • Tips & Tricks
  • TUTORIALS
    • Prep outbreak data for Microreact
    • Common use cases, solved
      • Fixing datatable headers
      • Select, remove, rename, reorder columns
      • Data in separate files
      • There's no single-column unique row ID (primary key)
      • Ensure non-dates stay non-dates
      • Connect directly to a database
      • Access files on a drive
Powered by GitBook
On this page
  • How to use 'Bind to a Data-flo input'
  • Secret inputs
  • Allowed Values
  • Remove binding
  • How inputs look on the Run Page

Was this helpful?

  1. USING DATA-FLO
  2. Adaptors overview
  3. Binding types

Bind to Data-flo input

Value to be provided by the user at Run-Time

When using the Bind to Data-flo input binding, the value for the argument can be defined by the user each time the data-flo is run. This is the easiest way to make a data-flo flexible to handle various similar data files.

A few of the many use cases:

  • Different users have similar files stored in different locations, and will need to point the data-flo accordingly (e.g. files saved on individuals' local computers)

  • Different values for a text or number field will be used from run to run (e.g. setting the numeric threshold for a filtering adaptor)

TIP: name your input and add plenty of information to the input description (in the right sidebar) so users know what they need to input. This is especially helpful when a data-flo’s inputs and outputs are going to be provided in a nested data-flo.

How to use 'Bind to a Data-flo input'

As shown in images below:

  1. Select "Bind to a Data-flo input"

  2. Click on the PLUS next to "Input argument"

  3. This adds the input box, which will be labeled with the argument name.

  4. Click on the new input box to bring up the "Input details" sidebar.

  5. Set the default value options:

    1. If the user must always enter a value at run-time, select "A value is required"

    2. In rare cases when no value is required from the user or a preset default, choose "Optional without a default"

    3. If the user can enter their own value, but a default value is desired (e.g. a numeric filter threshold is usually 0.2 but a user may desire a different threshold), select "Optional with a default value" and set the "Default value" (selecting "Treat default value as secret" is useful for values like API keys or other information that may help the data-flo run, but should not be shared among users or shown on the Run Page)

  6. Change the name of the input as needed, and add a description to assist users in setting the input from the Run Page. The values entered in these fields will be shown on the Run Page's INFO and RUN subpages.

Secret inputs

Default values are not shown on the Run Page, but by default, they do carry over when someone makes a copy of the data-flo.

In some cases, you may want to share a data-flo that contains sensitive information in the default value of a binding. When you want to hide values from others, check the box to "Treat default value as secret"; this leaves the value there, but the default is not shown on the Run Page (and if another user creates a copy of your data-flo, the secret input changes to "A value is required" so your secret doesn't get shared).

Allowed Values

This feature is meant to act similarly to a dropdown. It can be used regardless of whether the input is required, has default, has secret input, etc.

*Known bug alert*-"Allowed Values" feature does not always behave.

Remove binding

When you click the "REMOVE BINDING" button, the argument reverts to its defaults or reverts to blank**.**

If you delete the adaptor for a Data-flo input (e.g. the "target" box in the image above), this will also remove the binding.

How inputs look on the Run Page

The input looks the same on the Run Page, regardless of how it is configured, with the exception of the use of "Allowed Values". See images.


PreviousBinding typesNextBind to value

Last updated 2 years ago

Was this helpful?

Setting the Data-flo input
Defining the default values and descriptions of the Data-flo input
When a data-flo is copied, the bound-value inputs marked as "secret" do not get carried over to the copy.
Configurations noted in argument input descriptions
Run Page view is same for all options except when "Allowed Values" is used (description shows, as does dropdown)