Skip to content

Commit cd6984c

Browse files
committed
fix build errors
1 parent 1c3c1d7 commit cd6984c

File tree

3 files changed

+31
-3
lines changed

3 files changed

+31
-3
lines changed

docs/report/powerbi/sample-boards-featureprogress.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -244,7 +244,7 @@ https://analytics.dev.azure.com/{organization}/{project}/_odata/v3.0-preview/Wor
244244

245245
## Transform the data in Power BI
246246

247-
The query returns several columns that you need to expand before you can use them. Any entity pulled in using an OData **$expand** statement returns a record with potentially several fields. Expand the record to flatten the entity into its fields.
247+
The query returns several columns that you need to expand before you can use them to create a report. Any entity pulled in using an OData **$expand** statement returns a record with potentially several fields. Expand the record to flatten the entity into its fields.
248248

249249
For the Feature Progress report, you'll need to carry out the following transforms:
250250

docs/report/powerbi/sample-boards-releaseburndown.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ https://analytics.dev.azure.com/{organization}/{project}/_odata/v3.0-preview/Wor
9696
- `{project}` - Your team project name, or omit "/{project}" entirely, for a cross-project query
9797
- `{areapath}` - Your Area Path. Example format: `Project\Level1\Level2`
9898
- `{tag}` - A tag that represents your release. All work items tagged with `{tagname}` are included in the report
99-
- `{startdate}` - The date to start the burndown report
99+
- `{startdate}` - The date to start the burndown report with the format: `YYYY-MM-DDZ`. For example: `2022-04-01Z` represents 2022-April-01. Don't enclose in quotes.
100100
- `{enddate}` - The date to end the burndown report.
101101

102102

docs/report/powerbi/transform-analytics-data-report-generation.md

+29-1
Original file line numberDiff line numberDiff line change
@@ -169,7 +169,7 @@ From the Power Query Editor, select the ribbon **Transform** menu.
169169

170170
Sometimes one or more records will contain null values. For example, a value may not have been entered for **Story Points** or **Remaining Work**.
171171

172-
:::image type="content" source="media/transform-data/records-null-data.png alt-text="Screenshot of Power BI table containing null values. .":::
172+
:::image type="content" source="media/transform-data/records-null-data.png" alt-text="Screenshot of Power BI table containing null values.":::
173173

174174
For easier reporting, replace nulls with zero by following these steps.
175175

@@ -180,6 +180,34 @@ For easier reporting, replace nulls with zero by following these steps.
180180
- Enter "0" in **Replace With**.
181181
1. Choose **OK**.
182182

183+
## Create a custom column
184+
185+
<a id="create-percent-complete" />
186+
187+
### Create a percentage complete computed column
188+
189+
1. Select **Add Column** menu.
190+
1. Select **Custom Column**.
191+
1. Enter **PercentComplete** for **New column name**.
192+
1. Enter the following in **Custom column formula**.
193+
194+
```
195+
= [Completed]/([Proposed]+[InProgress]+[Resolved]+[Completed])
196+
```
197+
:::image type="content" source="media/reports-boards/custom-column-dialog-percent-complete.png" alt-text="Custom Column Dialog, PercentComplete syntax.":::
198+
199+
> [!NOTE]
200+
> It is possible you won't have a **Resolved** column, if the work items don't have States mapped to the Resolved State Category.
201+
> If so, then omit "[Resolved]" in the above formula.
202+
203+
1. Press **OK**.
204+
1. Select **Transform** menu.
205+
1. Select **Data Type** and select **Percentage**.
206+
207+
[!INCLUDE [temp](includes/sample-finish-query.md)]
208+
209+
210+
183211
184212
## Rename column fields
185213

0 commit comments

Comments
 (0)