Moving AR Form from Epicor 10 to Kinetic

Kinetic ERP
, , ,
1

Hi all :slight_smile:

Just putting it out there as a generic question to see if anyone else has had issues with the AR Form specifically moving across different versions.

In our experience, we are trying to move the AR Form we have set up in Epicor 10 over to the new Kinetic environment and running into a whole host of issues. We’ve even tried moving the Standard SSRS AR Form and dataset from Epicor 10 to Kinetic and even that fails with the below errors. We are more thinking this could be a version issue but wondered if anyone else has run into this issue at all? To note, other SSRS reports from Epicor 10 have worked without issue i.e. Order Ack / POForm etc

Thanks all!!

Program Ice.Services.Lib.RunTask when executing task 371 raised an unexpected exception with the following message: RunTask:
Ice.Core.SsrsReporting.SsrsCaller.SsrsException: The SSRS server returned the status code 500 (InternalServerError) with the following error text:
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 ‘ARForm’. —> System.Data.SqlClient.SqlException: Invalid column name ‘Calc_MtExtPrice’.
Invalid column name ‘ProbReasonCode’.
at Ice.Core.SsrsReporting.SsrsCaller.SoapCaller.Call[TContent,TResponse,TSoapHeader](String actionName, TContent content, TSoapHeader soapHeader) in C:_releases\ICE\ICE4.3.100.11\Source\Server\Internal\Lib\TaskLib\SsrsReporting\SsrsCaller\SoapCaller.cs:line 47
at Ice.Core.SsrsReporting.SsrsCaller.ReportExecutionService.Render(String format, String deviceInfo, String& extension, String& mimeType, String& encoding, Warning& warnings, String& streamIds) in C:_releases\ICE\ICE4.3.100.11\Source\Server\Internal\Lib\TaskLib\SsrsReporting\SsrsCaller\ReportExecutionService.cs:line 75
at Ice.Core.SsrsReporting.SsrsRendererBase.Render(SsrsRenderInformationBase renderInformation) in C:_releases\ICE\ICE4.3.100.11\Source\Server\Internal\Lib\TaskLib\SsrsReporting\SsrsRendererBase.cs:line 143
at Ice.Core.SsrsReporting.SsrsSingleDocumentRenderer.<>c__DisplayClass1_0.b__0() in C:_releases\ICE\ICE4.3.100.11\Source\Server\Internal\Lib\TaskLib\SsrsReporting\SsrsSingleDocumentRenderer.cs:line 49
at Ice.Core.SsrsReporting.SsrsRendererBase.TraceReportRendered(String printProgram, String ssrsRenderFormat, Func`1 timedAction) in C:_releases\ICE\ICE4.3.100.11\Source\Server\Internal\Lib\TaskLib\SsrsReporting\SsrsRendererBase.cs:line 81

1 Like
2

You will need to remove these columns from dataset query and also from subquery dataset query if it exists.

3 Likes
3

Ah yes, that one was a pain in the ass…

As Rythem mentions, you have to remove them from the RDDs, the RDL fields, RDL queries, and any other references on the RDL to them.

You can open RDL in notepad and CTRL+F to get any idea of where the references are.

5 Likes
4

Will this become a problem with SSRS in general, or just on AR / a select few tables?

5

That’s great thank you so much!!! Wow it really wasn’t just us then! is it just these two fields that played up for you too?

Invalid column name ‘Calc_MtExtPrice’.
Invalid column name ‘ProbReasonCode’.

1 Like
6

ARFORM has always neede adjustments from 10.2.100 on…

6 Likes
7

I believe they also said it changed from ARForm to ARInvoice somewhere else.

8

I thought there were a couple more of the calc fields.

1 Like
9

I found the Field Service fields were giving the error. I was able to see them in the system monitor and remove from the report.
Editing SSRS in notepad++ is sometimes easier b/c ssrs is amazing at hiding fields used in text boxes :cry:

3 Likes
10

Yes, iirc there were some as ell going from 10 to Kinetic. Our AR Invoice isn’t too over the top so I ended up just rebuilding it off Kinetic 2022.1 stock SSRS version.

I always edit the SSRS queries in NP++ as I hate the box SSRS report designer gives us to work with.

1 Like
11

XML Notepad is also good for editing rdls.

2 Likes
12

Right, I’ve had to do that only a few times but it’s good for that too!