Mi contenido
Please note that on Friday, September 19, 2025, at 8:00 PM Pacific time, our Case Management System will undergo a scheduled maintenance for approximately 4 hours. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.
Comentarios
-
Hey @User_Q1DPO, You can't do that natively. The workaround is to create a custom "Payments" sublist (Saved Search) and add it under the Related Records, and hide the native "Payments".
-
Hey @Vernita, The Project Task record doesn't support inactivation. The alternative option for these types of records is to create a workflow and "lock" the record. You can create a "Lock" button via workflow that would lock the record when it is pressed.en No Inactive Button on a Project Task Record Comentario por Tigran Shahnazaryan Jul 4, 2025 2:58PM
-
Hey @R. Dieka Pribadi G. E.,, You won't be able to restrict access to the native bulk-approval page. Instead, you should be able to build a "Before Record Submit" workflow to prevent the approval of non-applicable PR/PO. There is a chance the workflow might not be able to catch these POs, and if that is the case, you would…
-
Hey @User_FZNHI, Creating the year 2030 isn't unusual. We sometimes need to get to 10+ years ahead to accommodate Amortization and RevRec schedules. The report filters are usually sticky, so if you select 2025 next time, that value should stick. If it doesn't, try clearing the browser cache and try again. Also, ensure you…
-
Hey @Adam W, If you are building a Transaction Search, ensure to set the Main Line = False and use the Applying Transaction to get the WO information. The Applying Transaction would also contain Invoice, Item Fulfillment, and other records, so you would need to exclude unrelated transactions via Criteria or formulas in the…
-
You are correct - because the Expense Category and Expense Report records are unrelated, their custom fields (Transaction Line and Other Record) can't get sourced from each other. The best option would be to build a UE script to do that as the Workflow won't work either.
-
Thank you, Team!!
-
Hey @esabis, Because the Post Time JEs are system-generated, it will be hard to define the custom JE form. If NetSuite didn't provide a configuration option to select the Journal Form for Post Time, then you have to explore SuiteFlow (After Record Submit) or SuiteScript options.
-
Hey @Honey Soe, You can set the Accounting Preferences → Approval Routing → Invoices checkbox and use the SuiteFlow for Invoice Approvals. Setting the native "Approval Status" field to "Pending Approval" will prevent invoices from impacting the GL. One of the main issues I have encountered is preventing self-approvals,…
-
Hey @User_FL4CK, I recommend going through the details on the related SuiteAnswers articles, which provide useful details on the Post Vendor Bill Variance functionality: https://suiteanswers.custhelp.com/app/answers/detail/a_id/11157/loc/en_US https://suiteanswers.custhelp.com/app/answers/detail/a_id/11158/loc/en_US
-
Hey @Divya Unnikrishnan, Would it work for you if, on the Expense Report, you use the custom field type as "Free-Form Text" instead of "List"? That works more frequently and would still copy the required value to the Expense Report.
-
@Divya Unnikrishnan - No, there isn't a standard report or Saved Search option to replicate the COA view.
-
Hey @User_V93G9, Here is a video on SuiteAnswers covering the setup: https://suiteanswers.custhelp.com/app/answers/detail/a_id/1011846/loc/en_US
-
Hey @User_8X6LQ, Yes, it might be an issue with permissions. The user running the Income Statement should have access to all related subsidiaries to view their financials.
-
Hey @Divya Unnikrishnan, You can't do that natively via Saved Search. Some fields, such as Account Currency or the Eliminate checkbox, are only accessible via the Workbook.
-
Hey @Ba11zooka, There is a chance the old names are sourced from the browser cache. I recommend clearing the browser cache and re-logging to NetSuite to check if the issue has disappeared.
-
Thanks for the screenshots and the clarification, @Marie4455, The "Item Filter" only impacts the "Item" field values. The "Assembly" field is added as part of the "Outsourced Manufacturing" functionality, and NetSuite doesn't have a native functionality to filter the results via Saved Search or other methods.
-
Some of the "Quantity" fields may have an incorrect character (hidden) that sometimes happens when numbers are copied and pasted from Excel. You can try to clear and re-enter the quantities. An alternative would be to open a case with NetSuite Support and ask them to investigate.
-
Hey @User_4CF79, Did you create the Item Count manually or via script? It is possible that a wrong character was entered via the script.
-
Hey @Marie4455, If you are using the Purchase Order record with a custom form for Outsourced Manufacturing, the "Item Filter" should work the same way. Double-check the search that is being used to confirm it is accurate.
-
This might be a temporary issue on the NetSuite side. Perhaps the best is to open an urgent case with NS Support and ask them to investigate.
-
In that case, you may need a custom solution to support Withholding Tax Calculation with SuiteTax. I am not aware of any third-party solutions that would work.
-
Hey @User_DU7YV, Yes, that is the standard practice to use one email address to get access to multiple NetSuite accounts.
-
Hey @Hormese Paul, The issue might be related to the configuration of the related Outsourced Manufacturing Item. This article might help: https://suiteanswers.custhelp.com/app/answers/detail/a_id/91240/loc/en_US
-
Hey @User_Q3A12, The specialized user licenses give limited permissions, which can't be edited. You may need to create a custom reminder to see if you can make it work for the specialized user.
-
Hey @ddennison, Do you know if there were any changes to your domain's DNS records? There is a chance the DNS records were updated and NetSuite-related URLs removed.
-
The SuiteApprovals should support non-inventory items. If NetSuite's 3-way matching workflow doesn't support it, and you want to use it, you might be able to edit/modify it to support it. If not, you would need to build it from scratch.
-
I suspect it is related to the {amountpaid} field being incorrect. Can you replace it with {payingamount} and try again?
-
Hey @User_NUTAA, Your approach is correct. The best is to use a Non-inventory version of the same item for internal use, and there is no need to receive it. The GL impact would be based on the selected GL Accounts on the Item record. You can run a few tests in Sandbox to confirm you get everything you need before…
-
Hey @User_PFUIM, Per NetSuite design, the status of the PO becomes "Fully Billed" if the full quantity is billed. The same applies to other areas, such as Sales Order → Invoice. You can create a 2-way matching workflow (or consider using/updating the 3-way-matching workflow or SuiteApprovals) to capture the amount mismatch…