You do not need to set the form as Preferred if you only need a specific role to use it. So, just configuring the Role record would suffice. For other roles that were not configured, the form currently set as Preferred will be used. Hopefully, this clarifies things. -Jack

@User_75YL8, Yes, the Preferred Form applies to all users. If you need only a specific role to use the form, configure the Role record itself to restrict the form to that role. See the sample screenshot below: Related SuiteAnswers Article: 91081: Setting Default and Restricted Forms If you find this reply to your question…

Greetings @User_75YL8, Based on your screenshot, it seems that the template you created was not set as Preferred so a different form is being used when viewing Vendor records. With that said, can you try enabling the Form is Preferred option indicated in your screenshot below: -Jack

Hi @ksage, Were you able to check our latest suggestion above? -Jack

Hi @Gert Van Damme, Do you still need assistance with this inquiry? If so, we would appreciate you providing the additional information we requested in the previous post. -Jack

Greetings @Manish_Mohan, Testing the behavior in the UI which also applies to SuiteScript, it seems that only the Originating Entity Type is available in the Name (id: entity) dropdown in the Journal Entry Lines sublist. See the sample screenshots below: I haven't found any related documentation and Enhancement Requests…

Greetings @Gert Van Damme, For the requirement you specified in #3, do you only pertain to printed transactions? If so, should the cost of packaging be deducted from the printed transaction amount? -Jack

Thanks for checking, @ksage. As the capability of our script here suggests, it is possible that another script deployed on Sales Orders with a similar function might be conflicting with our script on setting the Status of the Opportunity. So, also check the existing scripts deployed on Sales Orders just in case. -Jack

Thanks for confirming, @jlbriggs. To rule out caching issues, can you check if the missing Custom Record will become available if you create a Dataset under Incognito mode/Private Browsing mode of your browser? -Jack

Greetings @jlbriggs, To confirm, are you trying to access the related Custom Record Type from the dataset of the other Custom Record Type, or are you trying to create separate datasets for each record type? -Jack

Greetings @Audrey G., Thank you for posting a new inquiry here in NetSuite Support Community. Tagging our gurus @Dominica Sevilla-Oracle and @Elychelle Gulen-Oracle who might be able to help you out on this one. To other members who have any ideas, feel free to share them here. -Jack

Thank you for providing the case number, @User_JN952. The community would also appreciate if you could provide updates here throughout the case resolution. -Jack

Thanks as well for the update and providing those details, @Varonis inc. Good to know that support is already on the case with this issue. -Jack

Greetings @Varonis inc., For unexpected errors, it is recommended to file a case with NetSuite Customer Support as they are the only ones who have access to the error logs and other details for such errors. Additionally, to fast-track their search for the appropriate details, kindly include the Error Ticket indicated on…

Hi @ksage, Were you able to check our suggestions above? -Jack

Greetings @Kedalene, Thank you for sharing your concern here in NetSuite Support Community. Upon checking, there is an ongoing issue right now on some accounts, preventing users from logging in. The following defect has been filed for this: Defect 721004: Unable to access Netsuite Account Currently, the defect is set to…

Greetings @Casey_Long_, I have redacted the sensitive information such as your Account Number and Company Address on your behalf from the attached screenshots on this thread. Please be reminded to check this for every thread that you post. Anyway, for the Image Files used in printed forms and mail merge, it is recommended…

Greetings @Kedalene, Thank you for posting a new inquiry here in NetSuite Support Community. Tagging our gurus @Patrick Fresnosa-Oracle and @Clarisa De Torres-Oracle who might be able to help you out on this one. In the meantime, you might be interested in participating in our Question of the Week. You only have until…

Greetings @ksage, Upon testing your script on my end, the value set by the script in the Status field on the Opportunity persisted, and it is not being closed after, unlike the behavior you described. With that said, there could be something else that automatically closes the Opportunity on your end. It could be another…

You're very welcome, @Tybrneryan! Glad we could help 😀 By the way, you might be interested in participating in our Question of the Week. You only have until tomorrow, May 18 at 2 PM EDT to comment on your answers and earn rewards! Click here for more details. -Jack

Alright, thanks for confirming @Amjad Kasem! 😃 Glad to hear that it all worked out. -Jack

Greetings @Tybrneryan, Upon checking, the Components sublist on Assembly Item records that are available only without the Advanced BOM feature is not customizable. However, there are available workarounds depending on your preference which are as follows: 1. Enable the Advanced BOM feature and customize the Components…

Thank you for the feedback, @Amjad Kasem! Just to clarify, are the issues here already resolved? -Jack

@Amjad Kasem, To show the hidden Subsidiary field, set the Default Access Level for the field to View or higher under the Access subtab on the Field Settings page. See the sample screenshot below: And to resolve the latest error you encountered, try using record.setValue() method instead on setting the Status field as…

Hi @Amjad Kasem, The latest script you provided looks good to me except for the part on setting the Subsidiary field. In my previous post, I notified you as follows about the error on the Subsidiary field you encountered: Additionally, I received another error after applying the fix described above related to the hidden…

Hi @Amjad Kasem, Upon testing in the Internal QA Environment of your account, I have identified the cause of the error, which is the usage of the wrong Custom Record ID for the record type loaded and updated within the For loop. The correct ID is 'customrecord_expodya_recive_item' and the script should be revised at the…

Greetings @sonisons, Thank you for following up on this thread. I will answer your question on Pauline's behalf. For your particular scenario, see the suggested solution provided in the following related thread: Let us know if you have further questions. -Jack

Thanks for confirming @Amjad Kasem. We will investigate the error further on our end and will get back to you once we have an update or need additional information. -Jack

Thanks for providing the case number, and apologies for not responding sooner, @Thomas UPF. As far as I know, since the data on a Sandbox account is based on Production data, you also need a Non-OneWorld Production account to have a sandbox without OneWorld. Hope this helps. -Jack

Thanks for the update @User_JN952. Since the same search and script you have are working fine on Vendor Records during my testing, and I was not able to reproduce the same error, it seems that looking into your account directly is necessary to troubleshoot further and determine the cause of the error. With that said, we…