Shipped calls
Nine calls ship with the package. This page covers what each one is, where it runs from, and which NetSuite record type every node writes to. Read it before you change anything in the call editor.
The nine calls
| Call key | Name | Root object | Action | Method | Flow action | Card surface |
|---|---|---|---|---|---|---|
order_booking | Order Booking | Order | book | POST | Book Order to NetSuite | Order record page |
invoice_sync | Invoice Sync | Invoice | invoices | POST | Sync Invoice to NetSuite · Sync Invoice Batch Run to NetSuite | Invoice and Invoice Batch Run record pages |
credit_memo_sync | Credit Memo Sync | CreditMemo | invoices | POST | Sync Credit Memo to NetSuite | Credit Memo record page |
payment_sync | Payment Sync | Payment | payments | POST | Sync Payment to NetSuite · Sync Payment Batch Run to NetSuite | Payment and Payment Batch Run record pages |
refund_sync | Refund Sync | Refund | refunds | POST | Sync Refund to NetSuite | Refund record page |
product_sync | Product Sync | Product2 | items | POST | Sync Product to NetSuite | Product record page |
customer_sync | Customer Sync | Account | customer | POST | Sync Account to NetSuite | Account record page |
order_line_sync | Order Line Sync | OrderItem | orderlines | POST | Sync Order Lines to NetSuite | Sync Order Lines on the Order record page's sync card |
pob_refresh | POB Refresh | Contract | pobs | POST | Refresh POBs from NetSuite | Refresh from NetSuite on the Revenue Summary card |
The action and method above are the defaults. You can override either one per call, along with the URL, in the endpoint editor. The Flow actions are catalogued with their inputs in Flow actions.
Every one of the nine envelopes carries orgBaseUrl and orgId, the two keys behind NetSuite-to-Salesforce deep links and the Source Org stamp. On Payment Sync, Refund Sync, and Credit Memo Sync, each application-child row also carries its own sfId. A landed credit memo gets the same custbody_cc_sf_url deep link a payment does. See Anatomy of the payload for the full envelope shape.
Reading the node tables
Default target is the NetSuite record type the node ships with. Alternates lists what else the node can point at in this release. A node marked fixed keeps its target because its NetSuite writer is built for that target alone. Any node can still be renamed or switched off. Any node except the call's root can be deleted, as long as you delete its children first. See Editing and removing shipped nodes.
Wherever "any transaction" appears, it means six choices. Sales Order, Estimate, and Return Authorization don't post revenue. Invoice, Cash Sale, and Credit Memo do, the moment NetSuite saves one, so the picker holds those three behind an acknowledgment.
The item choices are non-inventory, service, other charge, download, and inventory.
The Order node's picker also offers custom record. That's the way back to customrecord_cc_order after a re-point. The packaged RESTlet only writes that record or a native transaction there. Pointing it at any other custom record type gets refused with one error, and the Order section is skipped.
Order Booking
| Node | Salesforce object | Default target | Alternates |
|---|---|---|---|
| Customer | Account | customer | fixed, but can be switched off. A bare reference still links the graph |
| Product | Product2 | noninventoryitem | any item type |
| Contract | Contract | customrecord_cc_contract | fixed this release |
| Order | Order | customrecord_cc_order | any transaction, or back to a custom record. See Native transaction targets |
| Order Line (child of Order) | OrderItem | customrecord_cc_order_line | follows Order to its line sublist |
| Billing Schedule Group | BillingScheduleGroup | customrecord_cc_bs_group | fixed this release |
| Billing Schedule (child of the group) | BillingSchedule | customrecord_cc_billing_schedule | fixed this release |
| Billing Period (child of the group) | BillingPeriodItem | customrecord_cc_bs_period | fixed this release |
| Billing Address (child of Customer, packaged) | Account | customer.addressbook | fixed sublist; object, relationship and rows editable |
| Shipping Address (child of Customer, packaged) | Account | customer.addressbook | fixed sublist; object, relationship and rows editable |
The two address objects are packaged. The product ships them, and everything about them is yours to change. See Addresses are nodes.
Re-pointing Order to a Sales Order moves Order Line to salesorder.item automatically, in the same save. Nothing else is needed, and there's no line node to add. The editor shows this before, during, and after the save. See Native transaction targets.
Invoice Sync
| Node | Salesforce object | Default target | Alternates |
|---|---|---|---|
| Invoice | Invoice | invoice | fixed |
| Invoice Line (child of Invoice) | InvoiceLine | invoice.item | fixed |
| Billing Schedule Group | BillingScheduleGroup | customrecord_cc_bs_group | fixed this release |
| Billing Schedule (child of the group) | BillingSchedule | customrecord_cc_billing_schedule | fixed this release |
| Billing Period (child of the group) | BillingPeriodItem | customrecord_cc_bs_period | fixed this release |
The billing nodes are here because a synced invoice refreshes the billing mirrors it consumed. See Billing mirrors.
Credit Memo Sync
| Node | Salesforce object | Default target | Alternates |
|---|---|---|---|
| Credit Memo | CreditMemo | creditmemo | fixed |
| Credit Memo Line (child) | CreditMemoLine | creditmemo.item | fixed |
| Credit Memo Applications (child) | CreditMemoInvApplication | creditmemo.apply | fixed |
Payment Sync
| Node | Salesforce object | Default target | Alternates |
|---|---|---|---|
| Payment | Payment | customerpayment | fixed |
| Payment Applications (child) | PaymentLineInvoice | customerpayment.apply | fixed |
Refund Sync
| Node | Salesforce object | Default target | Alternates |
|---|---|---|---|
| Refund | Refund | customerrefund | fixed |
| Refund Allocations (child) | RefundLinePayment | customerrefund.apply | fixed |
Product Sync and Customer Sync
| Call | Node | Salesforce object | Default target | Alternates |
|---|---|---|---|---|
| Product Sync | Product | Product2 | noninventoryitem | any item type |
| Customer Sync | Customer | Account | customer | fixed |
| Customer Sync | Billing Address (child of Customer, packaged) | Account | customer.addressbook | fixed sublist; object, relationship and rows editable |
| Customer Sync | Shipping Address (child of Customer, packaged) | Account | customer.addressbook | fixed sublist; object, relationship and rows editable |
Customer Sync carries the same two packaged address objects as Order Booking, for the same reason: wherever a customer is written, its addresses are rows on that customer. See Addresses are nodes.
Order Line Sync
Order Line Sync has no nodes and no mapping rows. It sends a fixed set of fields for each booked order line: Delivered, Delivered Date, Fulfilled, Fulfilled Date and % Complete. You can't add objects to it.
It updates the RC Order Lines a booking made, then refreshes that contract's obligations. It runs from the Sync Order Lines button on the order's sync card, and from its Flow action. It's deployed and activated in step 6 like the others. See Recognition methods.
POB Refresh
POB Refresh has no nodes and no mapping rows. It reads from NetSuite instead of writing to it, and everything it does is built in. It still appears in the call list, has a version and an endpoint, and is deployed and activated in the wizard's step 6. See Writebacks & the POB mirror.
Adding to this list
Calls you build yourself sit alongside these nine. They get their own keys, nodes, endpoints, and versions, and they run from the generic Run NetSuite Call Flow action or from a sync card on their root object.
Only the nine above can reset to shipped defaults, since only they have shipped defaults to go back to.
Your own call can root on a custom record, a standard transaction, a customer or contact, or an item type. Standard transactions include Sales Order, Estimate, Invoice, Cash Sale, Credit Memo, and Return Authorization. See Configurable calls.