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
-
Hello @Karanjot Singh, Thank you for posting in the NetSuite Support Community! Hello everyone! Your expertise and knowledge are greatly appreciated, and we ask that you kindly offer your support. Your participation and willingness to assist a fellow member are sincerely appreciated.
-
Hi @kees.netsuiteadmin, Good day. Following up on this in case you missed my previous comment. If you need further assistance, please let us know. Thank you!
-
Hello @User_CDQ4X, Thank you for posting in the NetSuite Support Community! Hello everyone! Your expertise and knowledge are greatly appreciated, and we ask that you kindly offer your support. Your participation and willingness to assist a fellow member are sincerely appreciated.
-
Hi @kees.netsuiteadmin, Good day. We have identified your concern as a potential defect. It would be best to reach out to NetSuite Customer Support to find the root cause. Thank you.
-
Hello @Herman Suherman, I'm circling back to ensure you saw my previous communication. Should you require any additional support, please don't hesitate to contact us.
-
Hi @User_RLXCM, I'm touching base to confirm that you didn't miss my previous message. If you find yourself in need of further assistance, please don't hesitate to get in touch.
-
Hello @RGrier, I'm just checking in to make sure you didn't overlook my prior message. If there's anything else we can do to assist you, please feel free to reach out.
-
Hello @Herman Suherman, Good day. Are you still encountering the error? If so, you could try to get the values of the fields after you set them, and confirm whether they are successfully populated or not.
-
Hello @RGrier, Good day. Can you provide the documentation you followed to set this up? You can also provide your step-by-step so we can replicate it on our end. Thank you.
-
Hi @User_RLXCM, You might want to consider using SuiteQL POST and use the query to get invoice details instead of this method. See sample here: Using SuiteQL with SuiteTalk REST Web Services
-
Hello @Vernita, That is correct. However upon checking, the feature to lock the Project Task record is currently filed as an enhancement request under: 558612 Lists > Relationships > Projects > Ability to Set Task / Project Task to Inactive
-
Hello @rgonz-mhi, Good day! I'm circling back to ensure you saw my previous communication. Should you require any additional support, please don't hesitate to contact us. Thanks!
-
Hello @Rizkygaus, Good day! Gently following up on this thread. In case you need further assistance, please let me know.
-
Hello @Rizkygaus, Good day. May I know how you instantiate the "context" variable? Upon testing, response is returning a blank on my end. This could explain the 'undefined' error.
-
Hello @User_RLXCM, Good day. Have you tried using TO_DATE() function to parse the date field?
-
Hello @rgonz-mhi, Good day. Upon checking, Invoice Group is indeed not supported for record.attach. As a workaround, you can add a custom document field to the Invoice Group Record and set its value to the file ID you want to attach. You may do that by following these steps: Go to Customization > Lists, Records, & Fields >…
-
Hello @Vernita, Good day. Locking the record via Workflow can be done by doing the following steps: Navigate to Customizations > Workflow > Workflows > New Input the following: Record Type: Project Task Workflow Name Events: On Create On View or Update Double-click State 1 Click on New Action Button Choose Lock Record…
-
Hello @User_Q1DPO, Thank you for posting in the NetSuite Support Community! Hello everyone! Your expertise and knowledge are greatly appreciated, and we ask that you kindly offer your support. Your participation and willingness to assist a fellow member are sincerely appreciated.
-
Hello @Rizkygaus, Good day. This might be due to this line: xml = xml.replace(/&/g, '&').replace(/</g, '<').replace(/>/g, '>').replace(/"/g, '"').replace(/'/g, ''');var renderedPdf = response.renderPdf({ xmlString: xml }); I input your script into Visual Studio Code and it immediately highlighted the line because you used…
-
Hello @User_REUC1, Good day! Following up on this in case you missed the previous comment from James. Let us know if you still need further assistance. Thanks!
-
Hello @Rizkygaus, Good day. Having the script in front of us would really help us troubleshoot more effectively. Could you please share a copy of version 2.1? Thank you.
-
Hello @kees.netsuiteadmin, This is expected, the createdpo field is not available in the Work Order record as of version 2025.1. However, I can there is an "itemsource" field available. Can you please check if this returns the internal id of the PO?
-
Hello @Sharna Kinsey, Yes, you will be using the internal ID instead. I found this post on StackOverflow providing the list of internal IDs for each country. https://stackoverflow.com/questions/43680785/setting-country-in-suitescript Please note that this is not Official NetSuite Documentation. I hope this helps! If you…
-
Hello @kees.netsuiteadmin, I wanted to check in to make sure you didn't miss my previous message. If you require any more help, please don't hesitate to reach out. If not, please let us know by clicking the “Yes” button for “Did this answer the question?” below, you’ll be able to help the community members who might have a…
-
Hello @Narayan Sharma, Good day. Following up on this in case you missed my previous comment. Let me know if you still need further assistance. Thank you
-
Hello @Stephanie Lange, Good day. I think it would be best to have someone from NetSuite Support to have a look into this issue as they are might have the tools to get to the root cause of this issue. You may file a case via SuiteAnswers.
-
Happy to help!
-
Hello @Stephanie Lange, Good day. Was there any recent change in your account that could have affected the integration? i.e. version upgrade to 2025.1, bundle updates.
-
Hello @Sharna Kinsey, Good day! Upon checking, the value for US is 230. But to ensure that you are using the right internal ID, you can perform the same validation in your browser. These are the steps: Press F12 Go to 'Console' type nlapiGetFieldValue('<your custom field ID>') Press Enter I hope this helps! If you find…
-
Happy to help!