Red Velasco-Oracle NSC Guru

Hi @faisalabdulmoid_39498, This looks like a context difference between Client Script and Suitelet/server-side SuiteScript 1.0. On the Project Task record, custom segment fields can behave differently depending on whether they are exposed as a body/event-style field or as a segment column. In the Suitelet search, NetSuite…

Hello @Barb_CF Good day to you! Just wanted to circle back to this. Let me know if you need any other assistance or clarification from my end. Thanks!

Hello @Elina Kourouzidou, Just wanted to circle back to this. Have you checked the comments above? Let me know if you need anything else from our end. Thanks @Todd N Niedringhaus for the inisght!

Thanks for the insight @Estee! If there are any other specific use cases that you have used on your business process you can share them by creating discussions, member contents are more than welcome and appreciated!

Hi @User_N2L2G You are correct to question this. In the standard NetSuite check template, the routing number and bank account number are not normally exposed as selectable fields in the WYSIWYG field picker. Even if you upload a MICR font successfully, the font only controls how text is displayed. It does not make the bank…

Hello @Barb_CF For this type of issue, I would be careful about trying to simply change the Account Type on the existing GL accounts, especially if those accounts already have posted transactions. In many cases, once an account has activity, changing the account type may be restricted or could impact financial reporting…

Hello @User_DAIMX Thanks for reaching out! 💬 This is the perfect place to get answers, and the NetSuite Community is always ready to help. Let’s open up the discussion and share some insights!

@RAJDINESH Fantastic question! 🎯 Your curiosity pushes the whole community forward. To all our NetSuite experts out there, don’t be shy—let’s share some ideas and work through this together!

Hello @Aaron McCausland , Based on the error shared earlier, this may not be caused directly by setSegmentValueId() or getSegmentValueId(). The actual error shown was: Custom GL Lines Plugin error due to a failed validation of script output: Transaction was not in balance. Total = -25.08 That means NetSuite was able to…

Hello @Jan Prinosil, Good day. To answer your question straight, this is indeed a NetSuite behavior / limitation with the Employee Center role. It is listed under Enhancement # 27669 - Need to allow users logged into Employee Center to choose from standard and custom forms when entering purchase requests and expense…

Hello @Jayben Fung I just wanted to circle back to your concern. Let me know if you have any other concerns. Have a great day!

Hello @ User_N70FV Thank you for bringing up such an interesting topic! 🌟 This is what the NetSuite Community is all about—supporting each other. Let's hear your thoughts, everyone!

Hi @faisalabdulmoid_39498 , If you see NetSuite Next in the account, that confirms you have access to the newer AI experience, but SuiteAgent/SuiteCloud AI availability may still depend on enabled features, permissions, and release access. You can check in a few places: Go to Setup > Company > Enable Features Review tabs…

Hello @Jayben Fung Based on the screenshots, the workflow itself appears to be working for newly created records. The new Payment Voucher entered the Approved workflow state, the record is locked, and the Edit button is hidden. For the older records copied from Production to Sandbox, the likely reason the Edit button still…

Hello Thank you for bringing up such an interesting topic! 🌟 This is what the NetSuite Community is all about—supporting each other. Let's hear your thoughts, everyone!@User_S6FVQ,

Hi @faisalabdulmoid_39498 SuiteAgent examples and documentation may be limited depending on your account access and enabled features, so I would first confirm availability in your NetSuite account and check the latest NetSuite Help Center documentation. In general, you do not need to integrate a SuiteAgent into every…

Hi @Richard Appleford OB, Good day! Just wanted to circle back to your concern. Let us know if you need further assistance on this. — If the previous reply was helpful to you, it could be useful for others with the same question. By marking 'Yes' on 'Did this answer your question?', you'll help the community find the…

Hi @ User_PCF01 Adding to what’s already been shared, one other thing to consider is role/permission differences. Even if the form is the same, if the user’s role has different permissions (especially around Addresses or Vendors), it can sometimes affect whether the address defaults or not. You may also want to check: If…

Hi @ User_N0UVQ You usually do not need a separate line ID for this. For the apply sublist, the key value is the internal ID of the invoice in the <doc> field. That is what NetSuite uses to know which invoice to apply or unapply. Since this is not a real Customer Payment, that may be why you are not seeing the apply line…

Hello again @User_N0UVQ Yes, this is technically possible via SuiteScript, but there are some important limitations to be aware of. When a Journal Entry is applied to multiple invoices, the application is handled at the transaction level. If you attempt to update the Journal Entry via script, NetSuite may remove the entire…

Hello @User_N0UVQ Thank you for bringing up such an interesting topic! 🌟 This is what the NetSuite Community is all about—supporting each other. Let's hear your thoughts, everyone!

Hello @Mike F Blend Thank you for bringing up such an interesting topic! 🌟 This is what the NetSuite Community is all about—supporting each other. Let's hear your thoughts, everyone!

Hello @Tom Dalton, Circling back to this concern. Let us know if you need further assistance. — If the previous reply was helpful to you, it could be useful for others with the same question. By marking 'Yes' on 'Did this answer your question?', you'll help the community find the solution more quickly without needing to go…

Hi @TEN Just wanted to get back to this concern let us know if you need further assistance — If the previous reply was helpful to you, it could be useful for others with the same question. By marking 'Yes' on 'Did this answer your question?', you'll help the community find the solution more quickly without needing to go…

Hello @User_PM4A7, Have you checked the comments above? Just to add: Since the standard PO form works but the custom form does not, this looks like a custom form issue rather than a vendor or workflow issue. One more thing to check is whether the billaddress or billaddresslist field is set to Inline Text, Disabled, or Read…

Hi @Richard Appleford OB, Since it’s showing correctly in a standard account but not in your case, this does point to the custom Customer form / sublist setup rather than the CSV import itself. Given that: Transactions appear in the Dashboard view But not in the Form view (Related Records / Transactions subtab) And filters…

Hi @TEN Hope everything is fine on you end. Firstly thanks for answering the following question. Based on the previous responses, it looks like the issue is not with your setup but with how the SuiteApprovals Map/Reduce script is processing the PO. Since: Some POs enter the approval rule and others dont The script is…

Hi @Tom Dalton, Thanks for sharing the additional context—that helps clarify the issue. Since your custom item field works on the record but errors in a saved search, the main difference is how NetSuite evaluates formulas. In saved searches, fields like {pricelevel9} are often not valid, even though they work in item field…

Hi @User_DB9YX , Just wanted to circle back to your concern. Let me know if you need further clarification.

Hi @User_DB9YX , Short answer — this is not supported. The “Actions” tab in Auto-Create GL Transaction Rules only allows standard fields and does not support adding custom transaction body or line fields. If you need to incorporate custom field logic, the usual options are: Using criteria in the Saved Search that drives…