EDA Sync Error

Epicor ERP 10
,
1

Hi Guys,

I am battling with a sync error on my EDA sync with E10 (10.2.300). One item is failing with the below error message:

INFO 2019-11-28 11:50:15 Syncing ‘i_#Epicor_apinvdtl_measures’.
INFO 2019-11-28 11:50:15 Starting sync session for item ‘i_#Epicor_apinvdtl_measures’.
ERROR 2019-11-28 11:50:20 Client side error.
Sync failed for item ‘i_#Epicor_apinvdtl_measures’.
Exception: String or binary data would be truncated.
String or binary data would be truncated.
String or binary data would be truncated.
The statement has been terminated.
The statement has been terminated.
The statement has been terminated.
Stack Trace:
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.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)
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, TaskCompletionSource`1 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 Phocas.Sync.Client.PartGenerators.ODBCQueryDataItemPartGenerator.CreateReader(IParametersProvider parametersProvider)
at Phocas.Sync.Client.ItemSyncer.CreatePartGenerator()
at Phocas.Sync.Client.ItemSyncer.d__63.MoveNext()

I understand that some data is too big but how do I determine which field it is referring to?

2

So I’m looking for our issue in my email and haven’t found it yet. I’ll keep looking…

BUT, I am sure we have the same issue in that script and it was because the company or partnum or description variables were set too small (only in this SQL script). I want to say it was part# and we made it NVARCHAR(50) in two or three places where it was set for NVARCHAR(30). I think if you compare a few of the scripts and the Part# field in E10, that Part# is actually (50).

3

@epicGeoff
Found it. In the apinvdt_measures, Invoicenum length field had to be upped from 20 to 50 in two places, and then the CompanyVendorInvoiceNum had to go from 50 to 70 in one place.

4

Thanks Mike.

I have not yet been able to circle back to this but I will let you know once I have.

Thank you for your help.

image001.jpg