Skip to main content

Designing and using b.print reports

Applies to: ✅ Microsoft Dynamics Business Central & b.print​

The b.print Design Reports section is a powerful tool to create own reports instead of utilizing the standard BC reports. It is a simplified version offering a quick and easy report design.

Prerequisites​

In order to follow through with the setup and test of b.print reports, you need:

  1. A set up Business Central environment.
  2. The necessary network printers are reachable from the users clients and visible within the Network Printers in Business Central.
  3. The b.print driver has been installed to a network printer.
  4. A webservice key has been created on the print servers/printers side which enables access to the print sever. (This process differs depending on the printer used)
  5. The b.print extension has been installed to the desired BC environment.
  6. All settings relevant to the Assisted Setup have been configured.

Creating a new b.print report desgin​

In the following, we are going to set up a brand new custom b.print report.

  1. Navigate to the Business Central Search
  2. Search for b.print Design Reports and open the page.
  3. Click on New to create a new Report
  4. In the field Code, enter a fitting code for your new Report (eg. ORDERCONFIRMATION)
  5. In the field Name, define a fitting name for the report. (eg. Sales Order Confirmation)
  6. In the field Description, enter a fitting Description for your new Report (eg. A standard Cronus Sales Order Confirmation)

Tables​

You can define Tables from which the report can pull information. In the following, we are going to define tables for this purpose.

  1. Navigate to the section Tables
  2. Under Table ID, select a table from which the information in the report should originate. (eg. table 36)
  3. Under Alias, select a unique alias used in designer field bindings
  4. Under Is Sub Table select whether the selected table is a sub table fof another table (eg. for table 37 "Sales Line", this should be checked)
  5. Under Parent Alias, write an alias for the parent table (eg. SALES HEADER)

Design Variants​

.............