BRD File - Data360_Analyze - 3 - 3.12

Data360 Analyze Server Help

Product type
Product family
Data360 Analyze
Product name
Data360 Analyze
Data360 Analyze Server Help
First publish date

Imports and processes internal Data360 Analyze format (.BRD) files.

A BRD file is typically generated as an intermediate file or checkpoint file during the execution of a data flow.

To import a single BRD file, in the File property, enter the path of the BRD file that you want to import.

To import multiple BRD files, you first need to add an input to the BRD File node. For example, the Directory List node is often used to import a list of files. Then select the (from Field) variant of the File property and enter the name of the input field that contains the list of BRD files that you want to import.



Click the folder icon and browse to the BRD file that you want to import.

Choose the (from Field) variant of this property to look up the BRD file name(s) from an input field with the name specified.

A value is required for this property.

Note: If you are using the server edition and wish to use a file on your local machine, you must first upload it to the Data360 Analyze server. Please see the topic Uploading data to the server for more details.


Optionally specify which input fields will "pass through" the node unchanged from the input to the output, assuming that the input exists. The input fields specified will appear on those output records which were produced as a result of the input fields. Choose from:

  • All - Passes through all the input data fields to the output.
  • None - Passes none of the input data fields to the output; as such, only the fields created by the node appear on the output.
  • Used - Passes through all the fields that the node used to create the output. Used fields in this case will be a field referenced in the File property when using the from Field option.
  • Unused - Passes through all the fields that the node did not use to create the output.

The default value is None.

If a naming conflict exists between a pass-through field and an explicitly named output field, an error will occur.


Optionally specify whether, even if when parsing an input record the corresponding file contains no BRD records, the pass through fields are still written. Note that the File specified on the input must still exist and be a BRD file containing valid metadata.

If set to false (the default value), the pass through fields are output only when there are other records to include in that output with parsed data fields.


Optionally specify how to merge data if processing multiple input files. Choose from:

  • Union - Outputs all of the fields across the inputs, filling in nulls for fields not present in a given input.
  • Exact - The fields for all inputs must be the same.
  • Intersection - Outputs all the fields common to the inputs.

The default value is Exact.


Optionally specify how to handle columns that have the same name, but different types when processing multiple input files. Choose from:

  • None - No type conversion, all fields must match exactly.
  • Numeric - Numerical conversions will occur, int --> longint --> double precision float.
  • Unrestricted - Numerical conversions will occur - additionally, incompatible types will be converted to string if possible.

The default value is Numeric.


Optionally specify whether to create a reference (symbolic link) to the original file on the output pin, otherwise a copy of the file is created for output.

The default value is False.

Choosing True will improve performance.

This property can only be set to True if processing a single input file and has no impact when the node is running on a windows platform.


Optionally specify whether to skip reading the file to determine the number of records. The record count will be reported as zero.

The default value is False.

Choosing True improves performance.

Inputs and outputs

Inputs: None.

Outputs: BRD Data.