[$250] NetSuite - Inconclusive use of spaces before and after a backslash

[izarutskaya]

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.21-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: #47091
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

1. Open the app
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
8. Navigate to Accounting - Import

Expected Result:

All of the options should follow a similar syntax: "text/text" or "text / text".

Actual Result:

Inconclusive use of spaces before and after a backslash. One option is "Custom segments/records", the other is "Customers / projects".

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

Bug6573587_1723784432596.bandicam_2024-08-16_06-46-56-545.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01ad3e945fffc220c0
• Upwork Job ID: 1825680410861600909
• Last Price Increase: 2024-08-19
• Automatic offers:
• shubham1206agra | Contributor | 103678598

Issue Owner

Current Issue Owner: @Ollyws

[melvin-bot]

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

[izarutskaya]

We think this issue might be related to the #wave-control

[daledah]

Proposal

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

Inconclusive use of spaces before and after a backslash. One option is "Custom segments/records", the other is "Customers / projects".

What is the root cause of that problem?

Copy errors.

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

Modify these copy following same standard. Seems like all the segment/record copies have that same inconsistency.

App/src/languages/en.ts

Line 2578 in fc5cf59

title: 'Custom segments/records',

App/src/languages/en.ts

Line 2579 in fc5cf59

addText: 'Add custom segment/record',

App/src/languages/en.ts

Line 2583 in fc5cf59

helpText: ' on configuring custom segments/records.',

[melvin-bot]

@VictoriaExpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

[VictoriaExpensify]

I agree that this should be consistent. A low priority but we should fix it

[melvin-bot]

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

[melvin-bot]

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

[Ollyws]

I need Netsuite credentials before testing this one so I have requested in slack.

[shubham1206agra]

As discussed internally, I will pick this up. And @Ollyws will be the reviewer.

[melvin-bot]

@Ollyws, @VictoriaExpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

📣 @shubham1206agra 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

[melvin-bot]

@Ollyws, @VictoriaExpensify, @shubham1206agra Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@Ollyws @VictoriaExpensify @shubham1206agra this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[Ollyws]

Deployed to production 4 days ago.

[Ollyws]

@VictoriaExpensify This one's due for payment today, thanks.

[Ollyws]

this one is getting sorted in #46540 so I think we can close this.

[melvin-bot]

@Ollyws, @VictoriaExpensify, @shubham1206agra Eep! 4 days overdue now. Issues have feelings too...

[VictoriaExpensify]

Closing as the issue was fixed elsewhere