SOP Number field length
This is able to be imported because the value is truncated by eConnect when the XML sent through to SQL.
You could write a document task using C# or VB.NET to check the length of the source file column and fail the document so it isn't imported.
I’m having the same issue in Cash Receipts but the table is storing the larger number in the database. So, what do you mean by truncating? Also, we are testing prior to our upgrade to GP2015 and SmartConnect 184.108.40.206 and it no longer integrates the longer number. Was that something that was changed in SmartConnect?
Since this is a different map completely (and with a different symptom), you really ought to have created a new thread. You could perhaps have linked the URL of this thread in if you believed it relevant.
No biggie but if another user looks at the title of _this_ thread it won’t make sense in light of your response.
So as far as that goes – nothing in SmartConnect has changed at all. It is the underlying procs Microsoft eConnect procs that are different.
“… and it no longer integrates the longer number”
For me and the readers, you might have mentioned the error. (it is 12004).
And this is correct because on GP 2015 there are now recurring cash receipts and so they are limited to 17 characters in the “work” tables so that they can have 001, 002 appended to them for recurring documents.
If you go into the GP UI for RM Cash Receipts – you’ll only be able to enter 17 characters as well even though the table itself still can hold 20 (or 21 I forget).
If you would like to submit an answer or comment, please sign in to the eOne portal.