Update the build financial reporting page with clearer screenshots, slight edits to steps#2853
Conversation
…/customize-position.png
…/decimal-places.png
…/header-footer.png
…/prefix-suffix.png
…/value-display.png
…/semantic-formatting.png
…/quick-format-measure.png
…/quick-format.png
Updated the title and improved clarity in instructions for formatting numeric data and using templates.
|
@deepthy-dileep : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
PRMerger Results
|
There was a problem hiding this comment.
Pull request overview
Updates the “build financial reports” documentation for Intelligence sheets to improve clarity and consistency in the instructions and supporting guidance.
Changes:
- Renames the article H1 to better reflect the “build financial reports” focus.
- Refines a formatting step to use a clearer UI path description.
- Adds a TIP callout and fixes minor Markdown formatting/indentation for list and image blocks.
| --- | ||
|
|
||
| # Financial data reporting in Intelligence sheets | ||
| # Build financial reports with Intelligence sheets |
There was a problem hiding this comment.
The front matter is missing the required ai-usage entry. Add ai-usage: ai-assisted (or ai-usage: ai-generated, as appropriate) to comply with the repo’s AI disclosure guidance for substantially modified Markdown content.
There was a problem hiding this comment.
Was this content modified by AI tools? If so, please implement this Copilot suggestion. If not, you can just resolve it.
| @@ -45,6 +45,9 @@ This article provides a basic overview of how to create financial reports with I | |||
|
|
|||
| Out-of-the-box report templates provide a quick starting point for creating reports. They reduce the time and effort required to build reports from scratch. | |||
There was a problem hiding this comment.
Terminology is inconsistent in this section: the paragraph uses “Out-of-the-box report templates” while the new TIP says “built-in templates.” Pick one term and use it consistently (and align with any established term for the feature in the UI).
| Out-of-the-box report templates provide a quick starting point for creating reports. They reduce the time and effort required to build reports from scratch. | |
| Built-in templates provide a quick starting point for creating reports. They reduce the time and effort required to build reports from scratch. |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
| --- | ||
|
|
||
| # Financial data reporting in Intelligence sheets | ||
| # Build financial reports with Intelligence sheets |
There was a problem hiding this comment.
Was this content modified by AI tools? If so, please implement this Copilot suggestion. If not, you can just resolve it.
Updated the description of Intelligence sheets to clarify their features for presenting financial data.
|
Learn Build status updates of commit c9cad34: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
Learn Build status updates of commit 3568134: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
#sign-off |
|
🚫 Blocking issues that must be resolved before this PR can be merged: docs/iq/plan/media/intelligence-how-to-build-financial-reports/header-footer.png
|
|
#hold-off |
|
@baanders @v-dirichards |
|
@deepthy-dileep So the bar was not added to the screenshot to obscure sensitive information, but rather is included on the captured screen as part of the footer. Is that correct? |
|
Yes Bailey, that's right. |
|
Hi @v-dirichards, hoping we can proceed with merge now that we have confirmation that bar was not censoring sensitive information. #sign-off |
Thank you for contributing to Microsoft Fabric documentation
Fill out these items before submitting your pull request:
If you are working internally at Microsoft:
Provide a link to an Azure DevOps Boards work item that tracks this feature/update.
Who is your primary Skilling team contact? @mention them individually tag them and let them review the PR before signing off.
For internal Microsoft contributors, check off these quality control items as you go
1. Check the Acrolinx report: Make sure your Acrolinx Total score is above 80 minimum (higher is better) and with no spelling issues. Acrolinx ensures we are providing consistent terminology and using an appropriate voice and tone, and helps with localization.
2. Successful build with no warnings or suggestions: Review the build status to make sure all files are green (Succeeded).
3. Preview the pages:: Click each Preview URL link to view the rendered HTML pages on the review.learn.microsoft.com site to check the formatting and alignment of the page. Scan the page for overall formatting, and look at the parts you edited in detail.
4. Check the Table of Contents: If you are adding a new markdown file, make sure it is linked from the table of contents.
5. #sign-off to request PR review and merge: Once the pull request is finalized and ready to be merged, indicate so by typing
#sign-offin a new comment in the Pull Request. If you need to cancel that sign-off, type#hold-offinstead. Signing off means the document can be published at any time. Note, this is a formatting and standards review, not a technical review.Merge and publish
#sign-off, there is a separate PR Review team that will review the PR and describe any necessary feedback before merging.#sign-offagain. The PR Review team reviews and merges the pull request into the specified branch (usually the main branch or a release- branch).