Before you begin to map items to the spreadsheet, ensure that your spreadsheet is not protected. If the protection scheme for your worksheet prevents any user actions, you will not be able to select cells in the spreadsheet. First, unprotect the sheet and then add cell mappings.
The number of areas and cells to map differs according to the metric you select, the granularity, the date range, and the filters you have set. For example, if you select Site Metric > Traffic Report, set Week granularity, and set date range for Last 2 Weeks, you are prompted to map three cells (when using Custom Layout) on the Request Wizard: Step 2. The request retrieves data for week one and data for week two, where each data point value = the value of a page view. Your third cell serves as the row heading, which you can configure using Format Options.
If you mistakenly map incompatible locations on the spreadsheet, report builder issues an error.
The following sections contain more information:
On the Request Wizard: Step 2, when you enable Custom Layout for a trended request, you can map the request to a range of cells.
Click the Range Selector
next to the item you want to map.
You select the data by clicking the Range Selection icon
and click-dragging the mouse over the desired range of cells of the spreadsheet. A continuous selection is outlined by a black border.
Separate selected rows have a thin white border around each row.
To map separate rows in one request, use the Control key, then click and drag the cursor over the desired cells. You would do this if your request calls for four areas with ten cells each, rather than one continuous area with 40 cells together.
After you select cells, click the Range Selector again on the Range Selection form to return to the Request Wizard: Step 2.
If you mistakenly choose to map to a cell that already has an active mapping, you will notice that no cell reference appears in the text box next to the range-picker icon. When you click OK, report builder displays the error, “The range selected intersects another request’s range. Please change your selection.”
If you want to avoid this message, you can take two approaches:
To test for areas with embedded requests, you can: