Answered

Action 'Execute_stored_procedure_(V2)' failed due to the SQL conversion from a character string to uniqueidentifier

(0) Share

Report

Posted on by Zhangzhonghao

126

I have a stored procedure, which accepts a parameter. The parameter's type is an uniqueidentifier. I've pass the correct format, why did it always failed with the error conversion failure? Anyone can help!!!

{

"status": 400,

"message": "Microsoft SQL: Conversion failed when converting from a character string to uniqueidentifier.\r\n inner exception: Microsoft SQL: Conversion failed when converting from a character string to uniqueidentifier.\r\nclientRequestId: a866fd12-c4cf-4f04-b203-e86de3ee59c8",

"error": {

"source": "sql-ea.azconn-ea.p.azurewebsites.net"

}

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Pstork1 69,383 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Unique Identifiers are GUIDs, not strings, and there is no automatic conversion. Try using GUID() to cast the string to a GUID and use that for your parameter.

Was this reply helpful? Yes No
Zhangzhonghao 126 on at

Like (0)

Report
Copy link

Link copied!

Hi @Pstork1 , thanks for your replying! I just tried to use guid() function to convert, but it still failed. Any idea for this?

Was this reply helpful? Yes No
Verified answer

Pstork1 69,383 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!
First, my apologies. I should read documentation more closely. You can't use Guid() to cast a string to a guid. It always produces a new guid. But I did go back and try your scenario. SQL should accept a straight string in the right format as a guid. Can you share how the parameter is defined in the stored procedure and what you are using it for? I built a simple table with a uniqueIdentifier as a Key and then executed the following stored procedure feeding the Guid in as a string. It works.

ALTER PROCEDURE [dbo].[selectbyGuid] @GuidId UNIQUEIDENTIFIER AS BEGIN -- SET NOCOUNT ON added to prevent extra result sets from -- interfering with SELECT statements. SET NOCOUNT ON -- Insert statements for procedure here SELECT FieldA,FieldB from dbo.SQL Where Id = @GuidId END

I also ran it with the GUID you are using and it worked correctly. No data was returned but it did accept the GUID as a valid parameter.

Was this reply helpful? Yes No
Zhangzhonghao 126 on at

Like (0)

Report
Copy link

Link copied!

@Pstork1 thanks for your solution! It turned out that we have incorrect type define of UNIQUEIDENTIFIER (We defined it varchar)...

Was this reply helpful? Yes No