x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 5 replies
  • Subscribers 75 subscribers
  • Views 792 views
  • Users 0 members are here
Browse Forums
Announcements
105
topics
32
replies
General Discussion
6k
topics
18k
replies
derekhdn

The Sage CRM Component Manager fails to create a new component

Posted By

Hi everyone and compliments for the year ahead.

I am having a problem in Sage CRM 2018R3. When I try and create a new component in the component in order to record some changes I am going to make on the company screen, the new component fails to create. There is a message: SQL code: 8152.

I have checked the SQL logs and get the following:

String or binary data would be truncated:

Components(
Cmp_Name,
Cmp_Description,
Cmp_Writing,
Cmp_Version,
cmp_CreatedBy,
cmp_CreatedDate,
cmp_UpdatedBy,
cmp_UpdatedDate,
cmp_TimeStamp)
VALUES
(N'CasesWorkflow',
N'this is for the latest workflow to be moved from dev to live',
N'Y',
N'2018 R3',
1,
'20181205 10:49:48',
1,
'20181205 10:49:48',
'20181205 10:49:48')


I am not sure where the problem lies in order to fix

Thank you in advance for any ideas to resolve

Parents
  • 0

    Hello

    This is a known issue.

    In 2018 R3 it is not possible to create a new component to record changes made to CRM . There is a SQL Error due to the cmp_version column that is only 5 char and "2018 R3" that CRM is trying to insert.

    This is going to be fixed in Sage CRM 2019 R1. (Ref: 0-171173-QA)

  • 0 in reply to Sage CRM

    Excellent. I just hit this very issue and got around it by changing the SQL value to "18 R3" which allowed the component to be created and it runs. I needed a new component, because doing everything in the Changed component means you can't easily put that component on a new installation if you need to reinstall because CRM doesn't like you adding a component called Changed. You have to edit the ecf file and the other one to alter references to Changed to something else.

    My problem is that I have an installation of Sage 2018 R3 because that is the latest version I can put on when the customer is integrated with Sage 300 2017. Don't get me started on why we aren't upgrading them or why we are selling them a CRM version that is out of support. I've had this argument internally with the boss for years and it's got me nowhere.

    I assume the fix is just making the field bigger? I can't imagine anything else relying on cmp_version for anything. I'd imagine it's there just for informational purposes, so could I potentially just increase the field size and alter the field metadata?

  • 0 in reply to Vega

    I think you have it. 

  • 0 in reply to Vega

    We just modify the table in CRM to make the field bigger and this seems to get around the issue.

Reply Children
No Data

*Community Hub is the new name for Sage City