Change what a call sends
Every object in a shipped call is yours to change. You can turn one off, rename it, delete it, or change where it reads its data. This page shows how, using the objects that ship.
Each change is saved as a draft. Nothing reaches a live sync until you validate and activate the call. See Edit a draft, then publish it.
Turn off, rename or delete an object
Open Calls & Mappings, pick the call, and click the object. The controls sit at the top of the object.
| To | Do this | What happens |
|---|---|---|
| Rename it | Click Edit node and change the Display name. | Only the label changes. Past runs and NetSuite records aren't affected. |
| Turn it off | Flip the Mapping active switch to Inactive. | The next sync sends no records of that type. NetSuite skips that part of the sync. |
| Delete it | Click the delete icon, read the preview, and click Yes, remove it. | The object and its rows are removed. NetSuite keeps the records it already has. |
Some objects depend on others. An order line needs its order, and a billing period needs its schedule and group. If you remove one that another needs, Validate names both and Activate is blocked.
Customer, Contract and Product are different. You can turn them off, and Validate only warns you. The sync still links each order to the customer, contract and items NetSuite already has. A record that has never been synced to NetSuite stops the run before it starts, and the error names it.
You can't delete the call's first object, or an object that still has children. Delete the children first. To move an object under a different parent, delete it and add it again. Its rows go with it, so you'll need to add them again too.
Choose which addresses you send
Addresses are objects too. Billing Address and Shipping Address sit under Customer on Order Booking and on Customer Sync. Each one writes one row in the NetSuite customer's address book.
They ship ready to use. They read the Account's billing and shipping address fields, and you can change every row. Here's what Billing Address sends:
| NetSuite field | Filled from |
|---|---|
| Label | The word "Billing" |
| Default billing address | Always yes |
| Address 1 and Address 2 | Billing Street, split into its first line and the rest |
| City, State, Zip | Billing City, Billing State, Billing Zip/Postal Code |
| Country | Billing Country, sent as a code such as US |
A few rules keep addresses tidy:
- The label is how NetSuite finds the address next time. Keep a label row on every address object, or a re-sync adds a second copy. Validate tells you if one is missing.
- An account with no street and no city sends no address.
- If you clear a field in Salesforce, the next sync clears it in NetSuite. Country is the exception. A blank country is never sent.
- NetSuite never deletes an address. If you turn an address object off, NetSuite keeps what it has.
- If you remove one of the two objects, a customer with only one address uses it as both defaults.
Read addresses from another object
Say QuantumBit keeps customer addresses on ContactPointAddress records, one per address type. Here's how to send those instead.
- Click Billing Address, then Edit node.
- Set Salesforce object to ContactPointAddress.
- Set Relationship field to
ParentId, the lookup to the Account. - In Only sync records where…, enter
AddressType = 'Billing'. - Save. Any row whose Salesforce field doesn't exist on ContactPointAddress is flagged.
- Point each flagged row at the matching ContactPointAddress field: Street, City, State, PostalCode and Country. Keep the transforms. Leave the label and default rows alone.
- Do the same for Shipping Address, with
AddressType = 'Shipping'. - Validate and activate the call.
Send a third address
Click the Customer object and click Add address object. The Add object wizard opens with Customer as the parent. Pick the Salesforce object, set the relationship and a filter, and give the address its own name and label. Each label writes its own row. Add your own objects to a call explains the wizard.
Put a call back the way it shipped
If you've changed a shipped call and want to start over, reset it.
- Pick the call, and click the pencil beside its name. It's labeled Edit call settings.
- Click Reset to shipped defaults… at the bottom left.
- Read the list of what will be undone. A call you haven't changed says so.
- Click Yes, reset.
The reset publishes right away, so the version number goes up by one. A reset can't be undone. It doesn't touch your sync history, your base field mappings, or any other call.
A call you turned off comes back on after a reset. Turn it off again afterwards if you need to.
You can also reset calls from step 6 of the Connection wizard. Calls you built yourself have nothing to reset to.