[No QA] Add QuickBooks Desktop troubleshooting docs (New + Classic) #84815
[No QA] Add QuickBooks Desktop troubleshooting docs (New + Classic) #84815stephanieelliott merged 1 commit intomainfrom
Conversation
github-actions
bot
changed the title
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
|
||
| --- | ||
|
|
||
| # How to Fix the DESK03 Error |
There was a problem hiding this comment.
Heading level violation (AI Readiness): This uses # (H1) for a section heading, but the article already has an H1 title on line 8. HelpDot articles should have only one H1 (#). Use ## (H2) instead for section headings.
This pattern repeats across all New Expensify files in this PR -- every # How to Fix... and # FAQ heading uses H1 instead of H2. Please update all New Expensify articles to use ## How to Fix... and ## FAQ consistent with the Expensify Classic files in this same PR.
Affected files (representative list -- applies to all ~43 New Expensify articles):
- All files under
docs/articles/new-expensify/connections/quickbooks-desktop/Troubleshooting/
| # How to Fix the DESK03 Error | |
| ## How to Fix the DESK03 Error |
|
|
||
| --- | ||
|
|
||
| # FAQ |
There was a problem hiding this comment.
Heading level violation (AI Readiness): Same issue -- # FAQ should be ## FAQ since there is already an H1 title. This applies to the FAQ heading in every New Expensify article in this PR.
| # FAQ | |
| ## FAQ |
|
|
||
| --- | ||
|
|
||
| # How to Fix the DESK08 Error |
There was a problem hiding this comment.
Heading level violation (AI Readiness): Uses # (H1) for the "How to Fix" section. Should be ## How to Fix the DESK08 Error since the article title is already the H1. This pattern recurs in all New Expensify files.
| # How to Fix the DESK08 Error | |
| ## How to Fix the DESK08 Error |
| If you see the error: | ||
|
|
||
| DESK03: No data exchange required. |
There was a problem hiding this comment.
Readability violation: The error message text is displayed as plain paragraph text, making it hard to distinguish from the surrounding description. Error messages should be formatted as a blockquote or code block so they are visually distinct and scannable.
For example:
> DESK03: No data exchange required.
This pattern applies to all 100 files in this PR. Every error message string (e.g., DESK03: No data exchange required., DESK08: Unable to reach QuickBooks Desktop connection..., etc.) should use a blockquote (>) or inline code to set it apart from explanatory text.
| 2. Review each expense on the report. | ||
| 3. Check the **Description** field for unusual or special characters. | ||
| 4. Remove or replace any unsupported symbols. | ||
| 5. Click **Save**. |
There was a problem hiding this comment.
Expensify style violation: Per Expensify HelpDot conventions, the button label at the end of a save/update flow should be "Confirm" rather than "Save." Please verify whether the actual UI button says "Save" or "Confirm" and use the label that matches the product.
This pattern appears in multiple New Expensify files in this PR (DESK18, DESK33, DESK41, DESK88, DESK90, etc.) and in several Classic files (DESK44). If the product UI uses "Save," this can be kept; otherwise, update to "Confirm."
| 6. Open the **Export** tab. | ||
| 7. Change the export type for reimbursable or non-reimbursable expenses. | ||
| 8. Click **Save**. | ||
|
|
There was a problem hiding this comment.
Expensify style violation: Click **Save** -- per Expensify HelpDot conventions, the final button label in a configuration flow should be "Confirm" rather than "Save." Please verify the actual product UI label and use the matching term.
| 8. Click **Confirm**. |
| - The correct company file is not open. | ||
| - QuickBooks Web Connector (QBWC) is not running. | ||
| - The Web Connector is installed on a different machine than QuickBooks Desktop. | ||
| - The Web Connector does not have sufficient permissions to connect. |
There was a problem hiding this comment.
AI Readiness violation: Using ### (H3) heading level for "Step One: Confirm Both Applications Are Running." HelpDot articles should avoid heading levels deeper than ##. These step headings could be restructured as numbered sections under the ## How to Fix heading, or promoted to ## level.
This pattern recurs across most Classic files (DESK08, DESK29, DESK53, DESK66, DESK81, DESK83) where multi-step fixes use ### Step One/Two/Three headings. Consider restructuring to avoid ### depth -- for example, using a single ## How to Fix section with numbered sub-steps, or promoting each step to ## level.
|
|
||
| # DESK52 Sync Error in QuickBooks Desktop Web Connector | ||
|
|
||
| If you see the error: |
There was a problem hiding this comment.
Terminology violation (Expensify style): The error message text references "user" (Unable to set user as 'preferred exporter'). While this is likely the literal error message text from the product (which is acceptable to quote verbatim), ensure the surrounding article copy uses "member" instead of "user" per Expensify terminology standards. The rest of this article correctly uses "member" -- just flagging for awareness.
| @@ -0,0 +1,94 @@ | |||
| --- | |||
There was a problem hiding this comment.
AI Readiness / Structure observation: This FAQ file uses a different heading structure than the per-error FAQ sections. The top-level heading is # QuickBooks Desktop FAQ which is correct, but the individual questions use ## headings (which is correct for FAQ questions). However, the sub-sections under each question use ### headings (lines 22, 43, 55, 71). Consider whether the ### How to Resolve... sub-sections could be restructured to avoid ### depth -- for example, as part of the ## question's answer text rather than a separate sub-heading.
|
|
||
| --- | ||
|
|
||
| # FAQ |
There was a problem hiding this comment.
Heading level violation (AI Readiness): # FAQ should be ## FAQ -- same H1 issue as the # How to Fix heading noted earlier. Only one H1 per article.
| # FAQ | |
| ## FAQ |
| If you see the error: | ||
|
|
||
| DESK03 Error: No data exchange required. |
There was a problem hiding this comment.
Readability violation: The error message DESK03 Error: No data exchange required. is rendered as plain paragraph text. It should be visually distinguished from surrounding copy using a blockquote or inline code block. For example:
> DESK03 Error: No data exchange required.
This same formatting issue applies to every error message string in all New Expensify files in this PR.
|
|
||
| ## Recategorize Flagged Expenses | ||
|
|
||
| 1. Open the report that failed to export. |
There was a problem hiding this comment.
Expensify style violation: Click **Save** -- verify whether the actual New Expensify UI button label is "Save" or "Confirm." Expensify style guidelines specify using "Confirm" at the end of flows. If the product uses a different label, match it exactly.
This same concern applies to DESK18, DESK41, DESK88, and DESK90 New Expensify export error files.
HelpDot Documentation ReviewOverall AssessmentThis PR adds 112 new markdown documentation files covering QuickBooks Desktop (QBD) troubleshooting error codes (DESK03 through DESK99) across both Expensify Classic and New Expensify. The documentation is well-structured, consistently formatted, and covers a comprehensive range of error scenarios. The writing is clear, action-oriented, and follows a highly uniform template pattern. The author has done an excellent job establishing a repeatable structure for error documentation at scale. Scores Summary
Key FindingsHeading hierarchy issue across all files: Every file uses Significant content duplication within each platform: Many DESK error codes appear in multiple subcategories (Authentication-and-Login-errors, Connection-errors, Export-Errors, Sync-Errors) with byte-for-byte identical content. For example, in Classic, New Expensify articles are meaningfully different from Classic counterparts: The New Expensify versions are not just copies -- they use different navigation paths (e.g., "Click the three-dot icon next to the QuickBooks Desktop connection"), different title patterns ("in QuickBooks Desktop Integration" vs. "in QuickBooks Desktop Web Connector"), and slightly different structural patterns (e.g., using Error message text is not formatted as code or blockquote: Error messages like "DESK08: Unable to reach QuickBooks Desktop connection..." are displayed as plain text. Formatting them in a blockquote or code block would improve visual distinction and scannability. Consistent and helpful FAQ sections: Every article includes relevant FAQ questions that address common user concerns (data loss, applicability to QuickBooks Online, etc.). This is a strong pattern. Strong template consistency: The "Why it happens / How to fix / FAQ" structure is applied uniformly and provides a predictable reading experience. Recommendations
Files ReviewedExpensify Classic (56 files):
New Expensify (56 files):
Note: Detailed line-by-line feedback has been provided as inline comments. |
|
|
||
| --- | ||
|
|
||
| # How to Fix the DESK44 Error |
There was a problem hiding this comment.
Heading level violation (AI Readiness): # How to Fix the DESK44 Error uses H1, but the article already has an H1 title. Change to ##.
| # How to Fix the DESK44 Error | |
| ## How to Fix the DESK44 Error |
| 3. Click **Accounting**. | ||
| 4. Click **Export**. | ||
| 5. Change the export type for either **Reimbursable** or **Non-reimbursable** expenses. | ||
| 6. Click **Save**. |
There was a problem hiding this comment.
Expensify style violation: Click **Save** -- per Expensify conventions, the final button in a configuration flow should use "Confirm" rather than "Save." Please verify the actual product UI label.
| 6. Click **Save**. | |
| 6. Click **Confirm**. |
| ### Step One: Remove the Existing Web Connector Authorization | ||
|
|
||
| 1. In QuickBooks Desktop, go to **Edit** > **Preferences**. | ||
| 2. Select **Integrated Applications**. |
There was a problem hiding this comment.
Expensify style violation: Step 3 says Click **Continue**. Per Expensify HelpDot conventions, the button label "Continue" should be "Next" when advancing through a multi-step flow. Please verify the actual product UI label and update accordingly. This pattern appears in the DESK81 and DESK83 reauthorization steps across both Classic and New Expensify files.
| 2. Select **Integrated Applications**. | |
| 3. Click **Next**. |
…y Classic) - New Expensify: articles for Auth, Connection, Export, Sync errors, FAQ, plus root Configure/Connect/Troubleshooting. Removed placeholder files. - Expensify Classic: same structure and error articles. - Hub pages for both already exist on main. Part of Integration Errors Revamp (splitting PR #83106).
stephanieelliott
force-pushed
the
helpsite-quickbooks-desktop-new-and-classic
branch
from
80e4b93 to
603088f
Compare
stephanieelliott
deleted the
helpsite-quickbooks-desktop-new-and-classic
branch
|
@stephanieelliott looks like this was merged without a test passing. Please add a note explaining why this was done and remove the |
|
🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.3.36-0 🚀
|
|
🚀 Deployed to production by https://github.com/luacmartins in version: 9.3.36-10 🚀
|
3 participants
Master project issue https://github.com/Expensify/Expensify/issues/469226
Breaking main PR into smaller batches: #83106
Creates .MD files for QBD Integration error messages (New + Classic Expensify)