Input fields:

• Display Name: see report fields
• Name: see report fields
• Description: see report fields
• Type: The type of a row describes where it collects the data (see description on the right). Depending what type is selected the options to configure the type are displayed below:
• Invoice: Collects data from the Invoices Table
• Invoice Line: Collects data from the Invoice Lines Table
• Profit and Loss: Collects data from the ledger accounts imported from the bookkeeping software
• KPI: Collects data from "Manual Data Points" (time based static values) (see Settings > Manual Data Points)
• Formula: Use existing report variables or row results to calculate a value
• SQL: Use a predefined SQL query (see Settings > SQL Query). These SQL queries can only be defined/edited by admins (for security reasons)
• Conversion Row: Collects data from Invoice Lines Table
• Alias Normalisation Factor: (currently not in use)

Enter display name and description and, as we want to count invoices, select type "Conversion". The options are now displayed below:

Input Fields:

• Visibility: Select if the row should be displayed on the dashboard table/chart. Select "hidden" if the result is only used for calculations.
• Aggregate: A row can only have one result (but different columns in case of grouping). Select the method how the results (of each column) should be aggregated.
• Column: The database column used for calculation or a column based function (like "distinct") depending of the selected aggregate function.
• Date Filter: The Date Range Variable (Global or Report scope) that contains the date period where the invoices are collected from. Please note that reports variables with the same name (case sensitive) are overriding global variables.
• Filter Button: It's possible to add additional filters by comparing a column to a variable (global/report scope, only matching variable types are shown), e.g. "Products" "greater than" "transactional_xray" to count only radiography products
• Filter Logic: allows boolean operations on the defined filters (currently not implemented)

The person who did the procedure isn’t necessarily the person who spoke to the client and gave the recommendation. Conversion lines are used where the system looks back at the patients history, identifies when the most recent client facing event occurred, and allocates the credit of that particular procedure to the person who did the recommendation- not the procedure.

Below is an example on how conversion lines are used on individual staff performance reports.