{"id":1916,"date":"2014-12-03T00:00:00","date_gmt":"2014-12-03T00:00:00","guid":{"rendered":"https:\/\/test.simple-talk.com\/uncategorized\/sql-server-reporting-services-basics-the-visual-controls\/"},"modified":"2021-05-17T18:33:16","modified_gmt":"2021-05-17T18:33:16","slug":"sql-server-reporting-services-basics-the-visual-controls","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/databases\/sql-server\/bi-sql-server\/sql-server-reporting-services-basics-the-visual-controls\/","title":{"rendered":"SQL Server Reporting Services Basics: The Visual Controls"},"content":{"rendered":"
\n

\tThis is the third article in a four-part series on SQL Server Reporting Services 2012 (SSRS). Part 1<\/a>, Building Basic Reports<\/em>, provided a step-by-step guide to basic report creation and Part 2<\/a>, Customizing SSRS Reports<\/em>, took a tour of some of the core SSRS features and functions that you’ll need to develop dynamic reports. In this article, you will learn about the rich set of visual features included with SSRS. <\/p>\n

\tStarting with SSRS 2005, Microsoft has included a scaled-down version of the Dundas Chart Control<\/a>. Starting with 2008 R2, SSRS has an impressive set of visual controls including gauges, indicators, sparklines, and maps. For many people, these features alone offer a compelling reason to adopt SSRS and upgrade to at least 2008 R2. <\/p>\n

Getting Started<\/h1>\n

\tIn order to work through the examples, you will need to have installed and configured SQL Server 2012, SQL Server 2012 Reporting Services, and SQL Server Data Tools (SSDT). The examples will also work with the 2008 R2 version of Reporting Services, in which case you will need Business Intelligence Development Studio (BIDS) instead of SSDT for report development. For further details, please refer back to the Installing and Configuring Reporting Services<\/em> section of the previously-referenced Building Basic Reports<\/em> article. The examples will also work with SQL Server 2014, since there were no significant changes in report development with this release. <\/p>\n

\tThe code bundle for this article (see the Code Download<\/em> link in the speech bubble to the right of the article title) contains all the files you need to get started. You’ll need to create the ReportDemo<\/code> database, by running the ReportingDemoDatabaseScript.sql<\/code> script. <\/p>\n

\tThis article assumes that you understand the basics of creating reports, data sources, datasets, parameters, and grouping. If not, please review parts 1 and 2 of this series before proceeding. <\/p>\n

Basic Charts<\/h1>\n

\tSSRS is great for displaying data in a tabular or matrix format. You can add hierarchical grouping levels and totals. However, sometimes a picture is worth a thousand words, and as a report developer you will often be asked to display the data in an easily-digestible, visual format. The most basic way to display data, for example ‘sales by year’ or ‘sales by territory’ is with a chart. <\/p>\n

Creating a basic chart<\/h2>\n

\tLaunch SSDT, or BIDS if you are running an earlier version of SSRS, and create a new report server project called ChartProject<\/code>. Add a shared data source, ReportDb.rds<\/code>, which points to the ReportingDemo<\/code> database to the project. <\/p>\n

\tThe goal is to design a report that will display the total value of customer purchases on a given date. Add a new report called MyChart.rdl<\/code> to the project (right click Reports<\/strong>, select Add<\/strong> | New item<\/strong>). Highlight the chart report and then from the left-hand Report Data<\/strong> menu, add a data source called ReportDb<\/code> that references the ReportDb<\/code> shared data source. Set up an embedded dataset for the report based on ReportDb<\/code> and using the following query, which fetches various bits of information pertaining to customer purchases, including the field we wish to “measure”, i.e.<\/em>PurchaseAmount<\/strong>, over time (PurchaseDate<\/strong>). <\/p>\n

SELECT Purchase.PurchaseID ,\n       Purchase.CustomerID , \n       Purchase.PurchaseDate , \n       Purchase.PurchaseType , \n       Purchase.PurchaseAmount , \n       Customer.FirstName + ' ' + Customer.LastName AS CustomerName \nFROM   Purchase \n       INNER JOIN Customer ON Purchase.CustomerID = Customer.CustomerID\n<\/pre>\n
 \tListing 1 <\/p>\n
 \tOn your new report, expand out the design area so that you have room to work, and then drag onto the design area a chart control. When prompted to select a chart type, select the basic column chart, as shown in Figure 1, and click OK<\/strong>. <\/p>\n
 \t\"2105-1-c69d3b1f-6c30-4eee-adf2-452a88cda\"<\/p>\n
 \tFigure 1 <\/p>\n
 \tAs you can see there are many available chart types, including some 3D charts. In my experience, 3D rendering can distort the heights of the columns, so use caution. Simpler is usually better. <\/p>\n
 \tHaving selected the chart type, the Chart Data<\/strong> window pops open, as shown in Figure 2. This is where you will add the fields to be measured. <\/p>\n
 \t\"2105-1-c1885f64-86e3-4958-9cd8-c390bcf94\"<\/p>\n
 \tFigure 2 <\/p>\n
 \tThe â Values<\/strong> section is where you add the summary value for the chart, such as “total sales”. On a bar chart like this one, the field you add here will control the height of the bars. SSRS will calculate an aggregate value for the field added to this section, such as a sum (the default), or a count. <\/p>\n
 \tAlong the horizontal axis, several bars will be displayed. The Category Groups<\/strong> section controls the data represented by each of the bars. Generally, it is a limited set of data, such as several years, the months of one year, territories, or departments. In additions, the Category Group Properties<\/strong> allow you to, for example, add filters or change the sort order of the category field. <\/p>\n
 \tNotice that there is also a section called Series Group<\/strong> that you can use to break out the data by series as well as category. You will see how to use Series Groups<\/strong> a little later in this section. <\/p>\n
 \tClick the yellow plus sign and add the PurchaseAmount<\/strong> field into the â Values section and make sure that the SUM<\/code> function has been applied. You can change the aggregate function by clicking the down area next to the aggregate expression, selecting Aggregate<\/strong> and then selecting a different function. <\/p>\n
 \tSince you’re working with such a small data set, you’ll simply use PurchaseDate<\/strong> for the category group, so SSRS will group on this field, and present the total purchase amount by date. If you wanted to show the purchase amount by year instead of date, I suggest changing the original query to an aggregate that totals the sales, and then groups by YEAR(PurchaseDate)<\/code>. <\/p>\n
 \tTo display the total purchase amount on the chart by purchase date, change (Details)<\/strong> to PurchaseDate<\/strong>. The Chart Data windows should look like Figure 3. <\/p>\n
 \t\"2105-1-06c78147-9755-4adc-85e2-088668c2f\"<\/p>\n
 \tFigure 3 <\/p>\n
 \tExpand the size of the chart two or three times. Save the report and navigate to the Preview<\/strong> tab to run the report. It should look as shown in Figure 4. <\/p>\n
 \t\"2105-1-a9a88392-ca98-4c5f-82c3-b73bfec6f\"<\/p>\n
 \tFigure 4 <\/p>\n
 \tThis report shows total sales by purchase date, but what if it needed instead to show the sales by date for different types of purchase, such as online purchases, versus in-store purchases, and so on. You can achieve this by adding the PurchaseType<\/strong> field as a Series Group. For every field in the Values<\/strong> area, we’d see a series of bars, each one representing a distinct value that exists in the Series Group<\/strong> field. So, for example, if the PurchaseType<\/strong> field contains three distinct types of purchase, then you’ll see three series for each field in the Values<\/strong> area. <\/p>\n
 \tIn the Series Groups<\/strong> section of the chart’s data properties, click the plus sign and add PurchaseType<\/strong>. Preview the report again, and you should see the data displayed based on the type of purchase. <\/p>\n
 \t\"2105-4572a8f8-7508-4ad5-8a4e-1460ebfe4e1\"<\/p>\n
 \tFigure 5 <\/p>\n
Formatting the Chart<\/h2>\n
 \tYou now have a chart, but, there is still work to do in order to get it into a nice format. For a start, the date format does not look good, so fix that first. On the Design<\/strong> tab of the report, right-click the text area along the bottom of the chart that says “Purchase date A” and bring up the Horizontal Axis Properties<\/strong> dialog. Select the Number<\/strong> option from the left menu, and then the Date<\/strong> category. Select the appropriate date format and click OK<\/strong>. You can make the same type of change to the vertical axis if needed, for example formatting it as currency. Often the numbers on the vertical axis are very large and it might help to display the values as thousands, for example. <\/p>\n
 \tModify the title at the top of the chart and then remove or modify the axis titles. If you wish to change the sort order of the Category Group<\/strong> field, click the dropdown box next to the category, select the Category Group Properties and navigate to the Sorting<\/strong> section. To change the color of the bars, right-click the one of them to get to the properties. After tweaking the properties, my report looks like Figure 6. <\/p>\n
 \t\"2105-1-4ebbb27b-8ef7-4731-98b6-7d649d8fa\"<\/p>\n
 \tFigure 6 <\/p>\n
Chart types<\/h2>\n
 \tAs noted earlier, the chart control can produce a variety of the different chart types. To switch to a different type, simply right-click on the chart (in the Design<\/strong> tab) and use the Change Chart Type<\/strong> option. <\/p>\n
 \tFirst, remove the Series Group (right click PurchaseType<\/strong> and select Remove Series Group<\/strong>) and try switching to a Smooth Line<\/strong> chart, the second of the line chart types. Right-click the series line and choose Series Properties<\/strong>. On the Series Data<\/strong> page, select [Sum(PurchaseAmount)]<\/strong> in the Tooltip<\/strong> dropdown box. On the Markers<\/strong> page, change the Marker Type<\/strong> to Circle<\/strong> and click OK<\/strong>. <\/p>\n
 \tNow when you run the report, hovering the mouse over a data point should reveal its value as a tooltip. You can format the ToolTip value by changing the Tooltip property to an expression that uses the FormatCurrency<\/strong> function: FormatCurrency(Sum(Fields!PurchaseAmount.Value))<\/strong>. Figure 7 shows how the report should look. <\/p>\n
 \t\"2105-1-a5fe9e16-986b-43d6-9508-7d1b3b299\"<\/p>\n
 \tFigure 7 <\/p>\n
Indicators<\/h1>\n
 \tSo far you have looked at charts to compare data over time, or by some other measure. You can also add visual elements to regular report sections. One visual element you can add is called an Indicator, which is generally used to provide a simple, visual signal of success or failure. For example, an indicator could show an upward arrow if a goal is met, a horizontal arrow if it is close, and a downward arrow if the goals was missed by a wide margin. <\/p>\n
 \tCreate a new report called Indicators.rdl<\/code> with the same data source and dataset (Listing 1) as the MyChart<\/code> report. Drag a table control into the report design area, and populate it with the PurchaseDate<\/strong>, CustomerName<\/strong> and PurchaseAmount<\/strong> fields. Format the report (highlight the header row and hit F4 to set the font and background color), then and add a new column to the right, as shown in Figure 8. <\/p>\n
 \t\"2105-1-af03d592-74bf-4447-b915-d37d908b4\"<\/p>\n
 \tFigure 8 <\/p>\n
 \tDrag an Indicator<\/strong> control to the empty cell and use the automatic Select Indicator Type<\/strong> dialog box to choose one of the indicator types. It is a good practice to select an indicator that changes shape, as well as color, depending on the value. If the shapes are identical, then the colors are lost when printed on a non-color printer. There are also many color blind people who can’t distinguish all colors. <\/p>\n
 \tThe Indicator can be set to one value, the one that you want to measure. Click the indicator control to open the Gauge Data<\/strong> window and select PurchaseAmount<\/strong> as the indicator value. SSRS will automatically apply a Sum<\/strong> expression. <\/p>\n
 \t\"2105-1-ef415f0f-8b10-4cc4-9cbd-9947d453c\"<\/p>\n
 \tFigure 9 <\/p>\n
 \tPreview the report and you should see an indicator, with the default properties, revealing at a glance the low, mid-range and high value sales, as shown in Figure 10. <\/p>\n
 \t\"2105-1-57a8f45b-9911-4157-8e19-3ca6ef718\"<\/p>\n
 \tFigure 10 <\/p>\n
 \tBy default, the indicator is based on percentages and distributed by thirds, but the properties of the indicator are very customizable. On the design view, right-click the indicator, select Indicator Properties<\/strong>, click Values<\/strong> and States<\/strong> where you can customize the values or percentages that determines which indicator to display. Figure 11 shows the default properties. <\/p>\n
 \t\"2105-1-3dd651e2-5b0f-47ff-b00c-b205f2019\"<\/p>\n
 \tFigure 11 <\/p>\n
 \tYou can alter the percent ranges, switch to specific values instead, modify the colors and indicators, or even add additional indicators for more ranges. <\/p>\n
Gauges<\/h1>\n
 \tThe gauge is a slightly more complex control that compares the data to a set goal. Again, though, its basic purpose is to allow a manager to see quickly the progress towards a given goal. <\/p>\n
 \tSay you’re asked to provide a manager with a report that will tell him or her quickly whether or not the team is on track to meet a yearly sales target. Create a new report called Gauge<\/code> with the same ReportDb<\/code> data source. The data set just needs to include the field to measure, in this case the SUM(<\/strong>[<\/strong>PurchaseAmount<\/strong>])<\/strong>, broken down by year, so use the query in Listing 2. <\/p>\n
SELECT    YEAR([PurchaseDate]) AS PurchaseYear , \n          SUM([PurchaseAmount]) AS Amt \nFROM      [Purchase] \nGROUP BY  YEAR(PurchaseDate)\n<\/pre>\n
 \tListing 2 <\/p>\n
 \tAdd a table control to the report containing both of the fields. In the third data cell, drag in a gauge control. When prompted to select a gauge type, choose the first Linear gauge. Expand the width and height of the cell containing the gauge and format the report so that it looks similar to Figure 12. <\/p>\n
 \t\"2105-1-c5413c1b-5114-451c-9d35-2b6a7ed6f\"<\/p>\n
 \tFigure 12 <\/p>\n
 \tAt a minimum, you must set the value to measure, so click on the gauge to open the Gauge Data<\/strong> window and select Amt<\/strong> from the list. Once again, SSRS applies the SUM<\/strong> aggregate function automatically. <\/p>\n
 \tRight now, the gauge resembles a Celsius thermometer at 10 degrees. If you run the report now, all of the values will be at 100 since the amounts are all over 100, as shown in Figure 13. <\/p>\n
 \t\"2105-1-58692d14-c4a7-4e65-a864-339096f18\"<\/p>\n
 \tFigure 13 <\/p>\n
 \tTo alter the scale and the range (the red area), return to the Design<\/strong> tab. Right-click the range to bring up the Linear Scale Range Properties<\/strong> dialog box. Change the Start range scale value<\/strong> to 0 and End range at scale value<\/strong> to 1000. On the Fill<\/strong> properties, change the Color<\/strong> to Red<\/strong> and the Secondary Color<\/strong> to Green<\/strong>. Click OK. <\/p>\n
 \tNext, right-click on the scale and bring up the Linear Scale Properties<\/strong> dialog box. On the General<\/strong> tab, set the Maximum value to 1000. Click OK<\/strong> and now preview the report as shown in Figure 14. <\/p>\n
 \t\"2105-1-c75e12d8-e807-469c-a464-a2a8648d1\"<\/p>\n
 \tFigure 14 <\/p>\n
 \tYou can also add a gauge control to the report, outside of the table. In this case, the gauge will display the total aggregate value across the entire data set, in this case the total purchase amount over all years. <\/p>\n
 \tAdd a gauge control to the report area, and select the default type. Set the properties in a similar way as the previous example, but use 3000 for the maximum value of the scale and range. When you preview the report, the gauge should look similar to Figure 15. <\/p>\n
 \t\"2105-1-09968bf4-e78b-4059-8bd0-02839375e\"<\/p>\n
 \tFigure 15 <\/p>\n
Data bars and Sparklines<\/h1>\n
 \tData bars and Sparklines allow you to add visual detail to a grouping level within a report. For example, say you want to add a visual element to the report that indicates the trend of the sales for each month. This is a perfect use case for the sparkline. If you also want a visual way to see the sales broken down by categories then you can use a data bar. <\/p>\n
 \tCreate a new report called SparklineDatabar<\/code>. Listing 3 show the query for the report. <\/p>\n
SELECT   YEAR([PurchaseDate]) AS PurchaseYear , \n         SUM([PurchaseAmount]) AS Amt , \n         MONTH(PurchaseDate) AS PurchaseMonth , \n         PurchaseType \nFROM     [Purchase] \nGROUP BY YEAR(PurchaseDate) , \n         MONTH(PurchaseDate) , PurchaseType\n<\/pre>\n
 \tListing 3 <\/p>\n
 \tDrag a table to the report and add the Amt<\/strong>. Right-click on Amt<\/strong>, select Add Group<\/strong> | Row Group<\/strong> | Parent Group<\/strong>, group by PurchaseYear<\/strong> and check Add group header<\/strong>. Remove one of the empty columns. At this point, the report should similar to Figure 16. <\/p>\n
 \t\"2105-1-f62b58f6-5a46-4a67-ae2c-da8d2dbff\"<\/p>\n
 \tFigure 16 <\/p>\n
 \tDrag a data bar<\/strong> control to the cell at the intersection of the third column and second row. Select the default type and click OK<\/strong>. Click the data bar to open up the Chart Data<\/strong> window which looks just like the window used in the regular chart earlier in the article. Select Amt<\/strong> for the summary value and PurchaseType<\/strong> for the category group. The properties should look like Figure 17. <\/p>\n
 \t\"2105-1-94cef64b-1dbf-4163-9a20-eea25c6e0\"<\/p>\n
 \tFigure 17 <\/p>\n
 \tThe data bar control is essentially a small version of the chart control. Because it sits inside a cell, you cannot read the values or category. If the user of the report would like to see the values, you can add a tooltip. To do this, click twice in the cell with the data bar to select the bars. Right-click and select Series Properties<\/strong>. Click the Fx<\/strong> button next to the Tooltip<\/strong> property. Enter this expression: <\/p>\n
=Fields!PurchaseType.Value & \": \" & FormatCurrency(Fields!Amt.Value,0)\n<\/pre>\n
 \tClick OK twice to close both dialogs and then preview the report. Remember to mouse over the bars to see the tooltip. The report should look like Figure 18. <\/p>\n
 \t\"2105-1-e9ec309d-7208-4601-bdf5-bc1601efd\"<\/p>\n
 \tFigure 18 <\/p>\n
 \tNow back in the Design<\/strong> tab, add another column to the table. This time drag in a sparkline<\/strong> control to the cell next to the data bar and choose the first Line<\/strong> type. This time the category group should be PurchaseMonth<\/strong>. The data bar showed how the data was broken down by type of sale, but the sparkline will show how the data is broken down by month. Figure 19 shows how the properties should be set. <\/p>\n
 \t\"2105-1-bc497527-8342-43e9-b0ea-d0fcc1dc2\"<\/p>\n
 \tFigure 19 <\/p>\n
 \tThe tooltip expression for the sparkline’s Series Properties<\/strong> should be as follows: <\/p>\n
=MonthName(Fields!PurchaseMonth.Value) & \": \" & \nFormatCurrency(Fields!Amt.Value,0)\n<\/pre>\n
 \tChange the Marker Type<\/strong> to Square<\/strong>. Preview the report. It should look like Figure 20. <\/p>\n
 \t\"2105-1-22fa17d4-7f47-469a-a32b-78ff9b8a0\"<\/p>\n
 \tFigure 20 <\/p>\n
Maps<\/h1>\n
 \tThe final type of visualization is probably the most interesting. You can add maps to your reports to display data geographically. In this section, you will just set up a simple map that shows the location of the sales, but the world is your limit here (pun intended). <\/p>\n
 \tAdd a new report called Map<\/strong> with a dataset called MapData<\/strong>, defined by the query in Listing 4. <\/p>\n
SELECT   Purchase.PurchaseID , \n         Purchase.CustomerID , \n         Purchase.PurchaseDate , \n         Purchase.PurchaseType , \n         ISNULL(Purchase.PurchaseAmount, 0) AS Amt , \n         CASE WHEN PurchaseType IS NULL THEN 0 \n              ELSE 1 \n         END AS Sale , \n         State \nFROM     Customer \n         LEFT JOIN Purchase ON Purchase.CustomerID = Customer.CustomerID\n<\/pre>\n
 \tListing 4 <\/p>\n
 \tAdd a map control from the Toolbox. When you do, a wizard appears. On the first page, you select the source of spatial data. You can select the built-in maps from the Map Gallery, an ESRI shape file, or spatial data from SQL Server. Select the simplest choice, the Map Gallery<\/strong> and USA<\/strong> by State Exploded<\/strong>. Click Next<\/strong>. <\/p>\n
 \tThe following screen allows you to zoom in and crop. Youcan also add a Bing Maps layer<\/strong>. The Bing Maps layer is really cool, but it can distract from the meaning of the data. For now, accept the defaults on this screen and click Next<\/strong>. <\/p>\n
 \tOn the Choose map visualization<\/strong> page, youselect the type of map, Basic, Color Analytical or Bubble. Select the Color Analytical Map<\/strong> and click Next<\/strong>. The next page is where you map a dataset to the map. Select the MapData<\/strong> dataset. <\/p>\n
 \tOn the Specify the match fields for special and analytical data<\/strong> page, you will link a field from the map itself to a field in the dataset. The data in the middle section is from the map. The data in the lowest section is your data. You need to map the STUSPS<\/strong> field from the Spatial data<\/strong> section to the State field in the dataset, so check the Match Fields checkbox next to STUPS<\/strong>, and select the State<\/strong> field in the Analytical data<\/strong>set fields<\/strong> section, as shown in Figure 21. <\/p>\n
 \t\"2105-1-356f1ca8-a60b-48ac-95ae-5e84f2496\"<\/p>\n
 \tFigure 21 <\/p>\n
 \tClick Next<\/strong>. On the Choose color theme and data visualization<\/strong> page you will set the color properties and link the colors to a field in the data. In the Field to visualize<\/strong>, select SUM(<\/strong>[<\/strong>Amt<\/strong>])<\/strong>. The Color<\/strong> rule is set so that smaller values are green and larger values are red, the opposite of what you need to see. Switch the order to Red-Yellow-Green<\/strong>. Click Finish<\/strong> and preview the report. It should look like Figure 22. <\/p>\n
 \t\"2105-1-e2928d2d-45bf-4237-9bbe-4718952ca\"<\/p>\n
 \tFigure 22 <\/p>\n
Wrap up<\/h1>\n
 \tI hope this article has given you some insight into the visual controls. Between the visual controls’ rich features and SSRS’s ability to set nearly every property with an expression, you can see that Microsoft has delivered an extremely powerful and user-friendly set of visual features in this reporting tool. <\/p>\n
 \tStay tuned for Part 4 of this article series, which will peel back the layers on RDL (Report Definition Language) and take a look at Report Builder. <\/p>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"
The challenge of report development is to present complex data in a simple, visually compelling way. The goal is to make it as quick and easy as possible for others in the organization to use that data to make decisions, to see progress towards a business target, or spot and act on worrying trends sooner rather than later. Kathi Kellenberger demonstrates how to start adding visual flair to your SSRS reports, using its impressive set of visual controls, ranging from basic charts to gauges, indicators, sparklines, and maps.…<\/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":[4242,5983,5982,5753,4379,4179,5984,4150,4151,4400],"coauthors":[],"class_list":["post-1916","post","type-post","status-publish","format-standard","hentry","category-bi-sql-server","tag-basics","tag-charts","tag-graphs","tag-maps","tag-reporting-services","tag-source-control","tag-sparklines","tag-sql","tag-sql-server","tag-ssrs"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/1916","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=1916"}],"version-history":[{"count":4,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/1916\/revisions"}],"predecessor-version":[{"id":91014,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/1916\/revisions\/91014"}],"wp:attachment":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/media?parent=1916"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/categories?post=1916"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/tags?post=1916"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/coauthors?post=1916"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}