Connecting an environment to Salto
Setting up a Salto Netsuite environment (prod, sandbox, etc.) includes two parts:
Installing SuiteCloud Development Framework and creating an Oauth certificate
Salto SuiteApp installation and creating tokens for the Salto integration
Ensure that each of your NS environments has the following 6 features enabled:
OAuth 2.0
SOAP web services
REST web services
Token Based Authentication
SuiteCloud Development Framework
Create bundles with SuiteBundler
Detailed Netsuite environment setup instructions can be found here
Environment settings
To update the settings for a particular environment, navigate to the settings section where you will find:
General: where to update the environment name, setup the Scheduled fetch, and optionally mark an environment as "sensitive"
Application Connections:
credentials used for fetch and deploy (Note: make sure you have set up "Personal credentials" in the environment ahead of starting a deployment)
The Salto adapter config file. (Note: not all types are fetched by default, review the Supported Metadata types docs page. Also review the fetching custom records documentation)
Version Control: Git connection for the environment 🎥: Git for Salto users
Monitor changes: where to set up custom notifications (see below)
Fetch types
There are three types of fetches in Salto:
Full: fetches all configuration updates for the environment (the scheduled fetch uses a full fetch)
Change-Based Fetch: Only fetches the elements that have changed since the last fetch. (Note: due to NetSuite API limitations, Salto cannot fetch certain updates to some metadata types. Review our documentation to see if a full fetch is required.)
Custom: Optionally targets 1 or more specific metadata types to fetch
Impact Analysis
The explore page in Salto is used to explore your configurations, see dependencies and understand where and how configurations are used.
Monitoring changes
Set up notifications to alert when changes are made in production.
Comparison Overview
Here is an overview of the comparison screen showing you the differences between two environments, part of the compare and deploy process.
Changelog
Salto automatically keeps track of all changes made to each environment in the Changelog.
Backup and Restore
Through the scheduled fetch, Salto will automatically backup the configurations for each environment. Those backups can be used through the restore process to revert any changes made directly in the environment. 🎥 * Ex: Bringing back deleted workflows, saved searches with Salto
Deployment types
There are different types of deployments in Salto
Compare & Deploy: Choose which changes to align between any two environments.
Find environment changes & deploy: Choose the changes made during a specific time period to deploy into another environment. Especially useful when deploying from a shared environment.
Deploy from Pull Request: Initiate a deployment in Salto based on the changes contained in a Pull Request in an SDF repository
Promote a deployment: used to promote the same set up changes to another target environment. (ex: after deploying a set of updates to a form in
UAT, promoting those same changes up toProduction)Revert a deployment: Revert all changes made in a specific deployment (Note: to revert specific changes, use the restore process mentioned above)
Deployment examples
Comparing and deploying a custom list
A 3-minute walkthrough of the compare and deploy process using Salto to deploy a new custom list
Deploying forms and saved searches
A detailed walkthrough of deploying forms and saved searches from sandbox to Production using Salto.