Import Blend Data

The workflow name used can be Blend, Blend Workspace, or Workspace Blend. Your import options are the same as other OneStream Workflows that commonly result in cube data.

The configuration of BI Blend is managed in the Workflow Profile. However, some of the Stage Engine's workflow properties may not be valid or used in BI Blend configurations. The primary configuration for BI Blend is done using the workflow name and BI Blend settings. The BI Blend Engine's architecture, such as in-memory processing, makes some workflow properties, such as the Append Default Load Method, an invalid selection. Such selections do not have an effect on workflow blend behaviors.

Data can be collected using:

  • Files (Fixed or Delimited)

  • Connectors

  • Other workflow Stage data

The workflow shows the blend import completed successfully

Delimited Files

When loading data to a BI Blend workflow using a delimited file, a bypass must be used if the first row of the file contains column headers.

A Bypass is highlighted and settings display

How to Use a File Bypass

Use a bypass to prevent file load failures in cases where a delimited file contains column headers.

  1. Create a bypass:

    1. Navigate to Application > Data Collection>Data Sources.

    2. Under Delimited Files, select a data source.

    3. Click Create Source Dimension.

    4. From the Name drop-down menu, select Bypass.

    5. Click the OK button. The default Bypass Type is Contains Within Line.

    6. In the Bypass Value field, type the name of the first column header.

    7. Click the Save button.

  2. Load the delimited file into a BI Blend workflow.

Static Values in Fields

In Platform Version 7.4.4 to Platform Version 8.1.3, field values are bypassed if a Static Value is applied to the field. In Platform Version 8.2 and later, fields with a Static Value are no longer bypassed.

To replicate this functionality and drop certain lines, typically headers, create a Complex Expression or Business Rule that bypasses the field.

For example, the following rule, applied to the Account field, would ensure the line containing the Account header is ignored:

Copy 
'Check the parsed value for the criteria string
If StringHelper.FindIgnoreCase(args.Value, "Account") Then
    'Set the bypass switch on the globals object in order to tell the parser engine to skip this line.
    globals.Bypass = True
End If
Return args.Value