[No QA] Add QBWC1039 troubleshooting to QuickBooks Desktop FAQ#90785
[No QA] Add QBWC1039 troubleshooting to QuickBooks Desktop FAQ#90785MelvinBot wants to merge 6 commits into
Conversation
Add a new section covering the QBWC1039 "Unique OwnerID/FileID pair value required" error, including steps to remove the existing Owner ID using the CP3 tool, re-add the Expensify application, and guidance for hosted environments like Rightworks. Co-authored-by: Ted Harris <twisterdotcom@users.noreply.github.com>
|
@MelvinBot what's the deal with the spell check fails? Can we fix those? |
twisterdotcom
changed the title
|
A preview of your ExpensifyHelp changes have been deployed to https://4a8f8421.helpdot.pages.dev ⚡️ Updated articles: |
Co-authored-by: Ted Harris <twisterdotcom@users.noreply.github.com>
|
Fixed the spellcheck failure — added |
Co-authored-by: Ted Harris <twisterdotcom@users.noreply.github.com>
…ub.com/Expensify/App into claude-addQBWC1039TroubleshootingToFAQ Co-authored-by: Ted Harris <twisterdotcom@users.noreply.github.com>
Co-authored-by: Ted Harris <twisterdotcom@users.noreply.github.com>
|
Fixed the failing spellcheck: added |
|
MelvinBot has made 5 consecutive commits trying to fix CI failures. Automatic CI fix dispatches are now paused for this PR. Next steps: A human should review the recent commits and resolve the conflicting CI errors manually. |
1 similar comment
|
MelvinBot has made 5 consecutive commits trying to fix CI failures. Automatic CI fix dispatches are now paused for this PR. Next steps: A human should review the recent commits and resolve the conflicting CI errors manually. |
|
The only failing check is PR Author Checklist — this is a manual checklist that requires the PR author/assignee to complete, not something that can be fixed with a code change. All other checks pass (ESLint, Prettier, builds, spellcheck, etc.). The Action needed: Complete the PR Author Checklist items to resolve the failure. |
Concierge reviewer checklist:
For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member? |
|
@danieldoglas @greg-schroeder One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button] |
HelpDot Documentation ReviewOverall AssessmentThis PR adds a new FAQ entry for the QBWC1039 error to the QuickBooks Desktop FAQ article. The content is thorough, well-organized, and covers both standard and hosted-environment scenarios. The YAML metadata updates are appropriate. However, the new content introduces heading depth violations that conflict with the governance rules, and there is one cross-linking placement issue. Scores Summary
Key Findings
Recommendations
Files Reviewed
Note: This review covers only the proposed changes in the PR diff, not pre-existing content in the file. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
|
||
| This means the Expensify application is already registered in QuickBooks Web Connector and a second registration is being attempted. QuickBooks requires each application to have a unique OwnerID/FileID pair. If one already exists, the new registration is rejected. | ||
|
|
||
| ### How to Fix the QBWC1039 Error |
There was a problem hiding this comment.
Heading depth violation: Only # and ## headings are allowed per HELP_AUTHORING_GUIDELINES.md Section 4. This ### heading should be promoted to ## and rewritten as a task-based heading starting with an action verb or question word.
| ### How to Fix the QBWC1039 Error | |
| ## How to fix the QBWC1039 error |
There was a problem hiding this comment.
Fixed — promoted to ## with the suggested task-based heading.
|
|
||
| ### How to Fix the QBWC1039 Error | ||
|
|
||
| #### Step One: Remove the Existing Owner ID Using the CP3 Tool |
There was a problem hiding this comment.
Heading depth violation + generic heading: #### headings are not allowed — only # and ## are permitted (HELP_AUTHORING_GUIDELINES.md Section 4). Additionally, "Step One" is a generic heading pattern (Section 2 forbids headings like "Step 1"). Promote to ## with a task-based heading.
| #### Step One: Remove the Existing Owner ID Using the CP3 Tool | |
| ## How to remove the existing Owner ID using the CP3 tool |
There was a problem hiding this comment.
Fixed — promoted to ## with the suggested task-based heading.
| 8. You should see a confirmation that the Owner ID was removed. Select **OK**. | ||
| 9. Exit and reopen both **QuickBooks Desktop** and **Web Connector**. | ||
|
|
||
| #### Step Two: Re-add the Expensify Application |
There was a problem hiding this comment.
Heading depth violation + generic heading: #### headings are not allowed — only # and ## are permitted. "Step Two" is also a generic heading pattern. Promote to ## with a task-based heading.
| #### Step Two: Re-add the Expensify Application | |
| ## How to re-add the Expensify application in Web Connector |
There was a problem hiding this comment.
Fixed — promoted to ## with the suggested task-based heading.
|
|
||
| Return to Expensify and allow the Workspace to finish syncing. | ||
|
|
||
| #### If QuickBooks Desktop Is Hosted (e.g., Rightworks) |
There was a problem hiding this comment.
Heading depth violation + non-task-based heading: #### headings are not allowed — only # and ## are permitted. The heading must also start with an action verb or question word (How, What, Where, Who, Why, When). Promote to ## and rewrite.
| #### If QuickBooks Desktop Is Hosted (e.g., Rightworks) | |
| ## How to fix the QBWC1039 error when QuickBooks Desktop is hosted (e.g., Rightworks) |
There was a problem hiding this comment.
Fixed — promoted to ## with the suggested task-based heading.
| #### Step One: Remove the Existing Owner ID Using the CP3 Tool | ||
|
|
||
| 1. Open **QuickBooks Desktop**. | ||
| 2. Download the [CP3 tool from Intuit](https://http-download.intuit.com/http.intuit/CP3Tool/QBWC_CP3Tool.exe), then select **Open**. |
There was a problem hiding this comment.
Link placement violation: Per HELP_AUTHORING_GUIDELINES.md Section 7, links must not be placed inside numbered step instructions. Move the CP3 tool download link to an explanatory paragraph before or after the numbered steps.
Also note this is a full external URL — the cross-linking standards say to use relative links only, though this rule is primarily intended for internal HelpDot cross-links, so the external URL is acceptable here.
There was a problem hiding this comment.
Fixed — moved the CP3 tool download link to an explanatory paragraph before the numbered steps.
|
@MelvinBot give it a go at addressing the review comments, please |
- Promote ### and #### headings to ## (only # and ## allowed) - Replace generic "Step One/Two" headings with task-based headings - Move CP3 tool download link out of numbered steps into explanatory paragraph - Update cross-reference from "Step Two" to new heading name Co-authored-by: Ted Harris <twisterdotcom@users.noreply.github.com>
|
Addressed all 5 review comments:
|
|
@carlosmiceli Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button] |
3 participants
Explanation of Change
Adds a new FAQ section to the QuickBooks Desktop FAQ doc covering the QBWC1039: Unique OwnerID/FileID pair value required error. This error occurs when the Expensify application is already registered in QuickBooks Web Connector and a second registration is attempted.
The new section includes:
Fixed Issues
https://stackoverflowteams.com/c/expensify/questions/22685 is only in SO
Tests
N/A — documentation-only change.
Offline tests
N/A — documentation-only change.
QA Steps
N/A — documentation-only change.
PR Author Checklist
### Fixed Issuessection aboveTestssectionOffline stepssectionQA stepssectiontoggleReportand notonIconClick)src/languages/*files and using the translation methodSTYLE.md) were followedAvatar, I verified the components usingAvatarare working as expected)StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))npm run compress-svg)Avataris modified, I verified thatAvataris working as expected in all cases)Designlabel and/or tagged@Expensify/designso the design team can review the changes.ScrollViewcomponent to make it scrollable when more elements are added to the page.mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps.Screenshots/Videos
Android: Native
N/A — documentation-only change.
Android: mWeb Chrome
N/A — documentation-only change.
iOS: Native
N/A — documentation-only change.
iOS: mWeb Safari
N/A — documentation-only change.
MacOS: Chrome / Safari
N/A — documentation-only change.