List of Functions

The following table classifies functions as client-side, server-side, or both. Any function marked with Yes in both columns is a universal function.

The table also contains information about governance usage units for server-side functions. Because NetSuite CPQ Configurator is a Suitelet, each server-side action can use up to 1,000 usage units. However, some units are used to launch the action itself, so the maximum usage units allowed for each server-side action is 927. Depending on the record type, the governance units used vary:

In the table, these units are referred to as record type units.

For more information about governance usage units in NetSuite, see SuiteScript Governance and Limits.

Function

Client-Side

Server-Side

Governance Usage Units

addBreakoutItem()

Yes

-

-

addLink()

Yes

-

-

addMaterial()

Yes

-

-

addMessageListener()

Yes

-

-

addRuleset()

Yes

-

-

ajax()

Yes

-

-

changeRuleset()

Yes

-

-

closeConfig()

Yes

-

-

copyRecord()

-

Yes

Record type units × 3

createEvent()

Yes

-

-

createRecord()

-

Yes

Record type units × 3

createRecords()

-

Yes

Record type units × 3 × Number of records to be created

createTable()

Yes

Yes

None

customizeUI()

Yes

-

-

deleteEvent()

Yes

-

-

deleteFile()

-

Yes

  • Deleting by id: 20

  • Deleting by name: 30

deleteRecord()

-

Yes

Record type units

evalRule()

Yes

Yes

None

findList()

Yes

-

-

getAnswerCode()

Yes

Yes

None

getAnswerDesc()

Yes

-

-

getAnswerLabel()

Yes

-

-

getAnswerName()

Yes

-

-

getAnswers()

Yes

Yes

None

getAnswersCodes()

Yes

Yes

None

getAnswerVariable()

Yes

-

-

getContextVariable()

Yes

-

-

getData()

-

Yes

  • Using the id parameter: Number of required record types × Record type units

    Process records with the same record type units

  • Without the id parameter: (Number of required record types ÷ 10) + 5

getEvent()

Yes

-

-

getEvents()

Yes

-

-

getFieldOptions()

-

Yes

Record type units + (Number of required options ÷ 10) + (Number of fields × 5)

getFromExternal()

Yes

-

-

getItemPrice()

-

Yes

(Number of price levels ÷ 10) + 5

getLineNum()

Yes

-

-

getMovDate()

-

Yes

None

getOrderData()

Yes

Yes

30

getOrderField()

Yes

-

-

getOrderItems()

Yes

-

-

getOrderSublist()

Yes

-

-

getParsedValue()

Yes

Yes

None

getProgress()

Yes

-

-

getQTable()

Yes

Yes

None

getRemainingUnits()

-

Yes

None

getRuleset()

Yes

-

-

getTable()

Yes

Yes

None

getTable().loadContent()

Yes

Yes

  • Dynamic tables: (Number of required tables ÷ 10) + 10

  • Static tables: 10

  • CSV tables: 20

  • Function-generated tables: none

getValue()

Yes

Yes

None

hasAnswer()

Yes

Yes

None

hideMessage()

Yes

-

-

hideModal()

Yes

-

-

isAnswered()

Yes

Yes

None

loadConfig()

-

Yes

  • Loading from the File Cabinet: 10

  • All other cases: 5

loadFavorite()

-

Yes

-

loadFile()

-

Yes

10

loadListKeyValue()

Yes

-

-

loadListWithArray()

Yes

-

-

nresolve()

Yes

Yes

None

priceMatrix()

Yes

Yes

See getItemPrice()

processItemCreations()

Yes

-

-

processRecordCreations()

Yes

-

-

queryParent()

Yes

-

-

readFiles()

Yes

-

-

recalcRulesets()

Yes

-

-

removeLink()

Yes

-

-

renderView()

Yes

-

-

reset()

Yes

Yes

None

resetTab()

Yes

-

-

resolve()

Yes

Yes

None

restartAction()

-

Yes

None

runAction()

Yes

-

-

runSavedSearch()

-

Yes

5

saveFile()

-

Yes

10

scopeApply()

Yes

-

-

scopeRefresh()

Yes

-

-

sendMessage()

Yes

-

-

setAnswer()

Yes

Yes

None

setDebugMode()

Yes

-

-

setFormattedValue()

Yes

Yes

None

setPicklistColumn()

Yes

-

-

setTab()

Yes

-

-

setValue()

Yes

Yes

None

showAudit()

Yes

-

-

showMessage()

Yes

-

-

showModal()

Yes

-

-

showPicklistModal()

Yes

-

-

sresolve()

Yes

Yes

None

startConfig()

Yes

-

-

submitConfig()

Yes

-

-

updateRecordFields()

-

Yes

Record type units × 2

updateTable()

-

Yes

12

validateAddress()

Yes

-

-

The getOrderData() function is available on the server only if the Submit to transaction page box is checked on the options record. This option sends configuration data to the transaction page after submitting the configuration. For more information, see Sending Data to the Transaction Page.

The methods of the table and qTable objects are available in both client- and server-side actions. You can obtain these objects using the getTable() and getQTable() functions, respectively.

Related Topics

General Notices