Concatenate 3 fields on the results of a Saved Search

To concatenate 3 fields on the results of a saved search, do the following: 1. Create a saved search, List > Search > Saved Searches > New. 2. You may select any search type, for this example select Customer. 3. Navigate to the Results tab and add the field “Formula (Text)” and enter the following as the value of… Continue reading Concatenate 3 fields on the results of a Saved Search

NetSuite – How to create a Sales Report by Month when column option is not available

In order to use the same column option for a New Report the option to use Matrix Report will show the similar information.For this example the report will show Transaction by Item that are posted to a particle account. The same concept can be used for customized reports. 1. Navigate to Reports >  New Report2. Select Transactions3. Metric = Amount4. Check Matrix for… Continue reading NetSuite – How to create a Sales Report by Month when column option is not available

Remove the – New – option from drop downs for certain roles

Employees will see the – New – option in certain drop downs if they have the ability to create that type of record.  To remove this the permission to create that type of record should be removed from the role or the Level should be set to View.  This will also prevent employees with this role… Continue reading Remove the – New – option from drop downs for certain roles

Permissions Required to Create a New Financial Report

A user with a custom role needs to create a new financial report. When the user navigates to Reports > New Financial Report, the user gets Notice: You do not have permission to perform this operation. The role already has the permissions for Financial Statements set to View and Report Customization set to Full under Permissions tab > Reports on the role. For the user to… Continue reading Permissions Required to Create a New Financial Report

Set field value action – Workflow

Set field value action on the Before Record Load server trigger, you can set the value of a field during the creation of a new record as the entry form is loaded into the browser. However, you cannot set the value of a field when editing or viewing an existing record.

Server triggers – Workflow

Here are some key things to remember when working with server triggers. Use before record load rather than before user edit when configuring actions that affect the display characteristics of form fields when loading a record. If you want an action to execute only once when entering or exiting a state, use the entry or… Continue reading Server triggers – Workflow

Workflow trigger events

In step 1, the user requests the display of a record either through the creation of a new record or by viewing or editing an existing record. The server retrieves the record from the database and passes it to the before record load server trigger, which performs pre-processing on the record form, such as setting… Continue reading Workflow trigger events

How to create a report that shows sales per customer with a year-on-year comparison

1. Navigate to Reports > Financial > Comparative Income Statement > Customize2. Edit Columns > Add Budget and Financial: Customer/Job: Name3. Set Comparative Amount: Alternate Date Range = last fiscal year (e.g., 2020)4. Set Filters > Budget and Financial: Account (Line): Name equal to Revenue or Sales (or whatever account is used in recording sales). Add.5. Set Budget and Financial: Date: Enter From and To Dates. Click Done6. Click Preview

Key things to remember when creating new data sets in SuiteAnalytics Workbook

Here are some key things to remember when creating new data sets. •             Only fields added to the source data grid will be available in workbook visualizations. •             Data sets can be used as a complement to saved searches for ad hoc data analysis. •             Same field cannot be added twice to the data set’s… Continue reading Key things to remember when creating new data sets in SuiteAnalytics Workbook

Data duplication in SuiteAnalytics Workbook

Due to the nature of the analytics data source, loops can be found in some join paths which may result in unwanted data duplication. Consider this basic example, the green path represents the logical join path from the base transaction record to the account record through the transaction line and transaction accounting line records. The red path represents the loop and the possibility of data duplication. Be aware of this when defining filter criteria or when adding… Continue reading Data duplication in SuiteAnalytics Workbook