Just been using the pre release edition of 200 2024R1 & found an issue with the system administration tool installing Addons. The error was as follows:
INFO: Install, before AddOns.AddOnAdd
ERROR: Failed to install Add-on : String or binary data would be truncated in table 'Sage200Configuration.dbo.tblReqConflicts', column 'ReqConflictVersions'. Truncated value: '12.0.3; 12.0.7; 12.0.13; 12.0.20; 12.0.27; 12.0.31; 12.0.35; 12.0.36; 12.0.41; 12.0.43; 12.0.46; 12.'.
The statement has been terminated., String or binary data would be truncated in table 'Sage200Configuration.dbo.tblReqConflicts', column 'ReqConflictVersions'. Truncated value: '12.0.3; 12.0.7; 12.0.13; 12.0.20; 12.0.27; 12.0.31; 12.0.35; 12.0.36; 12.0.41; 12.0.43; 12.0.46; 12.'.
The statement has been terminated.
INFO: Process, before BuildModelSource
INFO: Install, after BuildModelSource
INFO: Process, errors=1}
I know exactly what’s caused it, the required applications in the addon are very extensive in the addon & the value it’s trying to put into the database table would be truncated. This prevents the Addon from being installed at all. I know the solution is to remove the number of versions supported in the Addon but equally there ought to be a more elegant way this type of error is handled – i.e. truncate the data being moved into that field in the first place.
Idea Benefit | Every user |
How do you solve for this problem today? | There is no solution apart from manually altering the column size in SQL which is not really a solution |
Product Variant | Sage 200 Professional |
Sure will - but I've had engineering check it and its definitely classified as an issue :)
Hi Jo, I did actually raise this with developer services directly who to quote replied with the following:
I would recommend raising this feedback on our Ideas Hub. The ideas hub is consistently monitored by the development teams who will identify and prioritise items for future releases.
Kind Regards,
James Conway
Can I leave this with you?
Thanks for the feedback Ian, having reviewing this its an issue not a request for change. I will ask our developer services team to raise it and contact you.