Points to be noted before deploying Workflow using SDF

We have different methods to deploy a workflow from sandbox to production. The methods can be manual creation, Suite Bundler, Copy to account or SDF method. While deploying a workflow to production, keep note of the following points. If the workflow has dependency fields that are created on the sandbox and not yet in the… Continue reading Points to be noted before deploying Workflow using SDF

Email recipients chunking to not exceed the limit 10

When implementing new functionalities to send emails, we have to be careful about the NetSuite limitation. A maximum of 10 recipients (recipient + cc + bcc) is only allowed. So to tackle this issue, we have to chunk the recipients before sending the emails, such that if we got 5 recipients, 3 cc and 4… Continue reading Email recipients chunking to not exceed the limit 10

Finding duplicated occurrences across multiple record entries

Prepare a saved search for the record. Two key fields are needed here: Counting: count the internal id of the record. Grouping: group on the column that produces the duplicate. With the result fields having grouped and counted values, running the saved search will show the count of records with the occurrences of same type.

Unexpected SDF error for Workflow

When deploying workflow from sandbox to live account via SDF an error is thrown. Validation failed. An error occurred during manifest validation. Details: All term references must be to terms in translationcollection objects in the same SuiteCloud project. Terms cannot be referenced in other SuiteCloud projects, bundles, or SuiteApps. File: ~/manifest.xml

Unexpected Department error while deploying workflow via SDF

While deploying workflow through SDF, an unexpected error throws saying ‘STATICDEPARTMENTS must be enabled in your account’.This throws up because the workflow uses Departent Division but the manifest.xml does not contain the feature for DEPARTMENTS. Adding < dependencies> <feature required =”true”>DEPARTMENTS</feature> in the manifest.xml will solve the issue.

Integrating line items of Transactions via REST

When Transactions like Sales Order, Invoice are integrated via REST Web services, the expected data structure needed for adding transaction lines is an object with an array of line item objects. Here’s an expected input to sync or integrate line items of an Invoice/SO along with the body fields. { “items”: [ { “item”: {… Continue reading Integrating line items of Transactions via REST

Reversal of journal lines using Suitescript

In order to reverse the Journal lines, we can use a script to fetch the line count and the line field values.After fetching the values the lines can be reversed added to the existing Journal lines. So if there are 3 lines, the new reversed Journal will have 6 lines with the accounts, amounts and… Continue reading Reversal of journal lines using Suitescript

Financial Report results show different results when filtered by period and date.

A financial report shows different balances for a chart of accounts when run by two different users. One user has the report filtered by period and the other user by date. So when the same financial report is opened by both users, the results are different. A potential issue will be when a transaction date… Continue reading Financial Report results show different results when filtered by period and date.