Notations for Excel exports
  • 26 Oct 2023
  • 1 Minute to read
  • Contributors
  • Dark
    Light
  • PDF

Notations for Excel exports

  • Dark
    Light
  • PDF

Article Summary

This article applies to BOOST EMPOWER licenses

Purpose and scope

Cooperlink has advanced features to automatically generate excel files based on the data contained in a space, taking into account the filtering rules applied. This article describes how to extract this data to an excel file.

Description

The notation for exporting data in an excel file strongly resembles that used for the constitution of masks (see Fields identifiers in cards and dynamic masks). However, it differs in a few respects:

  • The Mustach notation is not used. The notation uses a combination of a prefix representing the object concerned and a key surrounded by ${.}
    Example: ${project.name}
  • Data export notation can extract data from related items using the prefix
  • Section start and end markers are added to the Excel file to repeat certain dimensions

Export date

In order to extract the date when the file is exported, use the code ${export_content.current_date}

Dimensions

This dimension is used to mark the beginning and end of a section for repetition. To do this, mark any column in the first row to the right of the template with the ${markup} token. Then indicate the sections for the repetition:

Type of repetitionStart notationEnd notation
Workflow versions{prevWorkflows.start}{prevWorkflows.end}
Cards{cards.start}{cards.end}

Repeating objects in the exported list

When you request Cooperlink to export a report, this is done on an object list. This section describes how to tell Excel to repeat the same line for each exported object.

The line to repeat for each exported object is identified by the ${listrow} keyword to the right of the line.

Available fields by object type

Please refer to Fields identifiers in cards and dynamic masks for a list of the keys available for report generation.

Available prefixes by object type

Workspace

PrefixReference toComment
project.*Parent projectThis information differs at partner side

Document

PrefixReference toComment
project.*Parent projectThis information differs at partner side
virtualspace.*Parent workspace

Workflow

PrefixReference toComment
project.*Parent projectThis information differs at partner side
virtualspace.*Parent workspace
target.*Target object (e.g. document)
action.*Workflow action(s)Provides access to response cards using the action key and card key

Workflow Response Card

PrefixReference toComment
project.*Parent projectThis information differs at partner side
virtualspace.*Parent workspace
task.*Parent task

Task

PrefixReference toComment
project.*Parent projectThis information differs at partner side
virtualspace.*Parent workspace
card.*Card embedded in the task
workflow.*Linked workflow


Was this article helpful?