Pipelineapp.io, an Innovative Way solution.
Learn more @ www.pipelineapp.io


Add-ons

Data field reference

If you request a custom data export for your Asks, you will receive a XLSX spreadsheet with 5 tabs of data. Here is the reference for the data fields:

Note: For data relationship, 1 Ask has many Steps and 1 Step has many Files, Fields, and Activities.

  1. Ask - Header - the overview for the Ask
    • ask_code = Ask unique ID
    • flow_code = flow unique ID
    • version_id = flow version number
    • master_flow_code = flow ID for all versions of the same flow
    • create_date, update_date, close_date = key dates for the Ask
    • contact_* = submitter information
  2. Ask - Step Detail - step information for each Ask
    • is_ad_hoc_step = flag for whether the step was inserted (not part of the flow)
    • step_number = step number
    • step_start_date, step_complete_date, step_due_date = key dates for the step
    • contact_* = contact who currently owns the step, if step status = Completed, this is contact who completed the step
    • team_* = team who currently owns the step, and no one from the team picked it up
    • original_contact_* = contact who initially owned the step
    • original_team_* = team who initially owned the step
  3. Ask - Form Field Values Detail - form field information for each Ask
    • step_code = step that the form field belongs to; if blank, the form field belongs on the Create Ask form
    • step_number = if step_number is 0, the form field belongs on the Create Ask form
    • field_id = field unique ID
    • field_value = field value
    • submit_date = field value submitted date
  4. Ask - File Detail - attachments for each Ask
    • step_code = the step that the attachment was uploaded on
    • attachment_code = attachment unique ID
    • upload_date = attachment upload date
    • contact_* = attachment uploader information
  5. Ask - Activity Detail - additional activity logs for each Ask (excluding the above activities)
    • step_code = the step that the activity occurred on
    • activity_feed_type_id = activity unique ID
    • activity_feed_create_date = activity log date
    • contact_* = contact who performed the activity