Best Of

Hi @Lyssa

In NetSuite, Total Interval Value represents the Total Contract Value (TCV)—meaning the total amount of all charges over the entire term of the subscription.

• Your Term: 3 Years
• Your Recurring Amount: $1,000 per year
• Your Total Interval Value: 3 * 1,000=∗∗3,000**

1. Do NOT map the "Price Plan" field: Leave the Price Plan mapping completely blank.
2. Map "Total Interval Value": Map this to your $3,000 column.
3. Map "Charge Frequency": Make sure you map this to Annually.
4. Map "Status" as Draft: This is the most common reason imports fail! You can only import a Total Interval Value if the subscription line status is set to Draft. Once imported, it can be activated.

Hi @User_NQL2C
In NetSuite, you cannot apply a vendor credit directly to a Purchase Order (PO).

This is because a Purchase Order is a non-posting transaction—it represents an intent to buy and does not have a general ledger impact or create an Accounts Payable (AP) balance. Vendor Credits, on the other hand, are posting transactions that reduce your AP balance. Therefore, a Vendor Credit can only be applied to a Vendor Bill.

Apply at Payment -

Instead of holding the credit memo on your desk until the check is sent, you can enter it into NetSuite immediately. It will sit in the vendor's account as an open credit until you are ready to pay.

Agreed, I thought so too, but I think that should solve. Appreciate the help.

Hi @User_HKSJJ

NetSuite’s published logic is: customer-specific pricing should win first, then price rules help break ties among multiple customer-specific prices, and only after that does the Highest/Lowest preference apply.

If you’re seeing a Price Rule (25%) override Customer Item Pricing (10%), it usually means NetSuite is not treating your customer item price as “qualifying” on that transaction. Common reasons:

• Currency/price availability mismatch (especially if the rule returns a price level and prices aren’t all available in the SO currency).
• The rule is forcing a price level/rate so the line is priced in a different “lane” than customer item pricing.
• Your “10% / 15% / 25%” aren’t actually competing as the same type of price (rate vs discount vs price level), so the “conflict” logic isn’t being applied the way you expect.

For the dynamic customer group issue (106 members then later 579, and inconsistent application): that pattern fits delayed refresh/caching of dynamic group membership. A good test is to apply the same rule to a static group of known customer, if it becomes consistent, the problem is likely dynamic group refresh timing rather than the pricing rule itself.

To pinpoint it, check the SO line’s Price Level / Rate / Currency when the rule triggers, and confirm all competing prices exist/are comparable in the transaction currency.

Thank you for the quick responses

that's what I was hoping for but it logs me out if log in from a different computer with the same email

Thank you, @Todd N Niedringhaus.

User_N1Q40,

In addition, the Customer-Scheduled Maintenance page shows all dates and times using the time zone you set in User Preferences.

Maintenance notifications use the date and time format and time zone recipients set in their User Preferences.

For reference, please see SuiteAnswers ID: 95187 Customer-Scheduled Maintenance FAQ.

Hello @maffooclock,

Good day.

1. Created From field is not available in the Opportunity Record.
2. A 'cases' sublist does not exist in the Opportunity Record as of SuiteScript version 2025.2.
3. You can access the Related Transactions for Opportunity records using N/search module to search for cases related to the transaction record. Here's a sample code that you can use as a reference:

I hope this helps!

Hi,

When you want to create a new theme (Theme Y) based on an existing theme (Theme X), you should deploy it using:

gulp theme:deploy --create

This will create a new theme record in NetSuite instead of overwriting the existing one.

For your first question, if you want to delete a deployed but not activated theme, you can go to:

Customization > Lists, Records, & Fields > Record Types

Then find SC ExtMech Extension, click List, and in the SC ExtMech Extension List, locate the corresponding theme record and delete it.

Hope this helps!