Hello @ONO4, You may refer to SuiteAnswer 30955 as a reference. This article provides the step-by-step instruction to deploy a client script to a Suitelet. Hope this helps! Your participation is valuable to our community. By selecting "Yes" for the "Did this answer the question?" option on the comment that addressed your…

Hi @ONO4, Good day! You could use the fieldChanged/lineChanged function in a client script and set a condition where if the ETA field is changed, run a for loop that would update the value of the entire sublist's ETA. You can utilize the N/record module's Record.getLineCount() to use as a limit for the for loop.

Hello @User_C6XDE, We're delighted that you're with us today! Thank you so much for opening this thread. Our experts are currently reviewing your issue and conducting their initial investigation. We'll be back in touch as soon as we have any updates for you. To our other community members, your input is always valued and…

Hello @Ron Mc We appreciate your submission of this new thread and kindly ask that you give our experts and community members time to review and evaluate your concern. We will respond to you promptly with additional information. To our community users, we highly value your contributions whether in the form of insights or…

Hello @Janakan, Good day! I have personally not tried using Azure for SSO, however, after some digging, some of the users who previously asked this found that removing the "claims" made their Azure SSO work for both Sandbox and Production. (reference: link). Please also review SuiteAnswers 85462. Thanks!

Hello @Patrick_AroHomes, To verify whether you're not being able to get the values for the sublist, can you please try to include this line in your code? log.debug("lineCount", bomRec.getSublistCount({ sublistId: 'revision' })); Thanks!

Hello @Paul Salkeld, Can you please try using HH:MM:SS instead? Thanks!

Hello @Janakan, Following up on this thread in case you missed my previous comment. If you need further assistance, please let me know. Thank you!

Hi @User_QL13N, Just following up on this. If you need further assistance, please let us know. Thanks!

Glad to hear it is working now. If you ever need help again in the future, feel free to reach out. We're happy to help. Have a good one!

Hello @Nickey, Glad to have you with us today. We appreciate your submission of this new thread and kindly ask that you give our experts and community members time to review and evaluate your concern. We will respond to you promptly with additional information. To our community users, we highly value your contributions…

Hello @Tiffany Haslerud, We're delighted that you're with us today! Thank you so much for opening this thread. Our experts are currently reviewing your issue and conducting their initial investigation. We'll be back in touch as soon as we have any updates for you. To our other community members, your input is always valued…

Hello @tmarck, Thank you for submitting this new thread. Please allow our experts and community members to review and examine your concern. We will get back to you promptly with further details. To our valued users, your contributions in the form of insights or suggestions are highly appreciated!

Hi @User_FL4CK, From the tables you mentioned, I think they missed checking transactionLine table. transaction table - transaction body fields transactionLine table - Item Sublist transactionAccountingLine - Accounts/GL Impact If your new field is a column in the item sublist, it should be present in the transactionLine.

Hi @User_1XIV8, I also tried and got the same result. As of now, there doesn't seem to be a way to create and delete new lines for the Opportunity record. Considering that the record type is in beta status as of now, it is possible that those features just are not ready yet. I am currently confirming this with our…

Hello @User_9Z6BE, Welcome to the NetSuite Support Community! I'm Nicole and I'm a part of the SuiteCloud team. From my experience, MODULE_DOES_NOT_EXIST is often rooted in the naming convention used for the files. For example, some users forget to add ".js" at the end of their file name, thus the error. In other cases, it…

Hello @Janakan, As of now, it is not possible to mix SSO and Non-SSO Roles together. This feature is put in place as an added security measure. However, what I can suggest is to have a duplicate of the Role/s you plan to use for both SSO/Non-SSO login. Please feel free to check out SuiteAnswers 82963 to learn more about…

Hello @User_QL13N, I've looked into this further and it could possibly be due to a permission error on the server end. Please have this checked with your server owner. Thank you!

It is also important to note that the Opportunity record is listed as a Beta record in our REST API Browser. It is subject to change and is not recommended to be used in the production environment. Have a nice weekend!

Hello @User_1XIV8, Thanks for letting me know! I did a little more digging and I was able to successfully update an opportunity item by using this request: The key is to add the item line to the request URL. Here's a breakdown of how I figured it out: 1. Run a GET request. This will show you what the record's current…

Hello @User_FL4CK, The table you're looking for is transactionLine table. transaction table contains the body fields while transactionLine contains the line items. As shown below, I have several custom columns in my table schematics for transactionLine table. I hope this helps!

Hello @ONO4, Just following up on this thread in case you missed it. Thanks!

@User_F5KU8, We appreciate your submission of this new thread and kindly ask that you give our experts and community members time to review and evaluate your concern. We will respond to you promptly with additional information. To our community users, we highly value your contributions whether in the form of insights or…

Hello @esabis, Good day. This error is considered a potential defect. We will be emailing you separately for your account information and will be creating a case record on your behalf. Thank you!

Hello @ONO4, Thank you for the clarification. I think I understand what you mean now. As of now, it is not possible to determine the record type based on field ID or field name as most transactions share the same fields. Some of the examples are 'entity', 'item', and 'account'. It would be difficult for NetSuite to…

Hello @User_1XIV8, Can you please try sending your request using this structure and let me know if it works? /opportunity/<internal_id> { "item": { "line" : 1, "quantity" : 5 } } Thank you!

Hello @User_QL13N, Bumping this thread in case you missed it!

Hello @Paul Salkeld, Were you able to try the solution I provided above? If you need further assistance, please feel free to let me know!

Hi @User_QL13N, First, we must ensure that the directory in the configuration is not the problem. Can you please check if yours follow this format? /directory/folder Alternatively, you can also try using other folders for testing purposes, if that is feasible on your end. Thank you!

Hello @Varonis inc., We're delighted that you're with us today! Thank you so much for opening this thread. Our experts are currently reviewing your issue and conducting their initial investigation. We'll be back in touch as soon as we have any updates for you. To our other community members, your input is always valued and…