Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Best Of
Re: Entity Relationship Diagram for NetSuite2.com Schema
Hey @Febin Antony,
This tool should help:
I only used their paid version, but the free version may be sufficient, too.
Re: Unrestricted Saved Search not returning results for non-admin users on formula columns.
I see what you mean, and, in theory, the formula should have worked.
At the same time, because you are referencing "WHEN [type] = …", NetSuite should scan all transaction types to find the right types. These roles likely don't have access to all transaction types, which is causing the issue.
Can you check whether the Custom Roles have the "Find Transaction" permission, with the level set to Edit or Full? I wonder if that may help.
If not, try the "WHEN {recordtype} IN ( 'invoice', 'creditmemo' )" and see if that helps.
The only other options are to update the roles and give them access to the missing Transaction Types (that you use in your account) or check the "Core Admin Permissions" checkbox on the Custom Role.
Re: Unrestricted Saved Search not returning results for non-admin users on formula columns.
Hi @Dext3r I agree with Tigran's explanation, especially around permissions and how formulas evaluate records beyond what’s immediately visible in the first column.
Based on similar behavior I’ve seen in other saved searches, there are a couple of additional things worth checking:
- Background processes executing as Admin
In some cases, saved search results behave differently when there is a script or workflow running in the background with an “Execute as Admin” option enabled. When this is set, NetSuite evaluates certain values using administrator-level privileges, which can cause admins to see results while non-admin users see blanks, particularly in formula fields. - Subsidiary restrictions on the role
Even if users can see the base amount column, formula results may still be affected if the role is restricted to a specific subsidiary. I’ve seen scenarios where one role had access to all subsidiaries while another was limited to a single subsidiary, and the formula results only appeared once the subsidiary access was aligned. After updating the role to include all relevant subsidiaries, the saved search returned consistent results across roles.
So while the formula logic itself may be correct, differences in:
- transaction access,
- background execution context, or
- subsidiary visibility
can still cause formula columns to return blank values for non-admin users.
Hope this helps narrow it down.
If you find this reply to your question as helpful, others with the same question might find it helpful as well. By marking “Yes” on the“Did this answer your question?”, you’ll be able to aid the community to find the solution much easier and faster without the need to read through all the replies, and you will also get closer to earning your next Answer Accepter badge.
Re: CoPilot and MCP - How to get it working?
Hi @Grundemann Jiri ,
If Claude works but PowerApps (MCP) gives "Invalid login attempt," try these:
- Double-check that your redirect URI in PowerApps exactly matches what’s in your NetSuite integration record.
- Make sure the NetSuite role used for MCP has all necessary web services and REST permissions.
- Confirm you're using the correct OAuth2 flow in PowerApps ("Authorization Code Grant" is usually required).
- Ensure the user account is active and not locked.
If anyone has this working, please share your setup tips!
Retrieve the Transaction Status Name via ODBC or SuiteQL
When retrieving the Transaction Status via ODBC or SuiteQL, results are displayed as symbols (i.e. A, B, C) instead of "Pending Approval, Billed", etc. This is the sample query that displays status as symbols: SELECT status FROM transaction.
In order to get the desired values of the status as their text equivalent, use BUILTIN.DF(status) instead of just status. This way, it will retrieve the status name (i.e. Pending Approval, Billed).
Sample query tested via SuiteQL in console:
FROMrequire(['N/query'], function (query) {
var csFileIdQuery = "SELECT status FROM transaction";
var results = query.runSuiteQL(csFileIdQuery).asMappedResults();
console.log(results)
});
TOrequire(['N/query'], function (query) {
var csFileIdQuery = "SELECT BUILTIN.DF(status) FROM transaction";
var results = query.runSuiteQL(csFileIdQuery).asMappedResults();
console.log(results)
});
This is also applicable in many other similar situations, such as, when trying to obtain an actual name from an ID, etc.
Re: Can not show diagonal line in PDF Template
Hey @Jet Zhang,
How critical to show the diagonal line?
Perhaps you can use " \ " text/character as a separator.
What do you think?
Re: Inventory Count (IC) issues
Hi @User_6YI1X ,
It's ALWAYS recommended to export your items, assign the count classification, interval and next count date to all items in excel, then import the data.
You're right, doing it one by one is not viable.
Subsidiary-Wise Trial Balance in NetSuite
1. Background
NetSuite’s standard Trial Balance (TB) report does not currently support subsidiary-wise segmentation, which is a common reporting requirement in OneWorld environments. This limitation is tracked under Enhancement #174031.
To address this reporting gap, we implemented a workaround by customizing the Balance Sheet report to replicate the Total view of the Trial Balance for individual subsidiaries.
2. Approach Overview
The customized report uses the Balance Sheet structure but is redesigned to behave like a Trial Balance. This is achieved by:
- Clearing all layout rows
- Adding a Financial Section containing all accounts
- Applying specific display settings
- Filtering by Subsidiary to produce subsidiary-wise outputs
While this approach replicates the Total view of TB, it cannot reproduce the Debit/Credit split, which remains a limitation.
3. Customization Steps
3.1 Base Report
We begin by customizing the Balance Sheet report.
3.2 Layout Changes
- All pre-existing layout rows are removed.
- A Financial Section is added that includes all account types (Assets, Liabilities, Equity, Income, and Expenses).
3.3 Display Settings
- Display Row → Unchecked
Ensures only accounts with balances appear. - Reverse Sign → Checked
Aligns the sign conventions with the Trial Balance totals.
6. Data Validation
The balances produced by the custom report were cross-verified with the Standard Trial Balance to ensure accuracy.
This included checking:
- Accounting period
- Subsidiary context
- Consolidated vs non-consolidated view
- Include/Exclude Children
- Currency settings
7. Known Limitations
- Debit/Credit columns cannot be reproduced in this method.
- The approach mimics the Trial Balance only in terms of ending balances (Total view).
8. Summary
Although NetSuite’s standard Trial Balance report does not support subsidiary-level segmentation, the customization of the Balance Sheet report provides an effective alternative. With the right layout, filters, and display options, the subsidiary-wise Trial Balance totals can be reliably reproduced to meet business reporting needs, with the exception of the Debit/Credit view.
Re: Sales order print has an error, unable to identify the same
Hi @User_IM2YY
Someone edited your layout, and then saved it with an error on line 670 in the script version of your template.
The only way to fix this is to go in and try to undo whatever they did. Alternatively, you can switch to the basic template on the form, while you're trying to fix the advanced pdf layout.
Editing layouts should ONLY be done by creating a copy first, then editing your copy. This is the only way to prevent exactly what you have happening.
I hope this is helpful!
Re: Bill > Department and Class Line Level Mandatory
Hey @User_K51C7,
There is also a global Accounting Preference to make Classes and Departments mandatory on all Transaction Lines.