Set and Retrieve Date and Time Field Values in NetSuite

Learn how to effectively set and retrieve date and time field values using scripting functions in NetSuite CPQ Configurator.

·2 min read·7 views·View Oracle Docs

TL;DR

The setFormattedValue() and getParsedValue() functions are designed for efficiently setting and retrieving date and time values in NetSuite CPQ Configurator (version 1.9.0). These functions facilitate easier handling of date formats within your scripts.

How Do setFormattedValue() and getParsedValue() Work?

Introduced specifically for use within the NetSuite CPQ Configurator, the setFormattedValue() function converts a JavaScript Date object into a string format that matches the expectations of the answer record in NetSuite. Here’s how to use it:

Setting Date and Time

javascript
setFormattedValue('QUESTION_CODE', 'ANSWER_CODE', "text-purple-400">new Date());

This line of code will set the specified value using the current date and time. Ensure that you replace QUESTION_CODE and ANSWER_CODE with the actual reference codes pertinent to your implementation.

Retrieving Date and Time

To retrieve a date and time value back as a JavaScript Date object, utilize the getParsedValue() function:

javascript
getParsedValue('QUESTION_CODE', 'ANSWER_CODE');

This method helps in managing date formats more seamlessly, allowing developers to work within the JavaScript environment directly without conversion hassles.

Both functions are versatile and can be employed across both client-side and server-side scripts. When used with other field types, their behavior aligns with setValue() and getValue(), providing consistency across different data types.

Understanding Governance and Usage Units

In the context of the NetSuite CPQ Configurator, keep in mind the governance usage units for server-side actions. Below is a brief overview of how usage units are structured based on record type:

Record TypeUsage Units
Transaction records10 units
Custom records2 units
All other records5 units

When executing server-side actions, a total of 927 usage units are available due to the overhead needed to initiate the action. Understanding these limits is pivotal for optimizing script performance within NetSuite.

Who This Affects

  • Developers: Implementing date and time handling in scripts.
  • Administrators: Overseeing script performance and governance limits.
  • NetSuite CPQ Users: Utilizing date and time fields within configurations.

Key Takeaways

  • Use setFormattedValue() to set date and time values in an expected string format.
  • Employ getParsedValue() to retrieve date and time as JavaScript Date objects.
  • Understand governance limits and usage units for effective script management.
  • The functions can be used for both client-side and server-side scripting tasks efficiently.

Source: This article is based on Oracle's official NetSuite documentation.

Frequently Asked Questions (4)

Are `setFormattedValue()` and `getParsedValue()` functions specific to any NetSuite version?
Yes, these functions are specific to NetSuite CPQ Configurator version 1.9.0.
Is it necessary to convert date values when using `setFormattedValue()` and `getParsedValue()`?
No, `setFormattedValue()` and `getParsedValue()` handle date conversions internally, allowing you to work directly within JavaScript without manual conversion.
Do `setFormattedValue()` and `getParsedValue()` require any feature flags to be enabled?
The article does not specify any feature flags that need to be enabled for using these functions.
What are the usage units for executing server-side actions using these functions?
Usage units vary by record type: 10 for transaction records, 2 for custom records, and 5 for all other records. A total of 927 units is available due to action initiation overhead.
Source: Set and Retrieve Date and Time Field Values Using Scripts Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in SuiteScript

View all SuiteScript articles →