Disable taxes if we need to disconnect a previous integration first #44736

lakchote · 2024-07-02T14:47:50Z

Details

We were disabling taxes when connecting to QBO if the user disconnected from his previous integration first

We weren't disabling taxes if the user connected to QBO by using the disconnect modal

Fixed Issues

$
PROPOSAL:

Related to #42466 and specifically #42466 (comment)

Tests

Verify that no errors appear in the JS console

Sync to Xero by going to the Accounting menu item in the LHN (need Accounting and Xero beta)
Enable taxes import by going to Import > Taxes
You should still see the Taxes in the LHN populated with Xero data
Connect to QBO by clicking on Other Integrations > QBO
Categories remain enabled, the values are replaced with imported chart of accounts from QBO
Tags remain enabled, the values are replaced with imported classes and customers & projects from QBO (if they don't have any of those values in QBO, the page is just blank but enabled)
Taxes are disabled, because Taxes aren't imported by default when connecting to QBO.
Verify that the Taxes menu item in the LHN disappears correctly.

Offline tests

NA

QA Steps

Verify that no errors appear in the JS console
Same as in tests

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

melvin-bot · 2024-07-02T14:48:21Z

@jasperhuangg 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]

jasperhuangg · 2024-07-03T19:03:38Z

src/components/ConnectToQuickbooksOnlineButton/index.tsx

+                        // Since QBO doesn't support Taxes, we should disable them from the LHN when connecting to QBO
+                        PolicyAction.enablePolicyTaxes(policyID, false);


NAB: The name of this command is misleading IMO and it should be renamed to togglePolicyTaxes since you pass false to it to disable policy taxes.

jasperhuangg · 2024-07-03T19:03:59Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

OSBotify · 2024-07-03T19:12:10Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2024-07-03T20:04:27Z

🚀 Deployed to staging by https://github.com/jasperhuangg in version: 9.0.4-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2024-07-04T22:16:54Z

🚀 Cherry-picked to staging by https://github.com/tgolen in version: 9.0.4-5 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

kavimuru · 2024-07-04T23:56:37Z

Failing #42466 in android and iOS
https://platform.applause.com/services/links/v1/external/ba7bb8e5c13fdfc31a8b72f118107dd190e5eeaa75834ab6898c298166b0e03c
https://platform.applause.com/services/links/v1/external/fa6019689d8c186b1a28f7c8ed93db7bd9d2ac0134494f6f533f9deaaa53eac0

mountiny · 2024-07-05T11:59:05Z

@lakchote seems like this did not pass the QA, noting so its not missed

lakchote · 2024-07-08T10:59:10Z

@lakchote seems like this did not pass the QA, noting so its not missed

Thanks for the ping. I've addressed a fix here.

OSBotify · 2024-07-10T11:06:11Z

🚀 Deployed to production by https://github.com/Julesssss in version: 9.0.5-13 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2024-07-15T20:24:44Z

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.6-8 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

disable taxes if we need to disconnect a previous integration first

57d92ca

lakchote self-assigned this Jul 2, 2024

lakchote requested a review from a team as a code owner July 2, 2024 14:47

melvin-bot bot requested review from jasperhuangg and removed request for a team July 2, 2024 14:48

lakchote mentioned this pull request Jul 2, 2024

[HOLD for payment 2024-06-11] [Wave Collect] [Xero] Disable Taxes when connecting to QBO that doesn't enable Taxes by default #42466

Closed

fix prettier

3ef6702

jasperhuangg approved these changes Jul 3, 2024

View reviewed changes

jasperhuangg merged commit 979466d into main Jul 3, 2024
14 of 15 checks passed

jasperhuangg deleted the lucien/fix-qbo-taxes-lhn branch July 3, 2024 19:04

github-actions bot mentioned this pull request Jul 3, 2024

Deploy Checklist: New Expensify 2024-07-03 #44782

Closed

lakchote mentioned this pull request Jul 8, 2024

Fix disconnect QBO on native devices #44952

Merged

50 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Disable taxes if we need to disconnect a previous integration first #44736

Disable taxes if we need to disconnect a previous integration first #44736

lakchote commented Jul 2, 2024

melvin-bot bot commented Jul 2, 2024

jasperhuangg Jul 3, 2024

jasperhuangg commented Jul 3, 2024

OSBotify commented Jul 3, 2024

OSBotify commented Jul 3, 2024

OSBotify commented Jul 4, 2024

kavimuru commented Jul 4, 2024

mountiny commented Jul 5, 2024

lakchote commented Jul 8, 2024

OSBotify commented Jul 10, 2024

OSBotify commented Jul 15, 2024

		// Since QBO doesn't support Taxes, we should disable them from the LHN when connecting to QBO
		PolicyAction.enablePolicyTaxes(policyID, false);

Disable taxes if we need to disconnect a previous integration first #44736

Disable taxes if we need to disconnect a previous integration first #44736

Conversation

lakchote commented Jul 2, 2024

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Jul 2, 2024

jasperhuangg Jul 3, 2024

Choose a reason for hiding this comment

jasperhuangg commented Jul 3, 2024

Reviewer Checklist

Screenshots/Videos

OSBotify commented Jul 3, 2024

OSBotify commented Jul 3, 2024

OSBotify commented Jul 4, 2024

kavimuru commented Jul 4, 2024

mountiny commented Jul 5, 2024

lakchote commented Jul 8, 2024

OSBotify commented Jul 10, 2024

OSBotify commented Jul 15, 2024