Configurable calls
A call is one kind of sync, such as booking an order or syncing an invoice. You can change what any call sends to NetSuite, add your own objects to it, or build a new one. You do it all on the Calls & Mappings tab, with no code.
You need the Continuous Control Admin permission set to change calls. See the security model.
How a call is built
A call is a set of objects. Each object reads one kind of Salesforce record and writes one kind of NetSuite record. The editor also calls them nodes.
Objects sync in order, and a child sits under its parent. Take QuantumBit's Order Booking call. Order Line sits under Order, because each line belongs to an order. Billing Schedule and Billing Period sit under Billing Schedule Group.
Each object has its own field mapping rows. The rows say which Salesforce field fills which NetSuite field. Field mappings explains how rows work.
An object belongs to one call. So the same Salesforce object can send different fields on two calls, or be left out of one.
Pick a call to work on
- In the Continuous Control app, open the Calls & Mappings tab.
- Pick a call from the dropdown. Each one shows its name and version, for example "Order Booking · v4".
- The call's objects appear on the left, in the order they sync. Click one to see its rows.
The nine calls that ship come first in the dropdown. Calls you build come after them.
The nine calls that ship
Eight calls push data from Salesforce to NetSuite. One pulls data back.
| Call | What it does |
|---|---|
| Order Booking | Books an order, with its customer, contract, lines and billing schedules. |
| Invoice Sync | Sends posted invoices. |
| Credit Memo Sync | Sends credit memos. |
| Payment Sync | Sends payments and what they paid. |
| Refund Sync | Sends refunds. |
| Product Sync | Sends products as NetSuite items. |
| Customer Sync | Sends accounts as NetSuite customers. |
| Order Line Sync | Sends each booked line's delivery, fulfillment and % Complete. It sends a fixed set of fields, so there's nothing to map. |
| POB Refresh | Pulls performance obligations back to a Contract. |
Every object in each call, and the NetSuite record it writes, is listed in Shipped calls.
Choose what to change
| You want to | Go to |
|---|---|
| Turn off, rename or delete an object, or change which addresses you send | Change what a call sends |
| Put a call back the way it shipped | Reset to shipped defaults |
| Book orders as NetSuite Sales Orders | Book orders as Sales Orders |
| Send one of your own Salesforce objects with a call | Add your own objects to a call |
| Sync something no shipped call covers | Build a call of your own |
| Send a call to another NetSuite script or URL | Send a call somewhere else |
Edit a draft, then publish it
Your edits are saved as a draft. Syncs keep using the active version until you publish, so you can work on a call without affecting live orders.
Everything waits for you to publish. That includes the objects you add or remove, their rows, whether they're on, the NetSuite record they write, and the call's endpoint.
- Make your changes. The call shows a Draft changes chip.
- Click Validate. It checks every field and type. It also checks anything you added against your NetSuite account. You'll see a list of errors and warnings, grouped by object, and nothing is published. Anything about the call as a whole is listed under "This call".
- Fix any errors. Warnings don't stop you, but read them.
- Click Activate and confirm. The draft becomes the call's next version, and the chip turns green and reads Active. The next sync uses it.
Where to go next
- Field mappings covers the rows inside each object.
- Shipped calls lists every object in the nine calls.
- Anatomy of the payload shows what a call sends to NetSuite.