NetSuite Transaction Record Configuration

NetSuite Transaction Record Configuration

NetSuite Transactions Records are the records that record all the business transactions you perform during your daily operations.  Examples of Transaction records are Sales Orders, Purchase Orders, Invoices and Payments.  NetSuite provides a list of native transaction types that you can utilize to represent the many types of transactions you will post while performing your normal operations.  Each transaction type interacts differently with entities and other transactions and has it's own unique functionality with regard to inventory and accounting impacts.  Furthermore, you can create custom transaction types to support more unique business interactions with more flexibility and customization available.  VERSITAL supports all native transaction types and custom transaction types.
Remember that VERSITAL reads directly from the information that exists in your Netsuite account so you can only display fields and information that has already been created.  If there are fields and functions that do not currently exist in your Netsuite environment you will need to build them first, then they will be available to display through a VERSITAL portal.  If you need help enhancing your transaction records you can review the NetSuite documentation OR reach out to us at support@mavencloud.tech.

Form Template Configuration

To start using entity records in a VERSITAL portal you will first need to create a form template that defines what fields are displayed and how each user can interact with those fields within the user site.
  1. In the VERSITAL admin console navigate to Form Templates


  2. Here you can select Edit from the list of existing form templates OR click Create to create a new Template.


  3. If creating a new Form Template, select the record type that you would like to create a template for.


  4. In the Form Builder screen drag fields from the list of available fields on the left into the form workspace on the right.


  5. If you would like to add multiple sections to your form layout use the "+" icon to add new sections.


  6. You can rename sections in your form layout by simply typing over the section name


  7. After you have added all the fields and sections you want, update the field level Display Type settings to define how each field interacts with the user site
    1. Display - the field will be displayed as normal and the user can freely edit and change the data
    2. Hidden - the field will be hidden on the form but any default value entered here will be used as new records are created
    3. Read Only - the data in the field will be displayed to the user, but it cannot be edited
    4. Mandatory - the field will be displayed as normal and the user can freely edit and change the data.  However, this field cannot be left blank.


  8. If you would like to define a default value, enter it in the Default field and when a record is created it will default to this value, but the user is allowed to change it depending on the Display Type settings you have selected.


  9. Your Transaction Record will most likely have multiple subtabs with different sublists of information.  You can switch between these subtabs and define which fields are displayed on each tab or sublist.  If you add a field to a subtab it will be shown in the user site.  If no fields are added the subtab will be hidden from the user site.


  10. Many Transaction Records have an Items or Expenses sublist that contains unique functionality for adding items or expenses to a dynamic list of items to be sold or purchased.  When working with the Items or Expenses sublist note that VERSITAL attempts to mimic core NetSuite functionality.  When selecting an Item in the list, the item description and price are automatically sourced into that line of the transaction.  Furthermore, you can continue to add more items into the sublist if required as the sublist can be dynamically added to and removed from.


  11. Once you have added all the fields and sections to your form, give your form a name, change the status to published and click Submit


VERSITAL only supports field sourcing for the Description, Units, Rate and Amount fields currently.  Any other sourcing or functionality deployed to the items sublist is not supported at this time.  All server side workflows and scripts are triggered when a record is created or updated, so any other field sourcing or values that need to be set, can be done so using a workflow or script that triggers when the record is being saved.

Portal Element Configuration

  1. Before beginning work on configuring the portal element, you should build a saved search for this record type that will define the "List View" in the user site.  The "List View" is the list of records displayed to the user that allows them to click on each record and view/edit it.  The columns and data displayed here are sourced from the results of the Saved Search you build.


  2. Once you have built the Saved Search in your NetSuite environment, take note of the Saved Search ID as it will be used later.  If you need help creating a Saved Search please review the NetSuite documentation on how to do so.


  3. Furthermore, if you want to dynamically filter the results of this saved search based on the user that is logged in you will need to find a field on the record that references your Entity list.  If one does not exist you can always add a List/Record field that is an Entity reference.  Once you have added this field take note of the field ID as you will need this later.
    If you need help creating custom fields please review the NetSuite documentation on how to do so.


  4. Lastly, if you would like to allow users to upload files to this record type create a Folder in your file cabinet and take note of the Folder ID, OR use an existing folder by noting the Folder ID of an existing folder.


  5. Now that you have these 3 supporting elements you can navigate to the Admin Console and go to your portal list


  6. You select the portal you would like to edit or Create a new portal


  7. Select the tab you would like this record to be displayed on OR create a new tab with the "+" icon


  8. Similar to the Form Builder you can rename the tab you added, create new sections within each tab and rename sections within each tab


  9. Using the records list on the left hand side drag the record type you want to add into the portal builder workspace


  10. Once added you can begin to configure the settings:
    1. Access Settings - Define how the user should be able to interact with individual instances of this record type
      1. Full - the user can freely edit, create and view records
      2. Edit Only - the user can only view and edit these records, but cannot create
      3. Create - the user can only view and create these records, but cannot edit
      4. Read Only - the user can only view these records and cannot create or edit
    2. Select Template - this is the form template that you built above (or any other existing form template for this record type)
    3. Search ID - this is the saved search you built above that defines the "List View" of this record type
    4. Filter by Entity - check this box to further filter the results of the List View according to the user who is logged in and what entity they represent (this requires the field ID of the entity field you defined above.)
    5. Field ID - this is the field ID of the custom field referencing the Entity list you created above.
    6. Allow export - check this box to allow users to export the List View into a CSV file
    7. Allow Make Copy - check this box to allow users to Make a Copy of existing records in the list
    8. Allow File Upload - check this box to allow users to Upload files to records in the list
      1. Allowed File Type - select from the list, the file types to be allowed in the upload process
      2. Max File Size - enter the maximum file size allowed to be uploaded.  (Size is referenced in Kilobytes (KB))
      3. Folder ID - this is the Folder in your file cabinet that will be used when files are uploaded.  This is the ID from the folder that you created above.


  11. Once you have configured your element click Submit Portal to save your changes.



The file upload feature is only supported by record types that support file attachments.  To be sure if the record type you are using can support file attachments, navigate to the record and look for the Communication subtab.  On the Communication subtab there should be a Files sublist.  If this exists you know file uploads are supported.





    • Related Articles

    • Transform Record Custom Element Configuration

      The Transform Record custom element can be a very powerful tool to help your organization cut down on unnecessary tedious tasks within Netsuite. You can provide a way for any native record transformation that Netsuite supports, to be triggered from ...
    • Pay Invoices Custom Element Configuration

      The Pay Invoices custom element allows users to view a list of open invoices, print each invoice and process a payment against 1 or multiple invoices in the list. Payment processing is supported by an easy to enable integration with your existing ...
    • Grid Order Entry Custom Element Configuration

      The Grid Order Entry custom element is an incredibly responsive and beautiful looking ordering interface for you customers. I mimics a modern ecommerce website and reads right from your Netsuite environment so all Item data and pricing is kept up to ...
    • NetSuite CRM Record Configuration

      NetSuite CRM Records - also known as Activities - are usually considered productivity records such as Tasks, Phone Calls, Events and Notes. NetSuite provides a list of native CRM record types that you can utilize to track and log the productivity of ...
    • NetSuite Custom Record Configuration

      NetSuite Custom Records are incredibly useful when you need to capture data that is specific to your business, but might not be supported by native NetSuite records. They can also be used to support custom business processes and supplement native ...