Skip to main content
Solved

REST HTTP PUT call to Update A DropDown Custom field, 500 internal server error


Forum|alt.badge.img
  • Jr Varsity III
  • 16 replies

Hello everyone!

 

I have a custom field on Shipments Screen telling me the status of the order in a different system, the code is given below:

declaring UsrRWSStatus
the shipments screen for a visual representation

Now I have a service which will update its status to Pick Created , with the following request:

POSTMAN PUT request

But I get this error in response,

"String or binary data would be truncated in table 'AcumaticaDB.dbo.SOShipment', column 'UsrRWSStatus'. Truncated value: 'P'.\r\nThe statement has been terminated.",

 

this as the exception message,

 

I am confused here, am I sending the request correctly, or do I have to change something else in my customization of the DAC?

 

If any more context is required please let me know.

 

Cheers,

Jdeol

Best answer by Vignesh Ponnusamy

@jdeol, Considering the below error stack, looks like the field length is smaller than in the database.

"String or binary data would be truncated in table 'AcumaticaDB.dbo.SOShipment', column 'UsrRWSStatus'. Truncated value: 'P'.\r\nThe statement has been terminated.",

 

Did you check if the field length in database is rightly? Are you able to save/update the field value from the UI?

View original
Did this topic help you find an answer to your question?

2 replies

Vignesh Ponnusamy
Acumatica Moderator
Forum|alt.badge.img+5

@jdeol, Considering the below error stack, looks like the field length is smaller than in the database.

"String or binary data would be truncated in table 'AcumaticaDB.dbo.SOShipment', column 'UsrRWSStatus'. Truncated value: 'P'.\r\nThe statement has been terminated.",

 

Did you check if the field length in database is rightly? Are you able to save/update the field value from the UI?


Forum|alt.badge.img
  • Author
  • Jr Varsity III
  • 16 replies
  • March 24, 2023

Thanks @vigneshponnusamy89 , for pointing me to the correct place.

The problem was in my local DB which was only allowing string of length 1, i changed it and it is working as fine.

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings