inlinehtml is behaving differently on a project record compared to a sales order

AI generated answer (using internal Slack threads):

Based on the conversations, it appears that the behavior of Inline HTML fields can vary depending on the context in which they are used in NetSuite. In the first conversation, it is mentioned that the use of Inline HTML fields on Form pages (except for Forms generated by Suitelets) will be deprecated with a new user interface in NetSuite 2021.1 release. This could potentially explain why Inline HTML is behaving differently on a project record compared to a sales order. In the second conversation, the user is trying to create a hyperlink in an entity field on a project record. The user is advised to use the formula HTML column in saved search, but it is not clear if this resolves the issue. In the third conversation, a user is trying to set the value of an Inline HTML field on a Vendor Bill through a User Event (UE) script. The user encounters an error and is advised that they cannot submit the scriptContext.newRecord in an afterSubmit event, nor can they save a value in an inline HTML field. The user is advised to set a default value in the custom field page or set the value in a beforeLoad event if they need more dynamic behavior. The user then tries to get the Inline HTML field to print on an email template, but it shows up blank. The user is advised that Inline HTML is for use in the UI and not an option for email templates. The user is advised to use a regular field that stores its value for the email template. In conclusion, the behavior of Inline HTML fields can vary depending on the context and the specific NetSuite release. It is important to understand these nuances to effectively use Inline HTML fields in NetSuite. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******