Unplanned
Last Updated: 30 Oct 2026 10:25 by ADMIN
Michal
Created on: 17 Oct 2026 07:39
Category: Reporting
Type: Bug Report
1
[WRD] The request for the schema of the SQL procedure sends NULL for parameter values instead of the design-time values

Hello,

 it seems there is some glitch in blazor telerik web report designer. So its not possible, to use stored procedure with parameters as datasource

lets have input parmeter in SP, expecting "some value", how to configure it for report? Only person, which is designin report, puts the value in as constant.
@Typ=1 

1) - web report designer doesnt remember sql connection type(Choose data connection): Shared vs EMBEDED. Always fall to shared, when reopening report(but was configured as embeded).

2) - web repor designer, not applying DEFAULT "Configure design time parameters" VALUES, and also "Configure data source parameters". They are correctly stored in TRDP, they are visible in sql wizzard steps, but ALWAYS passed as NULL to the datasource when OPENING report. 
= so report is than messed up/or datasource invalid. 

**NOT BUG, ENHANCEMET: 3) - allow filtering in SQL datasource wizard "Stored procedure". Normally there is hundred of SP and its pain to pick one. OR allow to write SP directly

4) - when using SQL datasource, its not getting filed values correctly, this command is executed:
exec sp_executesql N' SET FMTONLY OFF; SET FMTONLY ON;exec [dbo].[IMS_PRINT_GETSET] @Typ,@ID;',N'@Typ nvarchar(1),@ID int',@Typ=N'1',@ID=30
in sql wizzard, there is command: "exec [dbo].[IMS_PRINT_GETSET] @Typ,@ID;"
how to solve that?
You are not ALWAYS allowed to modify SP. just consume as DATASOURCE, so its NOT VALID.
IF 1=0 BEGIN
        SET FMTONLY OFF
    END

iam unable to use version 1007-its not compatibile in project with telerik.blazor 15.1 (conflict in some skia or document proccesing nugets), but its not the case.

example:
Video demonstrating(reopened existing report), all described points + profiler result.

telerik sends - WRONG:
exec sp_executesql N' SET FMTONLY OFF; SET FMTONLY ON;exec [dbo].[IMS_PRINT_GETSET] @Typ,@ID;',N'@Typ nvarchar(4000),@ID int',@Typ=NULL,@ID=NULL
telerik SHOULD send:
exec sp_executesql N' SET FMTONLY OFF; SET FMTONLY ON;exec [dbo].[IMS_PRINT_GETSET] @Typ,@ID;',N'@Typ nvarchar(4000),@ID int',@Typ=N'1',@ID=30

TSQL demo procedure(one procedure for multiple sources - real world usage):
create PROCEDURE [dbo].[IMS_PRINT_GETSET]
@Typ INT,@ID INT
AS
BEGIN
  SET NOCOUNT ON;

  --!!TELERIK BUGFIX, but you are NOT ALWAYS permited to modify SP!!:
   IF 1=0 BEGIN
        SET FMTONLY OFF
    END  

IF @Typ=2 BEGIN
SELECT TOP 500 * FROM vTabOrders_active
RETURN
END

IF @Typ=1 BEGIN
SELECT TOP 500 ID,CisloZakazky,Nazev,Poradi FROM TabXYZ
RETURN
END

END

 

Thanks, even for some hotfix ideas.

    
4 comments
ADMIN
Dimitar
Posted on: 30 Oct 2026 10:25

Hello Michal,

Thank you for the attached videos and the additional information!

I had slightly misunderstood the problem originally by not realizing that the NULL parameter values are being sent when the Web Report Designer tries to load the schema of the SqlDataSource component upon loading the report.

I have now reproduced the problem, and as a result, I have approved this as a valid bug and have updated this item's title to reflect more precisely the type of issue it covers.

It is similar to the The Schema is not returned correctly when the SP returns different query depending on a parameter item, but that problem seems to occur while trying to execute the query to get the actual data, and it happens in the Standalone Report Designer, not the Web Report Designer, so they are not duplicates.

Once again, thank you for taking the time to report and thoroughly explain the issue!

Regards,
Dimitar
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Michal
Posted on: 23 Oct 2026 13:59

If it will help, example report is attached. - just change the sql connection and apply procedure.

Its partly the same as " The Schema is not returned correctly when the SP returns different query depending on a parameter" - but id doesnt share much detais.

The REAL troubles are parameter VALUES - as iam mentioned hotfix:

"IF 1=0 BEGIN
        SET FMTONLY OFF
    END  "

 

WORTS scenario: imagine that @Typ=NULL will  be the DELETE OPERATION, so designer will erase your data. It cannot happend, its crucial. but user DOESNT filled NULL values. So its sending something else then it should.

IF @Typ IS NULL DELETE FROM ....

if its not clear, just ask. priority are "the sql parameter values from designer and also then from report"

Michal
Posted on: 23 Oct 2026 13:47

Hello Dimitar,
 here are the details for your questions - more info.

if it is called from "combobox as sp, or direct query" - result is the same. The reason to write own query was only becaouse its simplier, then picking throught combobox(without filtering).

