Generic filters

BOMLink | Output

The end result of BomLink is to output all results to a format required. It support many formats. There are two sections to the output:

Output DestinationType of output to store rule result and location to save output.
Output Definition (Global Level)Fields to store in the output file.

Output destination types

Specify the output type that the rule sends its result to and the location to save the output file.

  • Csv output.
  • Excel output.
  • HsbMap output.
  • Jasper Report output (pdf).
  • MS Access output destination.
  • Sql output destination.
  • SqlCe output destination.
  • SQLite output destination.

Csv output

Output PathSpecifies the path of the CSV file to create.
DelimiterSpecifies the delimiter of the CSV file to create. Empty will use ‘,’ as the delimiter.
Output row numbersProduces a column for row numbers.

The delimiter will be set to automatic ‘;’ delimitation if the Regional settings have the decimal separator as ‘,’.

Excel output

Start columnThe column where the output will start.
Start RowThe row where the output will start.
Template PathThe path of the Excel template to be used (an xlsx file).
Output Path FormatFormat specifying the path where the excel output will created.

Jasper report output (pdf)

Output Path FormatFormat specifying the path where the output will be created.
Output FormatSpecifies the type of report to output.
Path to LogoPath to the logo that will be used for the reports.
Report NameName of the report.

Create an output Destination

Step 1. Select the destination.

Step 2. Click on Add.

Step 3. Select the Output Path.

add @(Number) or @(Comment) to the path, for additional information to the file.
add @(DwgPath) at the start of the path to create the output directly into the dwgfolder.
e.g. C:\BomLink\@(Number).csv
e.g. @(DwgPath)\@(comment).csv
e.g. @(DwgPath)\Reports BomLInk\Quantifier

Create an Output Definition (Global Level)

You set the fields (Represents the headers) to store in the output file. This is the output at a global level.

Step 1. Add a column header in the field.

Step 2. Click on add.

Step 3. Map this field to the information you need to see in the output file.

Step 4. Select the Type of the field item. String, Double, Boolean, ..etc.

Create an Output Definition (Rule Level)

It is possible to force an additional type of mapping on rule level.

Note this will over-ride the field setting at global level .e.g. Output the PosNum.

Step 1. Select a Rule.

Step 2. Select the Output tab.

Step 3. Select the correct Output Definition.

Step 4. Check the lightbal On.

Step 5. Overwrite the requested info. e.g. m.PosNum.

Instead of Code, the posnum will know be shown.

Example of an Output Definition at rule level

Situation: Output a rule that overides the global output definition that presently displays the inventory description, replacing it with the length of the wall. Also if the wall material is Antraciet to display yes or no dependent on a user input.

Task: Create an over-ride output at rule level in the article field to display the wall frame length and add addtional field called material for Antraciet material.

Step 1. Within the article field enter C(‘Length :’, round(m.FrameLength,0), ‘mm’.

  • This will return the string: Length: 2000mm.

Step 2. Within the material field enter if(v.Antraciet=true, ‘YES’, ‘NO’).

  • When the variable is true, this will return the string YES.

Output Preview

Click on preview, select model, change variables.
Updated on 31/12/2021

Was this article helpful?

Related Articles

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support