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: Long Item Description Cutoff in Print created by Advanced PDF Template
Hello @Angel mariya T. P. ,
You will need to customize the advanced pdf to have more room on the invoice and wrap the text.
Re: SDF browser-based authentication fails in SB1 after sandbox refresh.
I was able to get it working. The root cause was that the SuiteCloud Development Integration record was disabled.
rosse
New to NetSuite | Advanced Taxes: U.S. Tax Lookup – Scenarios Part 2
After presenting sample scenarios on the highest priority in the U.S. Tax Lookup, which is the Tax Item on the Customer record in our previous discussion, we will now provide scenarios for the next in hierarchy:
If the customer has a valid shipping address:
- Tax Schedule = Taxable and Charge Out Of District Sales Taxes = True, the system will pull up the tax code of the Shipping Address.
- Tax Schedule = Taxable and Charge Out Of District Sales Taxes = False:
- The system will pull up the Home Tax Code of the nexus.
- If there are no Home Tax Codes assigned, the system will pull up the Default Tax Code under the Setup > Accounting > Set Up Taxes.
For our demonstration, we'll use two items in the transaction: one with a taxable schedule and the other with a non-taxable schedule.
The sample valid customer address is 1400 E 70TH ST, Los Angeles CA 90001-1921:
Additional details will be provided in the following scenarios below.
Scenario #1: Customer record > Taxable = T and Tax Item = null. On the Setup Taxes page, Charge Out Of District Sales Taxes = True; with value on Home Tax Code and Default Tax Code
- Customer with Taxable = T and Tax Item = Null
- Charge Out Of District Sales Taxes = True; with value on Home Tax Code and Default Tax Code:
- On the Invoice transaction, select customer on scenario 1 then add the two items with taxable and nontaxable schedule:
- Taxable Item = CA_LOS ANGELES_ZFYC_POID_33
- Nontaxable Item = -Not Taxable-
As you can see, the system pulled the tax code of the shipping address which is aligned with the hierarchy presented above.
Scenario #2: Customer record > Taxable = T and Tax Item = null. On the Setup Taxes page, Charge Out Of District Sales Taxes = False; with value on Home Tax Code and Default Tax Code
- Customer with Taxable = T and Tax Item = Null
- Charge Out Of District Sales Taxes = False; with value on Home Tax Code and Default Tax Code:
- On the Invoice transaction, select customer on scenario 2 then add the two items with taxable and nontaxable schedule:
- Taxable Item = CA_SAN JOSE
- Nontaxable Item = -Not Taxable-
As seen in the scenario above, since the "Charge Out Of District Sales Taxes" is not marked as true, the system pulled the Home Tax Code associated with the CA nexus from the "Set Up Taxes" page, which is "CA_SAN JOSE."
Scenario #3: Customer record > Taxable = T and Tax Item = null. On the Setup Taxes page, Charge Out Of District Sales Taxes = False; Home Tax Code = null; Default Tax Code = with value
This scenario is identical to Scenario 2 above, with the only difference being that the Home Tax Code has no value selected:
- Charge Out Of District Sales Taxes = False; Home Tax Code = null; Default Tax Code = with value:
- On the Invoice transaction, select customer on scenario 3 then add the two items with taxable and nontaxable schedule:
- Taxable Item = AL_ABBEVILLE
- Nontaxable Item = -Not Taxable-
As seen in the scenario above, since the "Charge Out Of District Sales Taxes" is not marked as true, and the Home Tax Code for CA nexus has no value, the system pulled the Default Tax Code under the Setup > Accounting> Set Up Taxes, which is " AL_ABBEVILLE"
___
Follow the New to NetSuite > Advanced Accounting & OneWorld category to be updated whenever new articles are released!
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.