embedded paginated report with parameters doesnt work

Hi,jostnachs . Thank you for your reply.
I noticed that your data source is not the usual sqlserver but an off-the-shelf semantic model (using dax statements to query the model data)
You didn't provide a screenshot of the paginated report running, so I can't rule out if there is a problem with the DAX statement you are writing to get the data. Could you please check if your DAX statement is fetching the target data properly (even if the date parameter is set to null)
If possible, could you share the final results of the paginated report in Power BI Report Builder (including the final screenshot with different combinations of your parameter choices) to check if the paginated report itself can display the data properly under each combination of parameters. (You will need to mask the screenshots of the paginated report to protect your private data.)
Since the data source you are using is power BI service semantic model, if the report is in import connection mode, you can use XMLA (you need to have PPU or premium license, and enable XMLA read/write privileges in Admin portal) to realize remote connection to the report in SSMS. Connect to the semantic model of the report in workspace (since the Power BI report model is actually an AS model, you can process and view it as an AS model)
URL:
Semantic model connectivity and management with the XMLA endpoint in Power BI - Power BI | Microsoft Learn
like this:

XMLA remote connection workspcae using SSMS (SQL Server Management Studio):

create a new DAX query

Just like using DAX view on Desktop, you can now check what data is actually stored in a semanticmodel published to a service by using the xmla implementation.
To narrow down the scope of the check
Examine the paginated report query semantic model statement in desktop (run the DAX code you showed in the paginated report)

Check the data in the semantic model published to the service in ssms
(Run the DAX code you showed in the paginated report) Check that the dax statements written in the paginated report are valid

In addition, please test, when your Date parameter setting is not set to None, Desktop in the paginated reports run whether the data can be displayed normally, please provide the corresponding screenshots, which will help you quickly find out where the problem lies.

2. If you can be sure that it is not the DAX code problem when you make your own report. Then you please check the desktop operation: check whether the parameters of the paginated report is set up correctly bound, whether the data type is matched.

3. Change the version of Power BI Desktop.
Try to use other version of Power BI Desktop to see if it can solve your problem. (Please save the important data beforehand to avoid loss)

Links to download historical versions of Desktop:
Previous monthly updates to Power BI Desktop and the Power BI service - Power BI | Microsoft Learn

4.Please check if you have triggered a limit during the design process and make sure that the parameters correspond to each other correctly.
URL:
Create and use the paginated report visual - Power BI | Microsoft Learn

 I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi,jostnachs .I am glad to help you.

Has your problem been solved?
If you have found suitable solutions, please share them as it will help more users with similar problems.
Or you can mark the valid suggestions provided by other users as solutions.
Thank you very much for your understanding and support of Power BI.

I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.