GUID in parameter values editor

[Joe]

How can I enter a GUID in the parameter values editor? I've tried
{F1F613B9-1D64-40E9-B437-A837F0B1BC6D}
'F1F613B9-1D64-40E9-B437-A837F0B1BC6D'
"F1F613B9-1D64-40E9-B437-A837F0B1BC6D"
'{F1F613B9-1D64-40E9-B437-A837F0B1BC6D}'
"{F1F613B9-1D64-40E9-B437-A837F0B1BC6D}"

[Steve]

Hello Joe,

Check the How to use a Guid as value for report parameter or data source parameter KB article for more information.

Regards,
Steve
the Telerik team

[Joe]

How do you enter a GUID in the editor? That is the question.

[Steve]

Hi Joe,

It should be entered as is directly in the expression editor for the Value like this: F1F613B9-1D64-40E9-B437-A837F0B1BC6D. As noted in the Expressions as Values of Item Properties help article:

To specify that the value of a property is an expression, the value should be a string starting with equal (=) sign. If the equal sign is not present the value will be interpreted as a string literal.

All the best,
Steve
the Telerik team

[Paul]

Hi,

I'm having the same issue, I've tried implementing the KB article's ConcertToGuid example,  but if I try and put in a design time parameter of :

=ConvertToGuid("14986A65-951D-40D4-964A-99EE3EFF4CD9")

Then I get an "Object Reference not set to an instance of an object." error when I try and execute the query.

I've put in the Built-in/User Functions.

Cheers.

[Hadib Ahmabi]

I think you had it the other way around.
The parameter should be of type string. This expression =ConvertToGuid("14986A65-951D-40D4-964A-99EE3EFF4CD9")
will return guid and not string.
So, the report parameter value should be just 14986A65-951D-40D4-964A-99EE3EFF4CD9
and the sqlDataSource parameter value should be = ConvertToGuid(Parameters.Parameter1.Value) 

[Paul]

Thanks for your help, but I did have it the correct way round, which is actually the same as the way you suggested.

I was referring specifically to the "Design Time" parameter.  There is an issue here that User Functions are not called, which Telerik Support has acknowledged.

A work around, is instead of selecting a stored procedure from the list, you pretend it's a select statement using the following format:

exec storedProcedureName  @GuidParamater = '1ac63fc4-2b63-4d49-ad05-9ccab0087baf'

This will let you execute the query in the designer so you can then design the report.  Once you're finished designing the report, you can select the stored procedure in the drop down list instead.