Clear Cutover Get a quote

Epicor Kinetic · Reporting

How to add a field to an Epicor Kinetic SSRS report

By Al Hasib Tamim, published 25 October 2026

Applies to: RDD-based Epicor Kinetic SSRS reports, including PackSlip, ARForm, and POForm. Menu labels, report packaging, and upload workflows vary by release and deployment model. The cloud-upload notes below summarize community reports from 2024.x–2025.2 and should be checked against your installed release.

Short answer

To add a field to an Epicor Kinetic SSRS report that uses a Report Data Definition (RDD), the field must exist in three places:

  1. The RDD must expose the column in the report data.
  2. The RDL dataset query must select or return the column.
  3. The dataset field list must contain the returned field so the report layout can reference it.

First, confirm which RDD and report artifact are assigned to the exact report style you use. Then work on a copied RDD and report style, expose the column, update the relevant dataset query and field list in Report Builder, upload the report using the workflow supported by your release, and test the output.

For a customized Epicor-supplied RDL, manually adding a field to the existing query and field list can reduce unintended changes to the report's dataset structure. This is not a universal replacement for Sync Dataset; the appropriate method depends on the report, its customizations, and your release.

Make the change in Pilot or another test environment first. Do not make your first change to a production report style or its base RDD.

How the pieces fit together

Component What It Does Where You Typically Change It
Report Style Associates the report with an RDD and report location or artifact Report Style Maintenance
Report Data Definition (RDD) Defines report tables, relationships, and exposed columns Report Data Definition
RDL Defines the SSRS layout, dataset queries, and dataset field lists Microsoft Report Builder or Visual Studio, depending on the workflow

When an Epicor report runs, the report framework generates data for SSRS. The RDL dataset query reads the relevant report data. As a result, un-excluding a column in the RDD does not automatically make that field available in Report Builder: the RDL query and dataset field list may also need to be updated.

Always check the RDD assigned to the exact style you print. Do not infer it from the report name alone. For example, some Kinetic ARForm styles use the ARInvoice RDD. The configuration can vary by version and environment, and the RDL may expect particular report tables and columns. Before changing an RDD, inspect the style's assigned data definition, report location, and dataset query.

Step-by-step: Add a field

1. Record the Report Style Configuration

Open Report Style Maintenance, load the report you need to modify—for example, PackSlip, ARForm, or POForm—and record:

  • The RDD assigned to the style.
  • The Report Location or report path.
  • The specific report style used when printing.
  • Whether the report or its datasets have already been customized.

Do not assume the style uses the RDD suggested by its name.

2. Duplicate the RDD

Open Report Data Definition and use the RDD duplication action available in your release. Menu names and locations vary, so confirm that you are duplicating the data definition rather than the report style. Give the copy a clear name that identifies it as a custom RDD. Keep the original unchanged so you can compare configurations and roll back if necessary.

3. Expose the Field in the RDD

In the copied RDD, locate the table containing the field and clear Exclude Column. If the associated label also needs to be exposed, clear Exclude Label where applicable. If the field belongs to a table that is not included in the RDD, you may need to add the table and define a relationship to an existing table. Before doing so, confirm the relationship keys and expected cardinality. For the keys between core tables, see the Epicor Kinetic SQL schema cheat sheet.

Check relationship columns carefully. If a relationship uses columns such as Company or OrderNum, verify that the required columns are available to the RDD and are not excluded. Community users have reported relationship issues involving excluded columns, including after upgrades. The exact requirements depend on the RDD and report.

4. Copy the Report Style

Use Copy Report Style to create a separate style for the changes. In the copied style:

  • Assign the custom RDD.
  • Confirm that the Report Location points to the report artifact you intend to edit.
  • Keep the original style available for comparison and rollback.

Do not change the system style just to test a new field.

5. Download and Back Up the Report Artifact

On the copied style, use Download SSRS Report if that action is available in your client and release. In some Kinetic browser workflows, the download is provided as a ZIP archive. If so, extract it before editing and preserve the original archive, filenames, and folder structure. Other workflows may package or expose report files differently; follow the procedure documented for your installed release. Keep an untouched copy of the downloaded files so you can compare or restore them.

6. Edit the Dataset Query

Open the RDL in Report Builder. In the relevant dataset, open Dataset Properties → Query and inspect the existing query expression. Some Epicor report datasets use an expression assembled from text and report parameters rather than a standalone SQL statement. Preserve that structure when editing.

If the source table is already in the query, add the field to the SELECT list using the existing table alias. For example: T1.YourField Use the actual field name and alias from your dataset.

If the source table is not in the query, you may need to add a join and include the required column in the SELECT list. The following fragment illustrates a join pattern reported in a sales order report. It is a structural example only—not code to paste into another report unchanged:

