[$250] Set `syncCustomLists` and `syncCustomSegments` to true in the NetSuite config when a user has one or more set in their configuration

[yuwenmemon]

Problem

One thing we forgot about in the NetSuite project when building the integration configuration in New Expensify is that we need to set two boolean style configs whenever we have a Custom Segment or Custom List that we're importing.

This create issues when importing and exporting those segments and/or lists

Solution

1. If we ever update the NetSuite configuration for a workspace to add a Custom Segment such that there is > 1 entry insyncOptions.customSegmentsthen we should setsyncOptions.syncCustomSegmentstotrue`
2. If we ever update the NetSuite configuration for a workspace to add a Custom List such that there is > 1 entry in syncOptions.customLists then we should set syncOptions.syncCustomLists to true
3. If the customSegments or customLists array is ever empty when saving a configuration (i.e. we remove the last Custom Segment or list) we should set syncCustomLists / syncCustomSegments to false

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021836280909533854916
• Upwork Job ID: 1836280909533854916
• Last Price Increase: 2024-09-18

Issue Owner

Current Issue Owner: @rushatgabhane

[melvin-bot[bot]]

Triggered auto assignment to @OfstadC (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.

[yuwenmemon]

@mananjadhav @shubham1206agra Putting this under your radar in case you wanted to knock it out real quick

[melvin-bot[bot]]

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

[melvin-bot[bot]]

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

[shubham1206agra]

@yuwenmemon Can you tell me the use of this? Cause we don't use it anywhere.

[yuwenmemon]

It's used in the back-end to control what data gets imported and exported. But hmmmm... now that you mention it, we don't use it anywhere in the client itself... So I'll actually handle this internally in the API - thanks for the gut check! 🙇🏽