Conversation
|
@wyapams : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
@wyapams : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 886ce2f: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
|
#sign-off ready for sign off |
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @msmimart |
There was a problem hiding this comment.
Pull request overview
Updates the Real-Time Intelligence disaster recovery guidance for Graph Model/Queryset items in Fabric, replacing the prior Git-based recovery guidance with a step-by-step manual recreation flow aligned to the document’s capacity/workspace failover scenario.
Changes:
- Replaces Graph Model/Graph Queryset recovery text with a numbered procedure for rebuilding items in another region/capacity.
- Adds explicit steps for recreating the Graph Model, reconnecting lakehouse-based loading, and rebuilding the Graph Queryset queries/configurations.
| 1. Recreate the Graph Model item in C2.W2. Reconfigure the model definition, including entity types, relationship types, and property mappings, to match the original Graph Model. If a lakehouse was recovered in the previous step, connect it to the newly created Graph Model item. | ||
|
|
||
| 1. Reconfigure any data loading schedules or connections for the Graph Model in the new workspace. | ||
|
|
||
| 1. Recreate the Graph Queryset item in C2.W2. Manually reenter the queries and any saved query configurations from the original Graph Queryset. |
There was a problem hiding this comment.
Steps 4 and 6 instruct readers to recreate items specifically in "C2.W2", but steps 1–2 allow using any capacity/workspace in another region. Unless you explicitly constrain the procedure to the sample scenario, this is inconsistent and can confuse readers (or reference a workspace that doesn’t exist). Consider referring to “the new workspace you created in step 2 (for example, C2.W2)” or consistently using the sample-scenario phrasing throughout the steps.
| 1. Recreate the Graph Model item in C2.W2. Reconfigure the model definition, including entity types, relationship types, and property mappings, to match the original Graph Model. If a lakehouse was recovered in the previous step, connect it to the newly created Graph Model item. | |
| 1. Reconfigure any data loading schedules or connections for the Graph Model in the new workspace. | |
| 1. Recreate the Graph Queryset item in C2.W2. Manually reenter the queries and any saved query configurations from the original Graph Queryset. | |
| 1. Recreate the Graph Model item in the new workspace you created in step 2, for example, `C2.W2`. Reconfigure the model definition, including entity types, relationship types, and property mappings, to match the original Graph Model. If a lakehouse was recovered in the previous step, connect it to the newly created Graph Model item. | |
| 1. Reconfigure any data loading schedules or connections for the Graph Model in the new workspace. | |
| 1. Recreate the Graph Queryset item in the new workspace you created in step 2, for example, `C2.W2`. Manually reenter the queries and any saved query configurations from the original Graph Queryset. |
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.
https://dev.azure.com/powerbi/Fabric%20Graph/_workitems/edit/2055505
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).