# JobBOSS Custom Reports: Building and Editing Crystal Reports

> Source: https://netray.co/erp-help/jobboss-custom-reports-crystal-reports
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

JobBOSS reports are Crystal Reports (.rpt) files that read the JobBOSS SQL Server database. To customise one, copy the standard report, open the copy in Crystal Reports, point it at your database, change the fields or layout, and place it where JobBOSS looks for custom reports. JobBOSS2 reporting differs, so check the supported report tooling for your edition.

## Kind

how-to

## System

job-shop-erp

## Erp

JobBOSS and JobBOSS2

## Module

Reporting / Crystal Reports

## Query

jobboss custom reports

## Alternate Queries

- jobboss crystal reports
- how to edit jobboss reports
- jobboss report designer

## Applies To

JobBOSS (SQL Server) with Crystal Reports. JobBOSS2 report tooling may differ; confirm with the vendor.

## Steps

### Create or edit a custom report

**Items:**

- Find the standard report file (.rpt) used by the JobBOSS screen or menu, and copy it with a new name. Never edit the original.
- Open the copy in a compatible version of Crystal Reports on a workstation that can reach the JobBOSS database.
- Use Database, Set Datasource Location to point the report at your SQL Server and JobBOSS database, then Verify Database.
- Add or remove fields from the tables and views the report already uses, or add a table and define the join, usually on the job number or customer.
- Add parameters or selection formulas for date range, customer or status so users can filter at run time.
- Preview with real data, compare totals to a known JobBOSS screen or report, and fix grouping issues.
- Save the report in the folder JobBOSS uses for custom reports (or the location your reseller configured) and register it if the application requires it.
- Keep a copy and a change note, since upgrades can overwrite the standard reports folder.

## Sections

### Key tables to build from

**Body:**

Most shop reports are built from a handful of tables: Job and Job_Operation for work and routing, Material and Material_Req for bills and requirements, Customer, Delivery for shipments, Invoice_Header and Invoice_Detail for billing, PO_Header and PO_Detail for purchasing, and Employee and time tables for labor.

Verify names and relationships in your database before designing, as versions differ. Joining on the job number is the common pattern; be careful with one-to-many joins that multiply totals.

### Deploying and maintaining reports

**Body:**

Report files must exist where the client can read them. In multi-user installs that is typically a shared network folder; a stale local copy is the usual reason a report shows old layout on one PC.

Use a naming convention such as a company prefix, and keep the source in version control or a backed-up folder. Treat reports as code: a change should be reviewed and tested before it replaces the one users rely on.

### JobBOSS2 and alternatives

**Body:**

If JobBOSS2 does not support custom Crystal files in your edition, ask the vendor about the supported reporting route, or about a read-only data feed for an external tool such as Power BI. Do not assume a Crystal workflow carries over.

For ad hoc questions, many shops move to a reporting layer or an AI assistant over a read-only copy of the data, leaving Crystal for fixed forms such as travelers and invoices.

## Pitfalls

- Editing the standard report in place and losing the change at the next upgrade.
- Crystal Reports version or database driver mismatch causing blank or failing reports.
- Joins that duplicate rows and inflate totals.
- Hard-coded server names or credentials in the report that fail on other workstations.
- Running large reports against the production database at peak times.

## Ai Angle

Many custom report requests are really questions, such as which jobs shipped late last month by customer. A private assistant over a read-only copy of your JobBOSS database can answer them directly, with the SQL shown, leaving Crystal for fixed forms. Netray deploys this on-prem so shop data stays on your network.

## Faq

### What reporting tool does JobBOSS use?

**Answer:** Classic JobBOSS uses Crystal Reports (.rpt files) against its SQL Server database. Check the supported reporting tools for JobBOSS2 with the vendor, since they may differ.

### How do I change a JobBOSS report?

**Answer:** Copy the standard .rpt file, open the copy in Crystal Reports, set the datasource location to your database, edit the layout or fields, test with real data, and save it where JobBOSS reads custom reports.

### Why does my edited report not appear in JobBOSS?

**Answer:** Usually it was saved in the wrong folder, under a name the application does not look for, or a local copy is being used instead of the shared one. Check the configured reports path with your reseller.

### Can I use Power BI instead of Crystal Reports?

**Answer:** For analysis and dashboards, yes, via a read-only connection to the SQL Server database. Crystal remains common for printed forms embedded in JobBOSS screens.

## Search terms

jobboss custom reports, jobboss crystal reports, edit jobboss report, jobboss rpt file, jobboss report designer, jobboss job costing report, jobboss sql tables, crystal reports set datasource location, jobboss2 reports, jobboss reporting

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json