Repository navigation
[No QA] Update NS0068 NetSuite export error help articles - #104037
Conversation
Co-authored-by: Yuwen Memon <[email protected]>
This comment has been minimized.
This comment has been minimized.
Product reviewer checklist:
For more detailed instructions on completing this checklist, see How do I review a HelpDot PR? |
|
@JmillsExpensify 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] |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| internalScope: Audience is Workspace Admins using the NetSuite integration. Covers resolving the NS0068 export error caused by the Created From field not being visible on NetSuite transaction forms. Does not cover role permission or token configuration issues. | ||
| description: Learn what the NS0068 export error means and how to configure the Created From field (custbody_createdfrom_expensify) in NetSuite so Expensify can set it during export. | ||
| keywords: NS0068, NetSuite Created From field error, custbody_createdfrom_expensify, permission to set Created From NetSuite, Transaction Body Fields NetSuite, transaction form visibility NetSuite, Expensify Connect bundle, Expensify Card journal entry error, Expensify NetSuite integration, Workspace Admin | ||
| internalScope: Audience is Workspace Admins using the NetSuite integration. Covers resolving the NS0068 export error caused by the Created From field (custbody_createdfrom_expensify) not applying to the export record type, being hidden on the preferred form, not being editable by the Expensify role, or missing from NetSuite. Does not cover token configuration issues. |
There was a problem hiding this comment.
Terminology/casing: Use lowercase "workspace admins" in running text. Roles are only capitalized when quoting a UI label (per HELPSITE_NAMING_CONVENTIONS.md, Roles).
| Follow the steps below to check the field setup, form visibility, and role access in NetSuite. | ||
|
|
||
| --- | ||
|
|
There was a problem hiding this comment.
Heading rule: ## headings must use sentence case and be task-based (start with an action verb or question word). Rework to something like ## How to check the Created From field settings in NetSuite (per HELP_AUTHORING_GUIDELINES.md Section 2).
| 2. Go to **Customization > Lists, Records, & Fields > Transaction Body Fields**. | ||
| 3. Open the field with the ID **custbody_createdfrom_expensify**. | ||
| 4. On the **Applies To** tab, confirm the field applies to the record type you're exporting to. | ||
| 5. On the **Access** tab, confirm the role used by the Expensify connection has **Edit** access to the field. |
There was a problem hiding this comment.
UI action verb: Use "Select Save" instead of "Click Save". Governance prohibits click/tap; use select for UI interactions (HELPSITE_NAMING_CONVENTIONS.md, Actions).
| 4. On the **Applies To** tab, confirm the field applies to the record type you're exporting to. | ||
| 5. On the **Access** tab, confirm the role used by the Expensify connection has **Edit** access to the field. | ||
| 6. Click **Save**. | ||
|
|
There was a problem hiding this comment.
Link formatting: Use a relative link, not a full https://help.expensify.com/... URL (HELP_AUTHORING_GUIDELINES.md Section 7: "Use relative links only. Do not use full URLs.").
| If you can't find **custbody_createdfrom_expensify**, [update the Expensify Connect bundle](https://help.expensify.com/articles/new-expensify/connections/netsuite/Update-Expensify-Connect-Bundle-in-NetSuite), or reinstall it, before continuing. | ||
|
|
||
| --- | ||
|
|
There was a problem hiding this comment.
Heading rule: ## headings must be sentence case and task-based (start with an action verb or question word), e.g. ## How to make the Created From field visible on the preferred form (HELP_AUTHORING_GUIDELINES.md Section 2).
| ## Make the Created From Field Visible on the Preferred Form | ||
|
|
||
| 1. Go to **Customization > Forms > Transaction Forms**. | ||
| 2. Locate the transaction form marked as **Preferred** for your export type. |
There was a problem hiding this comment.
UI action verb: Use "Select Edit" instead of "Click Edit" (HELPSITE_NAMING_CONVENTIONS.md: never use click/tap; use select).
| 2. Locate the transaction form marked as **Preferred** for your export type. | ||
| 3. Click **Edit**. | ||
| 4. Locate the **Created From** field. | ||
| 5. Ensure the field is marked as **Show**. |
There was a problem hiding this comment.
UI action verb: Use "Select Save" instead of "Click Save" (HELPSITE_NAMING_CONVENTIONS.md, Actions).
| 4. Confirm **Created From** is marked as **Show**. | ||
| 5. Click **Save**. | ||
| 1. Go to **Customization > Lists, Records, & Fields > Transaction Body Fields** and open **custbody_createdfrom_expensify**. | ||
| 2. On the **Applies To** tab, confirm the field applies to journal entries, then click **Save**. |
There was a problem hiding this comment.
UI action verb: Use "then select Save" instead of "then click Save" (HELPSITE_NAMING_CONVENTIONS.md: never use click/tap).
| 1. Go to **Customization > Lists, Records, & Fields > Transaction Body Fields** and open **custbody_createdfrom_expensify**. | ||
| 2. On the **Applies To** tab, confirm the field applies to journal entries, then click **Save**. | ||
| 3. Go to **Customization > Forms > Transaction Forms**. | ||
| 4. Click **Edit** next to the preferred journal entry form. |
There was a problem hiding this comment.
UI action verb: Use "Select Edit" instead of "Click Edit" (HELPSITE_NAMING_CONVENTIONS.md, Actions).
| 4. Click **Edit** next to the preferred journal entry form. | ||
| 5. Go to **Screen Fields > Main**. | ||
| 6. Confirm **Created From** is marked as **Show**. | ||
| 7. Click **Save**. |
There was a problem hiding this comment.
UI action verb: Use "Select Save" instead of "Click Save" (HELPSITE_NAMING_CONVENTIONS.md, Actions).
| internalScope: Audience is Workspace Admins using the NetSuite integration. Covers fixing the NS0068 export error caused by the Created From field not being visible on the preferred NetSuite form. Does not cover other NetSuite error codes. | ||
| description: Learn how to fix the NS0068 export error in NetSuite when Expensify can't set the Created From field (custbody_createdfrom_expensify) during export. | ||
| keywords: NS0068, NetSuite Created From field not visible, custbody_createdfrom_expensify, permission to set value Created From, Transaction Body Fields NetSuite, NetSuite transaction form visibility, Expensify Connect bundle, Expensify Card journal entry error, Expensify NetSuite export error, Workspace Admin | ||
| internalScope: Audience is Workspace Admins using the NetSuite integration. Covers fixing the NS0068 export error caused by the Created From field (custbody_createdfrom_expensify) not applying to the export record type, being hidden on the preferred form, not being editable by the Expensify role, or missing from NetSuite. Does not cover other NetSuite error codes. |
There was a problem hiding this comment.
Terminology/casing: Use lowercase "workspace admins" in running text. Roles are only capitalized when quoting a UI label (HELPSITE_NAMING_CONVENTIONS.md, Roles).
| @@ -29,6 +35,21 @@ Expensify must be able to write to the Created From field during export. | |||
|
|
|||
| ## How to Fix the NS0068 Export Error | |||
|
|
|||
There was a problem hiding this comment.
Heading rule: Avoid ### headings — only # and ## are allowed (HELP_AUTHORING_GUIDELINES.md Section 4/9). The heading must also be sentence case and task-based, e.g. ## How to check the Created From field settings.
|
|
||
| 1. Log in to **NetSuite** as an Administrator. | ||
| 2. Go to **Customization**. | ||
| 3. Select **Lists, Records, & Fields**. |
There was a problem hiding this comment.
UI action verb: Use "Select Transaction Body Fields" instead of "Click ...". Governance prohibits click/tap; use select for UI interactions (HELPSITE_NAMING_CONVENTIONS.md, Actions).
| 2. Confirm **custbody_createdfrom_expensify** applies to journal entries, using the steps in **Check the Created From Field Settings** above. | ||
| 3. Go to **Customization**. | ||
| 4. Select **Forms**. | ||
| 5. Click **Transaction Forms**. |
There was a problem hiding this comment.
UI action verb: Use "Select Transaction Forms" instead of "Click Transaction Forms" (HELPSITE_NAMING_CONVENTIONS.md: never use click/tap; use select).
| 3. Go to **Customization**. | ||
| 4. Select **Forms**. | ||
| 5. Click **Transaction Forms**. | ||
| 6. Click **Edit** next to the preferred **Journal Entry** form. |
There was a problem hiding this comment.
UI action verb: Use "Select Edit" instead of "Click Edit" (HELPSITE_NAMING_CONVENTIONS.md, Actions).
HelpDot Documentation ReviewOverall AssessmentThis PR updates both the New Expensify and Expensify Classic NS0068 NetSuite export error articles to match a new error message that names the Created From field ID ( Scores Summary
Key Findings
Recommendations
Files Reviewed
Note: Detailed line-by-line feedback has been provided as inline comments. |
|
A preview of your ExpensifyHelp changes have been deployed to https://4077b8d4.helpdot.pages.dev ⚡️ Updated articles: |
|
🚀 Deployed to staging by https://github.com/yuwenmemon in version: 9.5.13-0 🚀
|
|
🚀 Deployed to production by https://github.com/grgia in version: 9.5.13-6 🚀
Bundle Size Analysis (Sentry): |
4 participants
Explanation of Change
The NS0068 NetSuite export error message now names the Created From field ID (
custbody_createdfrom_expensify) and gives fuller fix steps. This PR updates the New Expensify and Expensify Classic NS0068 help articles to match.Both articles now:
A
cspell:ignorecomment covers the field ID, matching the existing pattern in the Update Expensify Connect bundle article.Fixed Issues
$
PROPOSAL:
Tests
// TODO: The human co-author must fill out the tests you ran before marking this PR as "ready for review"
// Please describe what tests you performed that validates your changed worked.
Offline tests
QA Steps
// TODO: These must be filled out, or the issue title must include "[No QA]."
// TODO: The human co-author must fill out the QA tests you ran before marking this PR as "ready for review".
// Please describe what QA needs to do to validate your changes and what areas do they need to test for regressions.
PR Author Checklist
### Fixed Issuessection aboveTestssectionOffline stepssectionQA stepssectionAvatar, I verified the components usingAvatarare working as expected)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.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
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari