Best Of

Thanks for the clarification, @Glaced999991,

The Contact has two company joins, "Company (Primary)" and "Company".

The "Company (Primary)" is the one that appears in the Contact Header (Company) field.

All other Companies to which the Contact is attached are under the "Company" (not Parent) join.

You won't be able to show the Contact in a custom field natively within a "Company XYZ Estimate" because a Contact can be attached to multiple such Customers. This might have worked if the Contact had a 1:1 relationship with non-Parent Customers.

Hey @Gino Matthys,

There is a risk that the upgrade will impact the E-invoicing Integration.

NetSuite specifically mentions the following in the FAQ:

If you use any third-party integrations, particularly those that involve the creation or update of taxable transactions, please check with your vendors to ensure these integrations are compatible with SuiteTax.

Note that you can reschedule the upgrade to a later date if you need more time to review it and its impact on the integration.

Hey @JM Benitez,

Most probably, the issue is with the "Shipping Label PDF/XML". Did you check what address the label is pointing to? You should be able to update it to print the correct address.

Hi @Dext3r,

You can try creating this using SuiteAnalytics Dataset.

Criteria:
*Type: Purchase Order
*Transaction Line: Item [your items]

Results:
*Transaction
*Transaction Line: Item
*Created From = Transaction Line > Related Transactions - Previous > Transaction
*Created From: Shipping Cost = Transaction Line > Related Transactions - Previous > Transaction > Shipment > Shipping Rate

If SuiteAnalytics Dataset is not feasible, you can do customizations.
*custom transaction line field that would store the value of the Created From field
*custom transaction line field that would store the value of the Created From: Shipping Cost field

Hi Kirtee Jeetah-Naran

When a client has only a NetSuite Production account and no sandbox, the best approach is to implement changes carefully and incrementally in Production, keeping critical features disabled until testing is complete. Native NetSuite controls such as roles, permissions, inactive records, and feature toggles can be used to test without impacting live users, along with minimal or sample data wherever possible. We can also use custom flagging in records and transactions to identify test data. The Release Preview (RP) account provided by NetSuite for a few months can also be used for testing configurations, scripts, and workflows in a safer environment. While purchasing a Sandbox account remains the recommended long‑term solution, disciplined Production testing combined with RP usage and strong change control is a practical short‑term approach.

Thank you

Hi @User_WA9MO,

We sincerely apologize for the delayed response as we were coordinating this to proper teams. Can you please try the solution from SuiteAnswer 91463 | Creating a Budget from a Work Breakdown Structure.

To create a budget from a work breakdown structure:

1. 
   Go to Lists > Relationships > Projects.
2. Click Edit next to the project you want to update.
3. Click the Work Breakdown Structure subtab.
4. Click Set as Baseline Budget.

Thank you for your inputs @Entartes!

Hi @Richard Appleford OB

In order to create a new Opportunity from a Lead Record, the Lead Form used should show the Opportunities Subtab. However, the Standard Lead Form does not have the Opportunities subtab displayed by default. This article shows how to display the Opportunities Subtab on the Lead Forms.

Customize Entry Form for Lead

1. Navigate to Customization > Forms > Entry Forms
2. Preferred Customer/Lead/Prospect Form: Click Customize/Edit 
3. Name: Enter Custom Lead Form
4. Click Sublists
5. Click Sales Team
6. Show: Enter Checkmark for Opportunities
7. Click Save

2. Use the Preferred Lead Form

1. Navigate to Setup > Sales > Sales Preferences
2. Click General
3. Preferred Lead Form: Select Custom Lead Form
4. Click Save

I hope this helps.

Hi @Kirtee Jeetah-Naran ,

It's a BAD idea to not purchase a sandbox because the process of configuring and performing UAT is specifically to ensure that all configuration is approved prior to moving it into production. Without this possibility, your client may end up losing a lot of money if they need a re-implementation due to being stuck with a design that doesn't support their needs.

Spend more time on requirements gathering, documenting designs etc PRIOR to configuration. Once SuiteSuccess is installed (be sure to follow all instructions) they won't have much opportunity for customizations since there is no way to completely wipe a customization if they don't want it.

Good Luck

Hello @Dext3r, Sorry for the delay. Upon testing and reviewing I could figure what's happening here Smart Count visibility is permission-driven and cannot be added via Center Tabs or Center Customization. The recommended approach is Customize the Standard Smart Count Inventory Counter role(Center Type : Shipping Center) as it's built with the purpose and already includes Smart Count Reports and Dependencies. You an then add all the other permissions required as per your expectations or You can compare your Role with the Smart Count Inventory Counter Role and add missing permissions.

SuiteAnswers for reference :
1023481 Permissions Required for Smart Count Roles
106431 Smart Count Roles and Permissions
_________
In case you know someone who is new to NetSuite, we encourage you to direct them to our newly launched "New to NetSuite" page. This page is specifically designed to offer them information and guidance and help them make the most out of their NetSuite journey. Click here for more details.