Closed IuliiaHerets closed 1 month ago
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.
We think that this bug might be related to #wave-control
@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
Edited by proposal-police: This proposal was edited at 2024-09-26 02:19:00 UTC.
NetSuite - "Can't connect to NetSuite" message appears after connecting
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 (https://github.com/Expensify/App/pull/47059). However, this logic is redundant since we already have a condition to check wrong credentials right before this block here:
https://github.com/Expensify/App/blob/3488695033b5903198aeabbb87253c63716de5e8/src/pages/workspace/accounting/utils.tsx#L260
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
.
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.
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.
How do I get the NetSuite credentials?
Checking if we have test credentials
Thank you!
Job added to Upwork: https://www.upwork.com/jobs/~021840815188552877987
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Ollyws (External
)
@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?
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
Triggered auto assignment to @francoisl, see https://stackoverflow.com/c/expensify/questions/7972 for more details.
Reviewing
label has been removed, please complete the "BugZero Checklist".
The solution for this issue has been :rocket: deployed to production :rocket: in version 9.0.45-4 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2024-10-14. :confetti_ball:
For reference, here are some details about the assignees on this issue:
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:
Payment summary:
BugZero Checklist:
- [x] The PR that introduced the bug has been identified. Link to the PR:
https://github.com/Expensify/App/pull/47059
- [x] 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:
https://github.com/Expensify/App/pull/47059#discussion_r1799884665
- [x] 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:
N/A
- [x] Determine if we should create a regression test for this bug.
Yes.
- [x] 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.
Regression Test Proposal
1. Login with any account.
2. Create a new WS.
3. Go to that workspace setting => More Features => Enable Accounting feature.
4. Go to Accounting, click NetSuite.
5. Enter NetSuite credentials.
6. Verify you can connect with NetSuite without any issue.
Do we agree ๐ or ๐
Requested in ND.
$250 approved for @Ollyws
$250 approved for @hungvu193
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: https://github.com/Expensify/App/pull/48918 Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
There shouldn't be any error messages.
Actual Result:
"Can't connect to NetSuite" message appears after connecting.
Workaround:
Unknown
Platforms:
Screenshots/Videos
https://github.com/user-attachments/assets/c94288c5-8c86-4897-b95d-f54c3a588cf8
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @Ollyws