AR Invoice Form Printing Error

Kinetic ERP
, ,
1

After the update that Epicor released last week, we are unable to print our custom AR Invoice forms. We get an error message as stated below. I have tried including the column CallCode, but then the next print it says to include a different column and it continues to give that error message with a different column name each time. Is there something different that should be done to get this fixed?

Program Ice.Services.Lib.RunTask when executing task 2131666 raised an unexpected exception with the following message: RunTask:

System.InvalidOperationException: The lookup link ‘CallCode’ is missing the InvcDtl.CallCode column. If the column is excluded then include it. Otherwise, consider dropping the lookup link.

—> System.IndexOutOfRangeException: CallCode

at System.Data.ProviderBase.BasicFieldNameLookup.GetOrdinal(String fieldName)

at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name)

at Ice.Core.RptBase.DataRecordWrapper.get_Item(String columnName)

at Ice.Core.RptBase.ForeignLinkTableSqlBuilder.GetRightSideLinkCriteriaValueFromDataRecordWrapper(String sourceField)

— End of inner exception stack trace —

at Ice.Core.RptBase.ForeignLinkTableSqlBuilder.GetRightSideLinkCriteriaValueFromDataRecordWrapper(String sourceField)

at Ice.Core.RptBase.ForeignLinkTableSqlBuilder.BuildWhereClause()

at Ice.Core.RptBase.SqlBuilderBase.BuildSqlCommand()

at Ice.Core.RptBase.DataWriterBase.FillForeignLinkTableValues(ZDataDataSource dataSource, IRow toRow, IRow sourceRow)

at Ice.Core.RptBase.OutputRelationDataWriter.WriteRowsForKeyValues(IDataReader reader, IList`1 keyParameters, IDataSource relatedTable, Object[] keyValues)

at Ice.Core.RptBase.OutputRelationDataWriter.WriteRowsForKeyValues(IDbCommand sqlCommand, IList`1 keyParameters, IDataSource relatedTable, Object[] keyValues)

at Ice.Core.RptBase.OutputRelationDataWriter.WriteRows(IDbCommand sqlCommand, IList`1 keyParameters, IDataSource relatedTable, UniqueKeyCollection relationKeys)

at Ice.Core.RptBase.OutputRelationDataWriter.WriteTable(DataSourceRelationship relationship, IDataSource relatedTable, DataColumnCollection keyColumns, UniqueKeyCollection keyValues)

at Ice.Core.RptBase.OutputRelationDataWriter.WriteTables()

at Ice.Core.RptBase.ReportDataBuilderBase.XMLClose()

at Ice.Core.RptBase.ReportDatabaseBuilder.XMLClose()

at Ice.Core.RptTaskBase`1.XMLClose()

at Erp.Internal.AR.ARInvForm.RunProcess(Int64 instanceTaskNum, String outputFileName) in C:_releases\ERP\ERP11.2.200.0\Source\Server\Internal\AR\ARInvForm\ARInvForm.cs:line 1441

at Ice.Hosting.TaskCaller.InnerExecuteTask(IceDataContext newContext) in C:_releases\ICE\ICE4.2.200.0\Source\Server\Framework\Epicor.Ice\Hosting\TaskCaller\TaskCaller.cs:line 68

at Ice.Hosting.TaskCaller.ExecuteTask() in C:_releases\ICE\ICE4.2.200.0\Source\Server\Framework\Epicor.Ice\Hosting\TaskCaller\TaskCaller.cs:line 64

at Ice.Lib.RunTask.BpmFriendlyTaskLauncher.Run(String sessionIdPrefix, IceContext db, Action taskRunner) in C:_releases\ICE\ICE4.2.200.0\Source\Server\Services\Lib\RunTask\BpmFriendlyTaskLauncher.cs:line 63

at Ice.Services.Lib.RunTaskSvc.InnerRunTask(Int64 ipTaskNum, Boolean suppressTransaction) in C:_releases\ICE\ICE4.2.200.0\Source\Server\Services\Lib\RunTask\RunTask.cs:line 450

2

Go to your RDL for your custom ARFORM, then go to the Table Exclusions for InvcDtl and make sure that CallCode is not excluded. We had this for several fields in InvcDtl moving from 10.1.600 → 11.1.200.

1 Like
3

CallCode is currently checked on ExcludeColumn and ExcludeLabel. If I uncheck them, the next time I try to print it says another column needs to do the same thing and continues to say a different column each time I print but still will not print

4

You will probably have to do that for each field until you identify them all.

2 Likes
5

Is this common to have to do after an update?

1 Like
6

It depends on too many factors to predict. The one thing you can control is not customizing too much. And by that I mean, add all that you want but do not take away from the out of the box.

7

I think it depends how far behind one is. Previous versions did not enforce having fields in an index be included. You can check the fields in the links section and make sure they are not excluded.

ARFORM has been problematic during upgrades for various reasons since 10.2 in my experience.

8

Is a rewrite of the form going to be required at all to be upgraded to the latest Epicor version?

9

Not necessarily. I did it once but every other time I just fixed the issues. Remember to export the RDD or put it in a Solution so you can import it into your production when you upgrade to live.

I did fix the RDD column exclusions in my live version on this go around so I didn’t have to do it when going live.

2 Likes