When writing SSRS reports in Dynamics 365 for Operations, there are 3 different ways of passing parameters to SSRS.
If the Dynamics filters property is set to true on the report data set, the report includes a “Records to include” tab where the user can create their own query.
The default filters are taken from the ranges/group by/order by values on the query used for the data set in the report.
The user can also add their own ranges/group by/order by filters here.
The date effective filter is automatically added if
a) the table is a date effective table
b) one of the fields in the dataset list has a table relation which is a date effective table
When the query is dropped on to the dataset of the report, the parameters automatically appear in the dataset parameters and the report parameters.
If these filters appear on your report and you’re not sure why, you can look at the XML of the report and find the parameter. This will tell you the related table and field which is triggering the date effective filters.
The parameters are based upon the ranges set in the query which is used to populate the data set. Any ranges on the query will automatically be added to the data set parameters and the report parameters. From the report parameters, you can set the parameter visibly, whether it can allow nulls and blanks and whether or not it can contain a multi-value parameter.
If you are using a Report Data Provider(RDP) as a data source, the parameters you define in Data Contract class will bind to the data set. This will de done automatically when you specify the RDP data source on the data set of the report.