{"id":84917,"date":"2019-08-02T21:32:15","date_gmt":"2019-08-02T21:32:15","guid":{"rendered":"https:\/\/www.red-gate.com\/simple-talk\/?p=84917"},"modified":"2022-04-24T21:02:04","modified_gmt":"2022-04-24T21:02:04","slug":"reporting-services-basics-parameters","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/databases\/sql-server\/bi-sql-server\/reporting-services-basics-parameters\/","title":{"rendered":"Reporting Services Basics: Parameters"},"content":{"rendered":"

The series so far:<\/h4>\n
    \n
  1. Reporting Services Basics: Overview and Installation<\/a><\/li>\n
  2. Reporting Services Basics: Creating Your First Report<\/a><\/li>\n
  3. Reporting Services Basics: Data Sources and Datasets<\/a><\/li>\n
  4. Reporting Services Basics: Parameters<\/a><\/li>\n
  5. Reporting Services Basics: Adding Groups to Reports<\/a><\/li>\n<\/ol>\n\n

    Adding parameters is one of the essential skills to learn when you are new to SSRS. Parameters give end-users the ability to change the filter of the report on-the-fly. Imagine creating a separate report for every sales year or every department. Even worse, imagine creating a report for every combination of years and departments! With parameters, you can create one report that will work for any combination of these variables.<\/p>\n

    Starting with the Product List Report<\/h2>\n

    To demonstrate parameters, this article will use the list of products found in the AdventureWorks database. To get started, create a new Report Server Project<\/em> called Parameters<\/em> with a shared data source. (See previous articles in this series if you need help understanding how to work with projects, data sources, or datasets.) Add a report named Product List with this embedded dataset:<\/p>\n

    SELECT P.ProductID, P.Name AS ProductName, P.Color, P.Size, \r\n   P.ListPrice, PC.Name AS Category, PS.Name AS SubCategory\r\nFROM Production.Product AS P \r\nJOIN Production.ProductSubcategory AS PS \r\n  ON PS.ProductSubcategoryID = P.ProductSubcategoryID\r\nJOIN Production.ProductCategory AS PC\r\n  ON PC.ProductCategoryID = PS.ProductCategoryID;<\/pre>\n
    Your Solution Explorer<\/em> should look like Figure 1.<\/p>\n
    <\/p>\n
    Figure 1: The Solution Explorer<\/p>\n
    Your Report<\/em> Data<\/em> window should look like Figure 2.<\/p>\n
    <\/p>\n
    Figure 2: The Report Data window<\/p>\n
    Add a Table<\/em> control to the report\u2019s canvas and add these fields to the Data<\/em> row.<\/p>\n
      \n
    • ProductID<\/li>\n
    • ProductName<\/li>\n
    • Color<\/li>\n
    • Size<\/li>\n
    • ListPrice<\/li>\n<\/ul>\n
      The table on the report will look like Figure 3.<\/p>\n
      <\/p>\n
      Figure 3: The table<\/p>\n
      Preview the report to make sure it works at this point. It should look something like Figure 4.<\/p>\n
      <\/p>\n
      Figure 4: The report in Preview mode<\/p>\n
      Spend some time formatting the report. This is not required for learning about parameters, but if you are like me, the unformatted report is quite annoying! Your report might look something like Figure 5 when you are done.<\/p>\n
      <\/p>\n
      Figure 5: The formatted report<\/p>\n
      The wizard report from the first article had a header, but you didn\u2019t learn how to add a header to a new report. To do so, make sure that the report is in Design<\/em> view. Select the report canvas, which makes the Report<\/em> menu show up in the menu bar. Select Report Add Page Header,<\/em> as shown in Figure 6. Also, add a page footer.<\/p>\n
      <\/p>\n
      Figure 6: Add a page header and footer<\/p>\n
      Move the table so that it is close to the header and the left of the page. Also, drag the top of the footer to the bottom of the table. Drag the right side of the canvas to the table. The canvas should look like Figure 7.<\/p>\n
      <\/p>\n
      Figure 7: The canvas with header and footer<\/p>\n
      In the Report<\/em> Data<\/em> window, expand Built-in Fields<\/em>. Drag the Report<\/em> Name<\/em> field into the page header, as shown in Figure 8.<\/p>\n
      <\/p>\n
      Figure 8: Drag the Report Name<\/p>\n
      Expand the textbox width to the size of the canvas. Increase the font size to 22 and align the text in the centre. You can also drag Execution Time<\/em> and Page Number <\/em>to the footer. (Note that you may need to expand the are under the table where you can temporarily drag the first footer item before adding it to the footer.) The report canvas should now look like Figure 9.<\/p>\n
      <\/p>\n
      Figure 9: Formatted header and footer<\/p>\n
      Adding Simple Parameters<\/h2>\n
      SSRS will automatically add parameters to your report when you have variables in the WHERE<\/code> clause of the query. In this case, you\u2019ll add a parameter to filter on color. Double-click the dataset and change the query to this:<\/p>\n
      SELECT P.ProductID, P.Name AS ProductName, P.Color, P.Size, \r\n   P.ListPrice, PC.Name AS Category, PS.Name AS SubCategory\r\nFROM Production.Product AS P \r\nJOIN Production.ProductSubcategory AS PS \r\n  ON PS.ProductSubcategoryID = P.ProductSubcategoryID\r\nJOIN Production.ProductCategory AS PC\r\n  ON PC.ProductCategoryID = PS.ProductCategoryID\r\nWHERE P.Color = @color;<\/pre>\n
      Click OK<\/em>, and you\u2019ll see the new parameter @color listed in the Parameters<\/em> folder and the Parameters<\/em> section of the report canvas, as shown in Figure 10.<\/p>\n
      <\/p>\n
      Figure 10: The @color parameter<\/p>\n
      Preview the report. This time, it will not run automatically. Fill in the color \u201cblue\u201d and click View Report<\/em>. The report should look like Figure 11 with only blue items displayed.<\/p>\n
      <\/p>\n
      Figure 11: Filtered by blue<\/p>\n
      Right now, you must type in a valid color to get the report to return products. If you type in \u201cpurple,\u201d for example, no products will be returned.<\/p>\n
      There are quite a few properties you can set to control the behaviour of parameters. You might allow a blank value, for example, or supply a list of values from which to choose. To see the properties, double-click the parameter. The Report<\/em> Parameter<\/em> Properties<\/em> dialogue looks like Figure 12.<\/p>\n
      <\/p>\n
      Figure 12: The parameter properties<\/p>\n
      There are a few interesting items to note on the General<\/em> page. For example, what is the difference between Name<\/em> and Prompt<\/em>? The Name<\/em> refers to the actual name of the parameter that is used in the SQL query. The Prompt<\/em> is what the user will see. So, you might want to change the \u201cc\u201d in color to uppercase make it more user-friendly.<\/p>\n
      You can change the Data<\/em> Type<\/em> if you must restrict the type of values entered, such as numbers or dates. In fact, if you switch to date, the report will display a date picker control for the parameter when you run the report. There are three other options (Allow blank value<\/em>, Allow null value<\/em>, and Allow multiple values<\/em>) that will be covered later in the article. And, finally, there is the visibility property of the parameter. Here is what each option means:<\/p>\n
      Visible:<\/strong> The parameter is shown to the end-user who can change the value<\/p>\n
      Hidden:<\/strong> The end-user is not prompted for the parameter, but the value is typically passed in from a calling report<\/p>\n
      Internal:<\/strong> The end-user is not prompted and cannot change the value. This might be used for passing in the user id to the server.<\/p>\n
      There are three more pages to this dialogue. This article will cover Available Values<\/em> and Default Values<\/em>. Now, you\u2019ll learn how to provide a list of values for the parameter.<\/p>\n
      Adding a Parameter List<\/h2>\n
      It can be difficult for the user to remember the valid values for a report, so report developers often provide lists of values from which to choose. To provide a list of colors, follow these steps.<\/p>\n
      Switch to the parameter\u2019s Available Values<\/em> page. Currently, the option is set to None, <\/em>as shown in Figure 13, which means that no list is provided.<\/p>\n
      <\/p>\n
      Figure 13: The Available Values page<\/p>\n
      Switch to Specify values<\/em> and click Add<\/em>. You\u2019ll now have a space to type in the first value, as shown in Figure 14.<\/p>\n
      <\/p>\n
      Figure 14: Type in values<\/p>\n
      The Label<\/em> is shown to the end-user, while the Value<\/em> is passed to the SQL query. In this case, both values are the same. Enter the following list:<\/p>\n
        \n
      • Black<\/li>\n
      • Blue<\/li>\n
      • Grey<\/li>\n
      • Multi<\/li>\n
      • Red<\/li>\n
      • Silver<\/li>\n
      • Silver\/Black<\/li>\n
      • White<\/li>\n
      • Yellow<\/li>\n<\/ul>\n
        The screen should look like Figure 15 when you are done. Click OK<\/em> to save the list.<\/p>\n
        <\/p>\n
        Figure 15: The parameter list<\/p>\n
        Now when you preview the report, you\u2019ll see a list of colors from which to choose, as shown in Figure 16.<\/p>\n
        <\/p>\n
        Figure 16: The parameter with the list<\/p>\n
        Try running the report multiple times, each time with a different color to verify that the report works as expected.<\/p>\n
        If you are familiar with this data, you\u2019ll know that there are several products with no color (NULL<\/em>). How can you allow a user to see those products? You\u2019ll learn that next.<\/p>\n
        Searching for NULL values<\/h2>\n
        You may recall that there is a parameter option to allow NULL<\/em> (see Figure 12), but to use this option, you must make a change to your query that causes other complications later. It gets messy quickly, so I suggest substituting the NULLs<\/em> instead.<\/p>\n
        To get started, add another item to the available values in the Color<\/em> parameter, N\/A<\/em> for both Value<\/em> and Label<\/em>. Double-click the ProductList<\/em> dataset and change the query to this:<\/p>\n
        SELECT P.ProductID, P.Name AS ProductName, P.Color, P.Size, \r\n   P.ListPrice, PC.Name AS Category, PS.Name AS SubCategory\r\nFROM Production.Product AS P \r\nJOIN Production.ProductSubcategory AS PS \r\n  ON PS.ProductSubcategoryID = P.ProductSubcategoryID\r\nJOIN Production.ProductCategory AS PC\r\n  ON PC.ProductCategoryID = PS.ProductCategoryID\r\nWHERE COALESCE(P.Color,'N\/A') = @color;<\/pre>\n
        When you rerun the report and select N\/A<\/em>, you should see all the items with no color. So far, you are working with a static parameter list. Now, you\u2019ll learn how to create a dynamic list. Note that using a function like COALESCE<\/code> on a column in the WHERE<\/code> clause can often cause performance issues.<\/p>\n
        Using a Query for a Parameter List<\/h2>\n
        What happens if AdventureWorks gets in a new purple or orange product? You would have to manually add those colors to keep the parameter list up to date. Instead, you might want to maintain the list using a query. To do so, switch back to Design<\/em> view add a new Dataset<\/em> called Colors<\/em> to the report with this query that causes the N\/A<\/em> row to show up first.<\/p>\n
        SELECT DISTINCT COALESCE(Color,'N\/A') AS Color, \r\n\tCASE WHEN Color IS NULL THEN 0 ELSE 1 END AS SortOrder\r\nFROM Production.Product AS P \r\nORDER BY SortOrder, Color;<\/pre>\n
        Figure 17 shows how the dataset should look.<\/p>\n
        <\/p>\n
        Figure 17: The Colors dataset<\/p>\n
        Click OK<\/em> to create the dataset. Now open the parameter properties again and switch to the Available Values<\/em> page. Select Get values from a query<\/em>. Under Dataset<\/em>, select Colors<\/em>. In both the Values<\/em> and Labels field, select Color<\/em>. The properties should look like Figure 18.<\/p>\n
        <\/p>\n
        Figure 18: Using a query for the parameter list<\/p>\n
        Click OK<\/em> to save the change and be sure to test the report. If you don\u2019t mind modifying a row of the Product<\/em> table, run this update statement in SSMS or Azure Data Studio.<\/p>\n
        UPDATE Production.Product \r\nSET Color = 'Orange'\r\nWHERE ProductID IN (802, 803);<\/pre>\n
        If you rerun the report, you should see Orange<\/em> in the parameter list and the orange items in the results. Figure 19 shows the report.<\/p>\n
        <\/p>\n
        Figure 19: The orange items<\/p>\n
        You might want to give the ability to select multiple items at once. The next section will show you how to do that.<\/p>\n
        Selecting Multiple Values<\/h2>\n
        The person running your report might want to see more than one color at a time, maybe even all of them. There is a setting on the General page of the parameter properties (see Figure 12) that allows you to select more than one item. If you do this, however, your query will error, and the report will not run. Figure 20 shows the error message:<\/p>\n
        <\/p>\n
        Figure 20: The error message after setting Allow multiple values<\/em>.<\/p>\n
        The query sent to SQL Server uses = (equal to), but the variable holds a comma-delimited list of values. To fix this issue, you\u2019ll need to modify the ProductList<\/em> query to this:<\/p>\n
        SELECT P.ProductID, P.Name AS ProductName, P.Color, P.Size, \r\n   P.ListPrice, PC.Name AS Category, PS.Name AS SubCategory\r\nFROM Production.Product AS P \r\nJOIN Production.ProductSubcategory AS PS \r\n  ON PS.ProductSubcategoryID = P.ProductSubcategoryID\r\nJOIN Production.ProductCategory AS PC\r\n  ON PC.ProductCategoryID = PS.ProductCategoryID\r\nWHERE COALESCE(P.Color,'N\/A') IN (@color);<\/pre>\n
        After running, the report should look something like Figure 21 when Multi<\/em> and Orange<\/em> are selected.<\/p>\n
        <\/p>\n
        Figure 21: Selecting multiple values<\/p>\n
        So far, you have added just one parameter to the report. Many of the reports you run in the future will have more than that. Either the dataset will have multiple predicates in the WHERE<\/code> clause, or you might also use parameters to control something about how the report looks. In the next section, you\u2019ll learn how to control the value of a textbox in the report with a parameter.<\/p>\n
        Displaying Parameter Values on the Report<\/h2>\n
        Parameters are the \u201cworkhorse\u201d of SSRS. You can do so many things with them. In this section, you\u2019ll learn that you can display the value or label of a parameter in a textbox.<\/p>\n
        Back in Design<\/em> view, add a Textbox<\/em> to the header section of the report. Drag it to the left of the page and expand the width. It should look like Figure 22.<\/p>\n
        <\/p>\n
        Figure 22: The new Textbox<\/p>\n
        Right-click on the new Textbox<\/em> and select Expression<\/em>, as shown in Figure 23.<\/p>\n
        <\/p>\n
        Figure 23: Select Expression<\/p>\n
        Just about any property in an SSRS report can be controlled with an Expression<\/em>, i.e., a formula. You\u2019ll learn much more about expressions throughout these articles, but this is a simple example to get you started. Once you select Expression<\/em> in the menu, the Expression<\/em> dialogue should pop up, as shown in Figure 24.<\/p>\n
        <\/p>\n
        Figure 24: The Expression dialogue<\/p>\n
        Any expression begins with an equal to sign (=) similar to formulas in Excel. The Category<\/em> area contains dozens of built-in fields and functions that you can use to build these expressions. Change the expression to<\/p>\n
        =\"Colors chosen: \" +<\/pre>\n
        Then, make sure your cursor is to the right of the plus sign (+), click Parameters<\/em> and double-click color<\/em> in the Values<\/em> window, as shown in Figure 25.<\/p>\n
        <\/p>\n
        Figure 25: The expression<\/p>\n
        The final expression should be:<\/p>\n
        =\"Colors chosen: \" + Parameters!color.Value(0)<\/pre>\n
        Click OK<\/em> to save the expression. The Textbox<\/em> will show <<Expr>><\/em> instead of a field name. Run the report but select only one color. The report should look like Figure 26 if you selected Orange<\/em>. The value you chose is visible on the report.<\/p>\n
        <\/p>\n
        Figure 26: The parameter value displayed<\/p>\n
        This works great, but it will only display one item. It\u2019s possible that you are allowing multiple values to be selected. When you select more than one, only the first item is displayed. The reason is that the parameter values are held in an array of strings. Right now, the formula displays the first item in the array.<\/p>\n
        To display all the chosen values, go back to Design<\/em> view and bring up the Expression<\/em> dialogue again. Change the formula to this:<\/p>\n
        =\"Colors chosen: \" + Join(Parameters!color.Value,\", \")<\/pre>\n
        Notice that the index of the array (0) was removed. The Join<\/code> function builds a string from the array values. Now when you run the report, it will look something like Figure 27.<\/p>\n
        <\/p>\n
        Figure 27: Displaying multiple values<\/p>\n
        In this example, the Values<\/em> and Labels<\/em> of the parameter are identical. In many cases, they are different. For example, the query might need an ID number while the person running the report might like to see the name. To get around this, change the formula so that the user-friendly label is used instead of the value:<\/p>\n
        =\"Colors chosen: \" + Join(Parameters!color.Label,\", \")<\/pre>\n
        You can also use parameters to change the properties of objects on the report. You\u2019ll learn how to do this next.<\/p>\n
        Using Parameters to Control Properties<\/h2>\n
        Just about any property in SSRS can be controlled with an expression. If you take a look at the Text Box Properties<\/em> dialogue of the Textbox<\/em> you created in the last section, you\u2019ll see the fx<\/em> symbol next to two properties, as shown in Figure 28.<\/p>\n
        <\/p>\n
        Figure 28: The fx<\/em> symbol<\/p>\n
        Clicking this symbol anywhere you see it brings up the Expression<\/em> box to control the associated property. Before adding in an expression, cancel out of this dialogue. Create a new parameter called Background<\/em> by right-clicking the Parameters<\/em> folder and selecting Add<\/em> Parameter<\/em>. Add these values\/labels on the Available<\/em> Values<\/em> page.<\/p>\n
          \n
        • Yellow<\/li>\n
        • LightBlue<\/li>\n
        • Plum<\/li>\n<\/ul>\n
          Once all the parameter properties are in place, click OK<\/em>. You\u2019ll then see the second parameter in the list of parameters. Remember that this one isn\u2019t connected to a dataset query; it will be used to control the background, or fill, color of the Textbox<\/em>.<\/p>\n
          The next step is to connect the parameter to the Textbox<\/em>. Right-click and select Text<\/em> Box<\/em> Properties<\/em>. Select the Fill<\/em> page. Click the fx<\/em> symbol, as shown in Figure 29.<\/p>\n
          <\/p>\n
          Figure 29: The Fill property<\/p>\n
          The initial expression is \u201cNo Color.\u201d Replace it with this formula:<\/p>\n
          =Parameters!Background.Value<\/pre>\n
          The Expression<\/em> dialogue should look like Figure 30.<\/p>\n
          <\/p>\n
          Figure 30: The background expression<\/p>\n
          Click OK<\/em> twice to save the property change. Now, try running the report. If you chose LightBlue<\/em>, the report should look something like Figure 31.<\/p>\n
          <\/p>\n
          Figure 31: The textbox with a blue background<\/p>\n
          This simple example demonstrated how powerful expressions and parameters are. Next, you\u2019ll see how to set default values for parameters.<\/p>\n
          Using Default Parameters<\/h2>\n
          In some cases, the user is likely to select a specific value for a parameter and only rarely change it. To learn how to set up a default value for the parameter, open the properties of the Background<\/em> parameter. Select the Default<\/em> Values<\/em> page and Specify<\/em> values<\/em>, as shown in Figure 32.<\/p>\n
          <\/p>\n
          Figure 32: The Default Values page<\/p>\n
          Click Add<\/em>. Type in your favourite of the three colors, LightBlue<\/em>, Plum<\/em>, or Yellow<\/em>. The property should look like Figure 33. Click OK<\/em> to save the changes.<\/p>\n
          <\/p>\n
          Figure 33: Filling in the default value<\/p>\n
          Now when you run the report, the background color will be automatically filled in. You can also get default values from a dataset. Open the Default<\/em> Values<\/em> properties of the color parameter. Select Get<\/em> values<\/em> from<\/em> a query<\/em>. Fill in the Colors<\/em> Dataset<\/em> and Color<\/em> Value<\/em> field<\/em>. The properties should look like Figure 34.<\/p>\n
          <\/p>\n
          Figure 34: The default values from a dataset<\/p>\n
          In this case, all colors will be selected when you run the report.<\/p>\n
          One of the most common requests is to make the selection of one parameter filter another one. You\u2019ll learn how to do that next.<\/p>\n
          Creating Cascading Parameters<\/h2>\n
          Each product belongs to a subcategory, and each subcategory belongs to a category. This is the type of hierarchical relationship that works well when parameters work together with what\u2019s called Cascading<\/em> Parameters<\/em>. Figure 35 illustrates how this will work.<\/p>\n
          <\/p>\n
          Figure 35: The product\/category hierarchy<\/p>\n
          The first step is to modify the ProductList<\/em> dataset query so that it prompts for the subcategory. Change the query to this:<\/p>\n
          SELECT P.ProductID, P.Name AS ProductName, P.Color, P.Size, \r\n   P.ListPrice, PC.Name AS Category, PS.Name AS SubCategory\r\nFROM Production.Product AS P \r\nJOIN Production.ProductSubcategory AS PS \r\n  ON PS.ProductSubcategoryID = P.ProductSubcategoryID\r\nJOIN Production.ProductCategory AS PC\r\n  ON PC.ProductCategoryID = PS.ProductCategoryID\r\nWHERE COALESCE(P.Color,'N\/A') IN (@color)\r\n  AND P.ProductSubcategoryID = @subcategory;<\/pre>\n
          To make sure that the query works, add the SubCategory<\/em> and Category<\/em> fields to the report. Preview the report. Enter subcategory 31. The report should look something like Figure 36.<\/p>\n
          <\/p>\n
          Figure 36: Filtering with subcategory<\/p>\n
          At this point, the products are being filtered by subcategory, but the ID must be typed in. To get around this issue, add a new dataset called Subcategory<\/em> with this query:<\/p>\n
          SELECT PS.ProductSubcategoryID, PS.Name AS SubcategoryName\r\nFROM Production.ProductSubcategory AS PS\r\nORDER BY SubcategoryName;<\/pre>\n
          Connect the Subcategory<\/em> dataset to the subcategory<\/em> parameter. The Values<\/em> field<\/em> should be ProductSubcategoryID<\/em>, and the Label<\/em> field<\/em> should be SubcategoryName<\/em>. In this case, the query needs the ID while the user needs the name. The Available<\/em> Values<\/em> properties should look like Figure 37.<\/p>\n
          <\/p>\n
          Figure 37: Connect the dataset to the parameter<\/p>\n
          If you review Figure 35, you\u2019ll see that subcategories should be filtered by category. To do this, change the Subcategory<\/em> dataset so that it\u2019s filtered by category:<\/p>\n
          SELECT PS.ProductSubcategoryID, PS.Name AS SubcategoryName\r\nFROM Production.ProductSubcategory AS PS\r\nWHERE PS.ProductCategoryID = @category\r\nORDER BY SubcategoryName;<\/pre>\n
          You now have four parameters in place. Notice that Category<\/em> is listed before Subcategory<\/em> in Figure 38. That\u2019s because you must choose Category<\/em> before Subcategory. In this parameter area, you can rearrange the parameters by dragging them around. The report will break if Category<\/em> is not located before Subcategory<\/em>!<\/p>\n
          <\/p>\n
          Figure 38: The four parameters<\/p>\n
          The next logical step is to add a dataset for Category<\/em>. Use this query:<\/p>\n
          SELECT PC.ProductCategoryID, PC.Name AS CategoryName\r\nFROM Production.ProductCategory AS PC \r\nORDER BY CategoryName;<\/pre>\n
          Connect the dataset to the new Category<\/em> parameter. You guessed it! The Value<\/em> field<\/em> is ProductCategoryID<\/em>, and the Label<\/em> field<\/em> is CategoryName<\/em>. The Available<\/em> Values<\/em> page should look like Figure 39.<\/p>\n
          <\/p>\n
          Figure 39: The category Available Values<\/p>\n
          If you did everything correctly, the parameters should look like Figure 40 when you preview the report. Notice that the Subcategory<\/em> parameter is greyed out until you select a Category<\/em>.<\/p>\n
          <\/p>\n
          Figure 40: The Subcategory parameter is not available<\/p>\n
          When you select a Category<\/em>, the Subcategory<\/em> parameter refreshes. For example, if you select Bikes<\/em>, only the available bike subcategories show up. Figure 41 shows how this looks.<\/p>\n
          <\/p>\n
          Figure 41: The filtered subcategory<\/p>\n
          Configuring Cascading<\/em> Parameters<\/em> is one of the most challenging things to understand in SSRS. Hopefully, I\u2019ve shown that by breaking the steps down and completing them one at a time, it is doable.<\/p>\n
          Conclusion<\/h2>\n
          Learning about parameters is critical for SSRS developers. In this article, you learned many ways in which parameters are used, including with a list of available values from a query, multiple selections, defaults, cascading, and more. In the next article, you\u2019ll learn about more features that make SSRS reports dynamic.<\/p>\n
           <\/p>\n","protected":false},"excerpt":{"rendered":"
          Kathi Kellenberger continues her series on SSRS. In this article you learn how to use parameters that let your report users control how the reports are filtered.…<\/p>\n","protected":false},"author":110218,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[143528],"tags":[95509],"coauthors":[11292],"class_list":["post-84917","post","type-post","status-publish","format-standard","hentry","category-bi-sql-server","tag-standardize"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/84917","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/users\/110218"}],"replies":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/comments?post=84917"}],"version-history":[{"count":3,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/84917\/revisions"}],"predecessor-version":[{"id":85083,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/84917\/revisions\/85083"}],"wp:attachment":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/media?parent=84917"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/categories?post=84917"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/tags?post=84917"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/coauthors?post=84917"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}