Deploying a NaCl change

Making a simple NaCl change

Let's start with a small change, like changing the description of a field

Concrete Salesforce example (click to expand)
  • Click the search button - the magnifying glass to the right of your workspace name
    • Make sure you're on the Files tab in the modal
  • Type accountcustomfields, and in the search results click the AccountCustomFields.nacl file to open it
  • Click inside the nacl file, then with your keyboard control/command + F to search text inside the file, and type description = to look for existing field descriptions
    • If one exists, let's edit that one
    • If one doesn't exist, choose any field, and inside the field definition block (inside the curly brackets) add a new line
    • You should end up with a line that looks like description = "test description" (replace "test description" with anything you like)

Example custom field with a description

salesforce.Picklist SLA__c {
  apiName = "Account.SLA__c"
  label = "SLA"
  _required = false
  valueSet = [
    {
      fullName = "Gold"
      default = false
      label = "Gold"
    },
    {
      fullName = "Silver"
      default = false
      label = "Silver"
    },
    {
      fullName = "Platinum"
      default = false
      label = "Platinum"
    },
    {
      fullName = "Bronze"
      default = false
      label = "Bronze"
    },
  ]
  restricted = false
  createable = true
  updateable = true
  queryable = true
  description = "test description"
  sorted = false
}
Concrete NetSuite example (click to expand)
  • Click the search button - the magnifying glass to the right of your workspace name
    • Make sure you're on the Files tab in the modal
  • Type entitycustomfield, and in the search results click one of the files under the entitycustomfield directory (files under this directory are named after the script ids of your netsuite custom fields).
  • Click inside the nacl file, then with your keyboard control/command + F to search text inside the file, and type description = to look for existing field descriptions
    • If one exists, let's edit it and set its value to "test description"
    • If one doesn't exist, lets add a new description = "test description" row (inside the curly brackets)
    • You should end up with a line that looks like description = "test description" (replace "test description" with anything you like)

Example entity custom field with a description

netsuite.entitycustomfield custentity_14 {
scriptid = "custentity_14"
accesslevel = "1"
appliestocontact = true
appliestocustomer = false
appliestoemployee = false
appliestogroup = false
appliestoothername = false
appliestopartner = false
appliestopricelist = false
appliestoprojecttemplate = false
appliestostatement = false
appliestovendor = false
appliestowebsite = false
applyformatting = false
availableexternally = false
checkspelling = false
defaultchecked = false
description = "test description"
displaytype = "NORMAL"
encryptatrest = false
fieldtype = "CHECKBOX"
globalsearch = false
isformula = false
ismandatory = false
isparent = false
label = "Checkbox Field 14"
searchlevel = "2"
showhierarchy = false
showinlist = false
storevalue = true
}

Make sure you don't have any validation errors, by clicking the validations panel toggle, at the top-right corner of the file editor view

Deploying the change

  • Click Deploy
  • In the Env Deploy preview you can review what Salto is about to deploy
  • Click Deploy to confirm
    • Salto will now make API calls to apply the changes you edited earlier
    • This can take several seconds to complete
  • Click Done to go back to the editor's default state
  • You can now visit your service's admin UI to confirm the change was done as expected
  • It's recommended to push your changes to Git now

πŸ‘

You've deployed your first change!

Congratulations, you just changed your service's configuration in an entirely new way. You have also completed the last step of Salto's getting started tutorial!

See below what we recommend next, explore our docs to learn more, and never hesitate to get in touch at [email protected].


What’s Next

Ready for more hands-on? Try getting started with Multi-env.

Want some more background? Learn more about envs, Multi-env, Git and more!

Did this page help you?