RDD Linked Tables showing duplicate Description Fields

[TerryR (Terry Raymond)]

In our 2025.10 test environment, a few of our SSRS reports have stopped working, eg our custom AR Invoice Form. Standard SSRS ARForm report works fine.

Cause on our customized ARForm looks to be some UD fields not making it over correctly.

The reports work fine in 2021.2. In our customized ARForm RDD, a couple UD fields are selected for the OrderNum Linked Tables / Description Fields.

But those fields are failing in 2025.2, giving Invalid Column Name error in System Monitor. The only thing I see different is that on ALL the RDDs, on ALL linked tables, ALL the UD columns are duplicated / show up twice in the Description Fields list!

ARForm (default/system RDD):

POForm (default/system RDD):

Are yall seeing this too?

Though here is a custom PO form in the classic UI in 2025.2. The duplicates don’t show up. So maybe it is just a Kinetic UI bug and my issue is something else…

Specific errors I’m getting…

1. Conversion EnsureReportHasRequiredComponentsToRun showed errors on the failing reports, eg “The column FSCallDt.Company used by the ‘FsCallDtFsCallMt’ relationship is missing.” I found that for some reason there were a couple fields that got excluded during the upgrade… so I un-excluded them and got past that error.

2. When running the custom SSRS report, error in System Monitor now is:
   An error has occurred during report processing. —> Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. —> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset ‘Company’. —> Microsoft.Data.SqlClient.SqlException: Invalid column name ‘OrderNum_RMFOrder_c’.
   2021.2 and 2025.2, 2025.2 classic RDDs (no duplicate shown).
   

   
   
   
   
   
   
   

Any ideas what I need to do to get our custom form working again? Thanks much.

[TerryR (Terry Raymond)]

Well it looks like that UI glitch was a red herring.

I ended up getting the ARForm report to run (after way too many hours) by:

1. Making a new copy of the RDD, adding the couple UD fields back in.
2. Copying the latest system RDL dataset query into my custom RDL, and adding in the UD fields I needed. And the strangest thing is that I had to comment out 4 built-in fields in the RDL dataset query to get past these errors:

• Invalid column name ‘Calc_TrackByAttribute’.
• Invalid column name ‘Calc_MtExtPrice’. (two references)
• Invalid column name ‘RptLiteralsLServiceSource’.

Those fields work fine with the system RDD and system RDL dataset, but not in a custom RDD. Google says “When you run a Standard System Report, Epicor uses an internal, compiled C# assembly (a DLL) to generate the data. That assembly knows exactly how to calculate Calc_TrackByAttribute on the fly and injects it into the temporary SQL table schema, even if you don’t see it listed in a “Calculated Fields” UI.” Which is the case, those calculated fields above are not listed in the system ARForm RDD calculated fields.

It would be nice if someone else could take a look, see if you’re seeing the same thing…