topic Report Builder Error - Forward Dependencies Are Not Valid in Report Server

Report Builder Error - Forward Dependencies Are Not Valid

jus-astra — Mon, 15 Aug 2022 21:55:00 GMT

Hi everyone!

I'm working on building a paginated report using Report Builder.

I created a data source and dataset on Report Server. The dataset has a parameter specified in the query, so the parameter was generated in Report Builder when I connected the report to it. I'm trying to add values in the Available Values tab of this parameter, but when I try to run the report, I'm getting an error message that says "The report parameter xyz has a DefaultValue or a ValidValue that depends on the report parameter xyz. Forward dependencies are not valid."

This parameter is being used in a where clause on the dataset (something like below), so I don't believe there are any dependencies here.

SELECT *

FROM table1 t1 JOIN table2 t2 ON t1.key = t2.key

WHERE Department = @Department AND XYZ = xyz

Please advise.

Thanks!

Re: Report Builder Error - Forward Dependencies Are Not Valid

v-henryk-mstf — Thu, 18 Aug 2022 07:50:32 GMT

Hi jus-astra ,

What is your data source, for report server not all data sources support parameters.

If support, there should be an error in the parameter creation process. You can refer to the following document to check if the relevant steps were followed.

For more details, you can read below document.

Report parameters in Power BI Report Builder - Power BI | Microsoft Docs

Create parameters for paginated reports in the Power BI service - Power BI | Microsoft Docs

If the problem is still not resolved, please provide detailed error information and related operations screenshoots. Looking forward to your reply.

Best Regards,
Henry

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Re: Report Builder Error - Forward Dependencies Are Not Valid

duncfair — Thu, 09 May 2024 17:52:29 GMT

Thanks for the prompt response.

The parameter was created automatically by Report Builder because I selected a stored procedure with an input parameter as my datasource. SQL Server is 100% a-ok as a datasource. No errors anywhere until I click run.

I read through both of the articles you linked and there is no reference to the error nor any indication of anything I may have done incorrectly.