LEFT OUTER JOIN OrderHed_" + Parameters!TableGuid.Value + " T2  ON T1.Company = T2.Company AND T1.OrderNum = T2.OrderNum

Match the table naming, alias conventions, parameter expression, and join keys used by the existing query. Confirm that the join reflects the intended data relationship and does not return multiple matches for a single report line. A one-to-many join can multiply report lines, quantities, or totals. If the query expression is unfamiliar, save a separate copy before editing and compare your changes with the original.

7. Add the Field to the Dataset Field List

In Dataset Properties → Fields, use Add → Query Field and select or enter the field returned by the updated query. The field name must match the name returned by the query. If you use an alias, use that alias consistently in the dataset field list and report layout. A field can be present in the query but unavailable to report textboxes if the dataset field list has not been updated.

8. Place the Field in the Report Layout

Add the field to the appropriate textbox or tablix cell in Report Builder, using the correct dataset field reference. If a subreport retrieves the data independently, inspect its dataset as well. Updating the main report dataset does not automatically update a separate subreport query. Save the edited RDL.

9. Package and Upload the Report

Use the upload workflow supported by your Kinetic release and client. For a Kinetic browser workflow that expects a ZIP package, preserve the required folder hierarchy and filenames from the downloaded package. Re-create the archive in the structure expected by that release; do not assume that uploading only the RDL is sufficient.

Confirm that the copied style's Report Location points to the intended report artifact, then use the corresponding upload action. If Classic Report Style remains available in your environment, its upload workflow may be useful for troubleshooting, but do not assume it is interchangeable with the Kinetic browser workflow. If the upload succeeds but the old layout still prints, verify the style and artifact first. If those are correct, investigate whether a release-specific defect applies to your environment.

10. Verify the Report Output

Print the same representative record using the original style and your copied style. Compare:

  • Whether the new field appears and contains the expected value.
  • The number of report lines.
  • Quantities, subtotals, and totals.
  • Any subreport output affected by the change.
  • Any formatting or pagination changes.

Include a test case that could expose duplicate matches in a joined table. If a supposedly one-to-one join produces multiple matches, investigate the relationship rather than accepting duplicated report data. Do not promote the change until both the new field and the existing report output behave as expected.

Should you use Sync dataset?

For a customized Epicor-supplied RDL, manually adding the required field to the existing dataset query and field list can reduce unintended changes to the report's existing dataset structure. Community discussions have described cases in which Sync Dataset changed queries or field names, caused query failures, duplicated quantities, or affected subreports.

These are community-reported experiences, not proof that Sync Dataset is unsafe for every report. Some contributors recommend it for BAQ reports or other scenarios. Whether it is appropriate depends on the report type, existing customizations, and the intended changes.

If you decide to use Sync Dataset:

  • Back up the original RDL.
  • Work with a copied report style and RDD.
  • Compare the dataset queries, aliases, field lists, and subreports before and after syncing.
  • Print representative records and compare line counts, quantities, and totals.
  • Do not promote the result until the full report output has been tested.

If a report fails after syncing, compare its current RDL and dataset queries with a known-good copy before making further changes.

Troubleshooting: Symptom, likely Cause, and Next check

Symptom Possible Cause What to Check Next
Field is un-excluded in RDD but missing in Report Builder The RDL query or dataset field list has not been updated Add the field to the query and then to Dataset Properties -> Fields
Invalid column name 'YourField' Column absent from report data, missing from query, or expected by mismatched RDD/RDL Identify failing dataset and column; check style's RDD, Exclude Column, and query
Invalid-column errors on copied ARForm The selected RDD and RDL dataset expectations may not match Inspect the exact style's RDD and compare missing columns with dataset query
Invalid column name after upgrade for field not added Customized RDL still selects a column no longer available in report data Compare query with current RDD and confirm column status before changing query
Missing relationship-column error after upgrade Column used by relationship is excluded or unavailable Inspect relationship and required columns; change RDD only after confirming
Quantities or lines print twice Query change, sync, or join changed row cardinality Compare with known-good RDL; check join keys and expected row counts
Kinetic upload displays only "Undefined" Interface may not expose underlying SSRS error If available, try Classic upload workflow to obtain more informative error
Upload succeeds but old layout still prints Style points to different artifact, or release-specific cloud defect applies Verify style, report location, and uploaded artifact; check EpicCare guidance

Kinetic cloud upload issues: Verify current status

Community discussions and an Epicor support-engineer post described specific Kinetic cloud issues in late 2025 and January 2026. The reported symptoms included a custom report upload completing without an error while the old report version continued to print, and custom report entries being incorrectly flagged as system reports in the Ice.ReportStore view under certain PrintProgram conditions.

