Red Velasco-Oracle NSC Guru

Hi @User_S8PAJ , Yes, this is possible with SuiteScript. A developer can use a beforeSubmit User Event script on Sales Orders to identify the affected Customer and set the required Subsidiary before the order is saved. The target subsidiary must be assigned to the Customer, and the integration role must have access to that…

Hello @ faisalabdulmoid_39498 Thank you so much for reaching out with your question! 🎉 The NetSuite Community is full of knowledgeable experts—let's work together to help find a solution. Fellow community members, feel free to chime in!

Hello @User_BCKYD I just wanted to check up with your testing. Let me know if you still need help. — 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…

Hello @User_D548K Thank you so much for reaching out with your question! 🎉 The NetSuite Community is full of knowledgeable experts—let's work together to help find a solution. Fellow community members, feel free to chime in!

Hi @User_BCKYD , Yes, you would use Customer as the workflow record type. There is no separate Bank Details subtype available in a Customer workflow, so the workflow cannot directly run against an individual Bank Details line. For the scheduled-workflow approach, the workflow would still be on the Customer record. You…

Hello @Carrie DRSD Just circling back to this concern. Are the comments and suggestions above helped you with this concern? Let me know if you have any questions!

Hi @User_QQ76D, Just circling back to this concern. Are the comments and suggestions above helped you with this concern? Let me know if you have any questions!

Hi @Carrie DRSD, If you are having to correct leave balances every month after integrating with NetSuite Payroll, I would first check whether the issue is coming from the accrual setup or from the payroll import/integration mapping. A few things to review: Confirm the leave/paid time off plans are set up with the correct…

Hi @User_QQ76D, Adding to Dext3r’s answer, I would also suggest making sure the result column is set as Formula (Text), not Formula (Numeric), since the final output needs to display as H:MM. You may also be able to simplify the formula by avoiding the TO_DATE(TO_CHAR(...)) conversion unless it is specifically needed.…

Hello @Joel Ratcliffe Glad to hear it worked. For your follow-up, Item Labels are generally tied to the transaction context NetSuite uses when printing them. If the label is being printed from the Purchase Order flow, the available fields are usually from the PO context, which is why {transaction.custbody...} works only…

Hello @srussell 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!

Hello @Kevenale 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!

Hello @MJ NCO 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!

Hi @User_VW1KQ This is expected behavior in Advanced PDF/HTML templates. The item line field ${item.location} can display the location value/name correctly, but it does not reliably expose the full related Location record fields, such as city/address, per line. That is why ${item.location.city} keeps returning the same…

Hi @Joel Ratcliffe For the basic Item Label Transaction PDF Layout, the field has to be available from the transaction context that the label is rendering from. In the SuiteAnswer example, the field being printed is a custom transaction body field stored on the Purchase Order, and the PDF layout references it like:…

Hi @faisalabdulmoid_39498 , Thanks for the update. Since it works under Administrator, this does point to a role/permission issue rather than the script syntax itself. In addition to Setup > Custom Segment, I would also check the permissions on the segment record itself. Custom segments can have their own access settings,…

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…