/
Creditor Transaction Archiving fix to "String or binary data would be truncated".
Creditor Transaction Archiving fix to "String or binary data would be truncated".
- Beth Blok (Unlicensed)
- Julie Hanlon
Owned by Beth Blok (Unlicensed)
Problem
Running the Creditor Archiving function errors after a few minutes with 'String or binary data would be truncated
Solution
SQL skills are required
A sound knowledge of SQL Studio Management is required to complete this task
The problem is caused by the archiving stored procedure for creditor transactions using temp tables that expect CurrencyID of CHAR(20) instead of CurrencyID of CHAR(36). Patched stored procedures for 7.0.175.0 and 7.2.1 are attached. Download the relevant SQL script and apply to the database.
7.2.1
7.0.175
Related articles
, multiple selections available,
Related content
Solutions in addition to the Service Releases
Solutions in addition to the Service Releases
More like this
Archiving sales orders errors
Archiving sales orders errors
More like this
Troubleshooting articles
Troubleshooting articles
Read with this
Loading Creditor Transaction batches may error with "Conversion from string %s to type decimal is not valid"
Loading Creditor Transaction batches may error with "Conversion from string %s to type decimal is not valid"
More like this
How-to articles
How-to articles
Read with this
GLMGT200 - Profit & Loss errors Database Vendor Code: 468 Error
GLMGT200 - Profit & Loss errors Database Vendor Code: 468 Error
More like this