Install the Salesforce package

Install the Salesforce part of Continuous Control from an install link. It works in production, sandbox, developer, trial and scratch orgs. You don't need an installation key or any other package first.

Demoing? Follow the demo install runbook.

This release is Continuous Control 3.4.1. It works with the NetSuite release ns-v3.3.1, so make sure your NetSuite account is on that release.

Check your org first

No org yet? Build a test org creates a scratch org with Revenue Cloud and the QuantumBit sample catalog, then installs the package.
Your org needs Revenue Cloud with Billing turned on. The package adds fields to Invoice, Billing Schedule, Credit Memo, Payment and related objects. If those objects are missing, the install fails.
Your orders can use the Order Type values Net New, Amendment and Renewal. This is optional. If Order Type is blank, the sync works out New or Amendment from the order's action.

Install the package

Find the current package version id on Versions & compatibility. It starts with 04t.
Log in to your org as a System Administrator.
Open the link for your org type, with the id at the end.
- Production, developer or trial org: https://login.salesforce.com/packaging/installPackage.apexp?p0=<package version id>
- Sandbox: https://test.salesforce.com/packaging/installPackage.apexp?p0=<package version id>
Choose Install for Admins Only.

Prefer the command line? Run this instead:

sf package install --package <package version id> -o <org alias> --wait 20

Every release uses the same links. Only the id changes.

Give people access

The package includes two permission sets.

Give Continuous Control to everyone who starts syncs or checks sync runs. That includes admins, integration users and finance users.
Also give Continuous Control Admin to whoever runs the Connection wizard or edits Calls & Mappings. It adds to the first set. It doesn't replace it.

The security model lists what each one contains.

A sync reads records as the person who starts it. So that person needs read access to every field you map in Calls & Mappings. For orders, that includes the Revenue Cloud fields, which come with your Revenue Cloud permission sets. A field they can't read is left out, and the run warns you which one.

Keep the NetSuite secrets private

The Connection wizard stores your NetSuite secrets in a Salesforce custom setting. One org setting keeps other users from reading custom settings.

In Setup, open Schema Settings.
Turn on Restrict access to custom settings if it's off.
Click Save.

With it on, only Salesforce admins can read the stored values. Syncs keep working for everyone with the Continuous Control permission set, because the app reads the secrets in its own code.

See what the package adds

What	Details
App and tabs	The Continuous Control app, with the NetSuite Connection, Calls & Mappings, NetSuite Calls, NetSuite Endpoints, Sync Runs, NetSuite Sync Runs and Performance Obligations tabs.
Record page cards	Continuous: NetSuite Sync for orders, invoices, batch runs, credit memos, payments, refunds, products and accounts. Continuous: Revenue Summary for contracts. You place them in App Builder. See Placing the components.
Flow actions	Twelve actions you can use in Flow. See the Flow actions reference.
Objects	NetSuite Sync Run, Performance Obligation, field mapping records and org settings. See Performance obligations.
Fields	The four sync status fields on each synced object, plus delivery, fulfillment and % Complete fields on order products.

Installing sends nothing. No data leaves your org until you finish the Connection wizard and someone, or a Flow, starts a sync.

Check the NetSuite version

Each Salesforce release needs a minimum NetSuite release. Step 4 of the Connection wizard reads your NetSuite version and flags one that's too old. See Versions & compatibility.