Posting and non-posting discounts/markups are not allowed on the same transaction

Scenario Saving a Transaction gets an error of “Posting and non-posting discounts/markups are not allowed on the same transaction”  Solution By design, the system will not allow a Transaction with either two or more Discount or Markup items that are both a posting and non-posting account to be saved.  This is covered by Enhancement # 156967 – Please have the ability to add a non posting discount and a posting… Continue reading Posting and non-posting discounts/markups are not allowed on the same transaction

Application Performance Management (APM)

The Application Performance Management (APM) SuiteApp enables you to see and manage the performance of your NetSuite customizations and business-critical operations. Analyzing Scripts: We can adjust date ranges. Follow the navigation : Customization> Performance> Suitescript Analysis Then we can select individual scripts and analyze the performance based on the execution time etc. See the below… Continue reading Application Performance Management (APM)

CCPA Privacy Deletion Request Flow

Requirement: Privacy Request on the website is sent through Listrak to remove customers from all mailing lists. When done the customer account is wiped of all personal information including name, address, contact information, etc. We should still be able to see the customer account order history but not see the customer name or anything about… Continue reading CCPA Privacy Deletion Request Flow

vendor Preference and PO printing

If TO BE PRINTED is checked in the Purchase Order ( under Communication> Messages) it will appear in the print Queue.a). If it’s Standalone PO, it will follow vendor preferences and marks the TO BE PRINTED if Vendor>Send transactions via : Print = T, similarly to other preferences.b). If it’s Dropship PO, it won’t follow the vendor preferences. Take print for… Continue reading vendor Preference and PO printing

Some Limitations of BeforeLoad() in User Event Script

beforeLoad() Entry point limitations: beforeLoad() user events cannot be triggered when you load/access an online form. Data cannot be manipulated for records that are loaded in beforeLoad scripts. If you attempt to update a record loaded in beforeLoad(), the logic is ignored. Data can be manipulated for records created in beforeLoad() user events. Attaching a child custom record to… Continue reading Some Limitations of BeforeLoad() in User Event Script

MerGroup to Commerce Category Mapping – Solution Design

Requirement As a member of the Marketing Team I need to be able to manage the 20,000 items and their relationships to Commerce Categories without going crazy So I need the system to add and remove items from Commerce Categories based on the MerGroups(custom record) assigned to each item. Solution Notes We will create a… Continue reading MerGroup to Commerce Category Mapping – Solution Design

Sales Ranking Items – Solution Design

We need to weekly review the sales Rank of the Items based on their sales history of it. Require a field on the Items called “Sales Rank”, that has its ranking in total Sales (over the past year) Our Solution: First of all, we will create a search of sales orders as follows: 2. We… Continue reading Sales Ranking Items – Solution Design

Merging Duplicate Records- Automation

There are two ways to merge duplicate entities without manual intervention. That we can schedule the duplicate detection process and the system will merge those records automatically. Standard Method: Scheduling a Mass update: List > Mass Update > Mass Updates > Duplicate Resolution. Then we can set criteria accordingly and schedule this to run at… Continue reading Merging Duplicate Records- Automation