[HOLD for payment 2024-10-14] [$250] NetSuite - "Can't connect to NetSuite" message appears after connecting

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.0.40-0
Reproducible in staging?: Y
Reproducible in production?: Y
Issue was found when executing this PR: #48918
Issue reported by: Applause Internal Team

Action Performed:

1. Navigate to https://staging.new.expensify.com/
2. Log in with a new Gmail account
3. Click on FAB - New workspace
4. Enable "Accounting" in the "More features" page.
5. Navigate to "Accounting"
6. Connect to NetSuite and upgrade the workspace to Control when asked
7. Wait for the sync to finish

Expected Result:

There shouldn't be any error messages.

Actual Result:

"Can't connect to NetSuite" message appears after connecting.

Workaround:

Unknown

Platforms:

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6615201_1727293693434.bandicam_2024-09-25_21-41-33-738.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021840815188552877987
• Upwork Job ID: 1840815188552877987
• Last Price Increase: 2024-09-30

Issue Owner

Current Issue Owner: @sonialiap

[melvin-bot]

Triggered auto assignment to @sonialiap (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[IuliiaHerets]

We think that this bug might be related to #wave-control

[IuliiaHerets]

@sonialiap FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[hungvu193]

Edited by proposal-police: This proposal was edited at 2024-09-26 02:19:00 UTC.

Proposal

Please re-state the problem that we are trying to solve in this issue.

NetSuite - "Can't connect to NetSuite" message appears after connecting

What is the root cause of that problem?

In here, we're showing the error if policy?.connections?.[CONST.POLICY.CONNECTIONS.NAME.NETSUITE]?.verified === false, this logic was added to show the authentication error if the user enters the wrong credentials in this PR (#47059). However, this logic is redundant since we already have a condition to check wrong credentials right before this block here:

App/src/pages/workspace/accounting/utils.tsx

Line 260 in 3488695

if (isAuthenticationError(policy, connectionName)) {

Because of that, when 2 Pusher events arrived later. We will briefly see the error because the connection object contains verified: false and the other contains verified: true.

What changes do you think we should make in order to solve the problem?

Remove policy?.connections?.[CONST.POLICY.CONNECTIONS.NAME.NETSUITE]?.verified === false from this condition since it's redundant.

After that, we also need to update hasSynchronizationErrorMessage to handle the logic of showing RBR as well.

What alternative solutions did you explore? (Optional)

As I checked, the response of NetSuite connection is almost the same as other connections, we can consider removing this condition and handling Netsuite like other connections.
We also need to update hasSynchronizationErrorMessage to handle the logic of showing RBR as well.

[layacat]

How do I get the NetSuite credentials?

[sonialiap]

Checking if we have test credentials

[layacat]

Thank you!

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021840815188552877987

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @Ollyws (External)

[mallenexpensify]

@layacat, for NetSuite, and some other accounting integrations, we currently only allow our expert Contributor+ team to work on them.

@Ollyws , can you review @hungvu193 's proposal above?

[Ollyws]

As I checked, the response of NetSuite connection is almost the same as other connections, we can consider removing this condition and handling Netsuite like other connections.

This was my finding too and it works fine without, what exactly was supposed to be unconventional about the lastSync object for Netsuite?

Let's move forward with @hungvu193's proposal.

🎀👀🎀 C+ reviewed

[melvin-bot]

Triggered auto assignment to @francoisl, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

[hungvu193]

@Ollyws PR is here 😄

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.45-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Fix error shows briefly while connecting NetSuite #50032

If no regressions arise, payment will be issued on 2024-10-14. 🎊

For reference, here are some details about the assignees on this issue:

• @Ollyws requires payment through NewDot Manual Requests
• @hungvu193 requires payment through NewDot Manual Requests

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@Ollyws / @hungvu193] The PR that introduced the bug has been identified. Link to the PR:
• [@Ollyws / @hungvu193] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
• [@Ollyws / @hungvu193] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
• [@Ollyws / @hungvu193] Determine if we should create a regression test for this bug.
• [@Ollyws / @hungvu193] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [@sonialiap] Link the GH issue for creating/updating the regression test once above steps have been agreed upon: