Execute store procedure to update data

Sounds like you're trying to insert some text with advanced features (unicode / emojis / etc) into a text column that can't handle it.

Hi Mike,

I am not writing any emojis or Unicode just text values writing it from one table to other table using sp.

and I am passing parameters to sp through pv in process model

(if i execute sp manually in data base and pass the parameter it is working fine & facing issue while using execute sp smart service).

Sharing some code might help us to support you.

The value you shared ('\xAC\xED\x00\x05ur', etc) suggests it's trying to process some disallowed special characters - I can't say much more without specifics.

CREATE PROCEDURE

UpdateDetailsFromSourceToDestination( IN id text)

BEGIN 

UPDATE destination_table AS dst INNER JOIN source_table AS src ON dst.id = src.id

SET

dst.name = src.name,

dst.age = src.age,

dst.other_details = src.other_details  WHERE src.id = id;

END$$ 

That CREATE PROCEDURE script does not match the parameters shown in the DB GUI or Execute Procedure node, but I'm guessing you typed that manually and the procedure does have 2 inputs for "ids" and "code"?  The procedure script above also uses "id" instead of the "ids" input you appear to be passing.  I would first ask to confirm the inputs and script match what you are sending.

Is this happening always or only on some values for id/ids?

id/ids is a text value in the DB?

Confirm the destination table fields you are updating are the same type and length of the source table?

Confirm the value of the constant you are using for the data source is correct?  (However since your error notes column I am assuming this part is ok)

Share the exact call you use when you run the procedure directly on the DB?  (as you note this does work correctly)

To note, I always recommend avoiding the Execute Stored Procedure service unless absolutely necessary - all we are doing here is updating some table values which can easily be done by pulling them into a CDT, updating values in Appian, and persisting back with the Write to Datastore service - which is simpler to build, maintain and debug.

That CREATE PROCEDURE script does not match the parameters shown in the DB GUI or Execute Procedure node, but I'm guessing you typed that manually and the procedure does have 2 inputs for "ids" and "code"?  The procedure script above also uses "id" instead of the "ids" input you appear to be passing.  I would first ask to confirm the inputs and script match what you are sending.

Is this happening always or only on some values for id/ids?

id/ids is a text value in the DB?

Confirm the destination table fields you are updating are the same type and length of the source table?

Confirm the value of the constant you are using for the data source is correct?  (However since your error notes column I am assuming this part is ok)

Share the exact call you use when you run the procedure directly on the DB?  (as you note this does work correctly)

To note, I always recommend avoiding the Execute Stored Procedure service unless absolutely necessary - all we are doing here is updating some table values which can easily be done by pulling them into a CDT, updating values in Appian, and persisting back with the Write to Datastore service - which is simpler to build, maintain and debug.