Child UD Table User Code

We are in the process of moving from E9 to 10. In our engineering workbench, we are using UD05 as a child table to ECORev. We have user codes tied to some UD05.Fields in EpiCombos.

I am not able to figure out how to work around Errors in the form : “Error accessing the database: Invalid column name XXXX”

It’s been a long time since we set it up in E9. Maybe I’m missing some steps, but I’ve verified that the epiCombo properties look correct and I’ve also been able to get User Codes working in an epiCombo that points at a standard table’s ud field.

It seems like I have something misconfigured in the setup of the child UD table. Any ideas would be appreciated!
Thanks,
Joe

Here is the error detail:
Server Side Exception

Error accessing the database: Invalid column name ‘ECO_OpenPO’.

Exception caught in: Epicor.ServiceModel

Error Detail

Description: Error accessing the database: Invalid column name ‘ECO_OpenPO’.
Program: System.Data.dll
Method: OnError
Original Exception Type: SqlException
SQL Line Number: 7
SQL Error Number: 207
Framework Method: b__0
Framework Line Number: 488
Framework Column Number: 36
Framework Source: b__0 at offset 1280 in file:line:column c:_Releases\ICE\3.1.600.0\Source\Framework\Epicor.Ice\Services\TablesetBound.cs:488:36

Server Trace Stack: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TrySetMetaData(_SqlMetaDataSet metaData, Boolean moreInfo) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at Ice.TablesetBound`3.<>c__DisplayClass27_0.b__0() in c:_Releases\ICE\3.1.600.0\Source\Framework\Epicor.Ice\Services\TablesetBound.cs:line 488

Client Stack Trace

at Epicor.ServiceModel.Channels.ImplBase`1.ShouldRethrowNonRetryableException(Exception ex, DataSet[] dataSets)
at Ice.Proxy.Lib.BOReaderImpl.GetList(String serviceNamespace, String whereClause, String columnList)
at Ice.Lib.Framework.EpiCombo.getDataSet()

Inner Exception

Invalid column name ‘ECO_OpenPO’.

Did you check to see if the Column exists in E10? You may have to change where they’re pointing.

Or just scrap the UD fields and recreate them in E10 using the Extended UD Table Maintenance and name the UD fields something meaningful so you don’t run into this again.

Yes it does exist. As an example of one that’s failing, UD05.ShortChar05.

So the DropDown for E9 used to be defined with Double Quotes but because its SQL that now needs to be changed to Single Quotes. If you look for the DropDown that is bound ot that column. Look in the properties and you’ll see the Filter Paste a Screenshot of that setup I believe is just a Single / Double QUote issue

2 Likes

That was the problem, exactly! Thank you Jose!