In a January 2026 post, the reported defect information was:

Defect Reported Behavior Status Stated in Jan 2026 Discussion
PRB0308665 Custom PackSlip, ARForm, and APCheck RDLs upload without errors, but the old report version continues to print Listed as fixed in Kinetic 2026.1; a 2025.2 point-update request was in progress
PRB0308049 Custom report entries in Ice.CustomReportStore are incorrectly flagged as system reports in Ice.ReportStore when PrintProgram <= 200 characters Listed as fixed in Kinetic 2026.1; a 2025.2 point-update request was in progress

These are status details as posted in January 2026. If you are on Kinetic 2026.1 or later, both defects are reported as fixed, so the workaround below should not be needed. On earlier releases, confirm with EpicCare whether the defect applies to your installed version before using a workaround.

A Workaround Reported for Affected Styles

The support post described a workaround, as of Kinetic 2025.1.11 and 2025.2.5, for affected styles in which a comma-separated PrintProgram represents two report paths:

  1. Download the existing custom RDLs from Report Style Maintenance and preserve backup copies.
  2. For each affected ARForm, PackSlip, or APCheck style, create two new styles—one for each path in the original PrintProgram.
  3. Delete the original style only after confirming that the downloaded RDLs are saved and accessible.
  4. Run Conversion Workbench conversion 405.
  5. Confirm that changes to the split styles persist and print correctly. From then on, treat each new style as a separate report.

Other cloud upload considerations

  • Designing SSRS reports in the cloud: Community users have reported that using Generate for Design and Design SSRS Report from Kinetic may require the Edge Agent and, in some environments, the Classic client. Treat these as release- and environment-specific observations; confirm the prerequisites for your setup.
  • Uploading a single RDL: Some users report being able to upload an individual RDL through Classic Report Style where that workflow remains available. It may help expose an error hidden by the Kinetic screen, but it is not necessarily the standard upload method for your release.
  • If an upload succeeds but the old layout still prints, first verify that you edited and uploaded the artifact used by the intended style. If that is correct, investigate whether a release-specific defect applies. Do not assume the problem is caused by ZIP packaging alone.

Looking ahead: Epicor's reported move from SSRS to Bold reports

An EpiUsers forum post dated 8 September 2026 relayed an update from Epicor stating that Bold Reports was actively in development, with first availability planned for Kinetic 2027.100. The update included a safe-harbor statement, so treat this as a plan rather than a guaranteed release date.

This announcement does not, by itself, establish the final migration path, feature parity, compatibility requirements, or how existing custom RDLs will behave. Until Epicor publishes release-specific guidance for your environment, use the SSRS workflow supported by your current Kinetic version and plan to retest custom reports when you upgrade.

If your organization has complex custom reports, keep the source RDLs, document any non-standard datasets and subreports, and include representative report-output checks in your upgrade plan. Confirm migration and compatibility details with Epicor when official guidance becomes available.

FAQ

Why doesn't my new field appear in Report Builder after I unchecked Exclude Column?

Changing the RDD does not automatically update the RDL dataset query and field list. Add the column to the query's SELECT list, then add the returned field under Dataset Properties -> Fields.

Should I use Sync Dataset to add new fields?

Usually not, for a customized Epicor-supplied report. Add the field to the query and field list by hand. Sync Dataset can rewrite queries and field names, and users have reported it duplicating quantities and breaking subreports. If you do use it, work on a copied style and compare the full output before promoting the change.

Which RDD does an AR invoice use in Kinetic?

It depends on the style, so check it in Report Style Maintenance. Some ARForm styles use the ARInvoice RDD rather than one named after the form.

Can I rename the RDL when uploading to Kinetic cloud?

No. Keep the filenames and folder structure from the downloaded package so the style's Report Location still matches the uploaded artifact.

Why does Kinetic Report Style say "Undefined" when I upload?

The Kinetic upload screen often hides the underlying SSRS error. Where Classic Report Style is still available, upload there to see the real message.

Why does the report still print the old layout after a successful upload?

Usually the style points to a different RDL than the one you uploaded, so check its Report Location first. On cloud releases before Kinetic 2026.1, a known defect (PRB0308665) also caused this for PackSlip, ARForm, and APCheck styles.

Is Epicor replacing SSRS in Kinetic?

An EpiUsers post dated 8 September 2026, relaying an Epicor update, said Bold Reports was in development with first availability planned for Kinetic 2027.100, under a safe-harbor statement. Treat that as a reported plan, not a guarantee or confirmation of the final migration process. Check current Epicor release notes and guidance before planning a migration.

References

Most implementation details in this guide are informed by community troubleshooting discussions and verified knowledge base articles:

Systems I work on