1) the problem is, that report designer is not passing parameter values as expected. in exapmple it is: @Typ=1. It passing it as @Typ=NULL (wrong) - as its shown in video.
Your example is excact WRONG(you dont need values), its covering the real problem, how is "query really executed againts SQL" - observer it by SQL profiler - its the only place, where values are WRONG and can be observed.
! AFTER reopening report, NOT when editing FIRST time(iam doing it in video on reopened report - schema is empty-lost)
a) - create report, fill everthing save everything, CLOSE everything - report, browser.
b)- reopen report = query values are NULL


here is real procedure, no data in database are needed.
Create two SEPARATE datasources in report, and direct it to the the SINGLE procedure.

@Typ=1 will be datasource name id SQLdata1
@Typ=2 will be datasource SQLdata2

Take a look at the video - QUERY for "example/preview data are OK"0:16s
, but query for getting schema passing ALL VALUES AS NULL(wrong) - 0:27s

do the step a) - works ok, so far, so good
do the step b) - problem
= none of the smecha is filled, because query is called as  "exec [dbo].[IMS_PRINT_GETSET] @Typ=NULL,@ID=NULL" and should be "exec [dbo].[IMS_PRINT_GETSET] @Typ=1,@ID=NULL"
ALSO, be aware of "SET FMTONLY OFF" hotifx(it normally shoud not be needed) - when you remove it, you are not able get @Typ=1 SCHEMA at all = also big trouble. Even at step a) 
Try it yourself, remove this part:
"
IF 1=0 BEGIN
        SET FMTONLY OFF
END
"

create PROCEDURE [dbo].[IMS_PRINT_GETSET]
@Typ INT,@ID INT
AS
BEGIN
  SET NOCOUNT ON;

  --!!TELERIK BUGFIX, but you are NOT ALWAYS permited to modify SP!!:
   IF 1=0 BEGIN
        SET FMTONLY OFF
    END  

IF @Typ=2 BEGIN
Select * From  (values ('Dummy1',1,getdate())
             ,('Dummy2',2,getdate())
      ) A(xKey,xVal,xDat)

RETURN
END

IF @Typ=1 BEGIN
Select * From  (values (33.5,55,getdate(),null,convert(bit,1))
             ,(77,25,getdate(),null,convert(bit,0))
      ) A(ID,xInt,xDat,xNone,xBit)

RETURN
END

END

 

 

Thanks for info, how to deal with it.

Most of stored procedures has LONGER body, and require EXACT filed parameters values, not the null or some random.

Otherwise, stored procedure are absolute nogo. They are for computing and returning data(lot of queries inside)Schema cannot describe only firs random select(it is your "wrong" example), but the excact one, and with exact parameters - same way as "data preview" in query builder is doing the job.

ADMIN
Dimitar
Posted on: 23 Oct 2026 12:50

Hello Michal,

Thank you for the attached file and the additional information!

Let me start with the two simpler points - the data connection type and filtering the stored procedures dropdown. Both are absolutely valid, and I have created separate items for them, which I will link below:

Regarding the issue with the default design and runtime parameter values not being applied, I am afraid that I was able to reproduce the issue locally. I tested with the following stored procedure:

CREATE PROCEDURE GettingStartedSP
    @MaxId INT
AS
BEGIN
    SET NOCOUNT ON;

    SELECT
        [HumanResources].[vEmployee].[EmployeeID],
        [HumanResources].[vEmployee].[FirstName],
        [HumanResources].[vEmployee].[LastName],
        [HumanResources].[vEmployee].[JobTitle],
        [HumanResources].[vEmployee].[Phone]
    FROM [HumanResources].[vEmployee]
    WHERE [HumanResources].[vEmployee].[EmployeeID] <= @MaxId
    ORDER BY [HumanResources].[vEmployee].[EmployeeID] ASC;
END;
GO

The @MaxId parameter was passed successfully in both scenarios. Below, I have pasted a short GIF demonstrating the test:

One difference that I noticed is that you seem to be calling the stored procedure with the exec command instead of relying on our engine to successfully execute it. Is there a reason to invoke it like that? If you use it in the standard approach, by selecting the procedure from the stored procedures selector, does it work as expected?

Regarding the last point, if I understood it correctly, the problem is that the schema of the SQL response is not filled correctly? Or that NULL values are passed to the SQL parameters?

We already started the discussion on the latter above, and so far, I am unable to reproduce that. However, the former, the schema, is based on the metadata pulled from the SQL Server response. I see that the given stored procedure includes an IF statement, and the response differs based on that.

There is a known problem for such scenarios - The Schema is not returned correctly when the SP returns different query depending on a parameter. I have cast your vote for the item, so that you are subscribed to updates on its status.

To summarise, the two UI-related issues have been logged on your behalf, and your Telerik points have been updated as a result! The issue with the schema is known and already logged, while the other problem with the parameters did not reproduce.

For the issue with the parameters, could you try to reproduce it with the sample stored procedure that I pasted above? Please try that and let me know how it goes.

Until we can determine the validity of the issue with the parameters, I will set the status of the item to "Need More Info". Please try to reproduce the issue with the suggested stored procedure, and if it does not happen, let me know how to reproduce it with the AdventureWorks database shipped with the Teleirk Reporting installer.

Thank you for helping us improve the product!

Regards,
Dimitar
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.