Census NetSuite syncs fail on sublist fields: case-sensitive, ScriptID not label

TL;DR: Use the NetSuite Schema Browser to confirm a field exists on the exact sublist (itemList, lineList, applyList), and for custom fields confirm it was created as a Transaction Line Field, not a body field. [Official Census docs (NetSuite sync troubleshooting)]: NetSuite sync errors almost always come from sublist fields. Sublist fields must be sent as arrays of objects, names are case-sensitive and must match the API schema exactly, and custom fields need the ScriptID (for example custcolexamplefield), never the label.

Census NetSuite syncs fail on sublist fields: case-sensitive, ScriptID not label

Fix

1. Use the NetSuite Schema Browser to confirm a field exists on the exact sublist (itemList, lineList, applyList), and for custom fields confirm it was created as a Transaction Line Field, not a body field. Expected: the request routes instead of erroring.

Details

[Official Census docs (NetSuite sync troubleshooting)]: NetSuite sync errors almost always come from sublist fields. Passed nil into T.must Context: Official docs (Census/Activations NetSuite sync troubleshooting): documents the most common source of NetSuite sync errors: sublist (line-level) fields. The error Passed nil into T.must

When to use

You hit exactly this: Census NetSuite syncs fail on sublist fields: case-sensitive, ScriptID not label in Census.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Census.

Root cause

means a configured field could not be found or resolved, usually a sublist field on the wrong record type or a recently added field not yet in the API. usually means a field could not be resolved.

Edge cases

• Sublist fields must be sent as arrays of objects, names are case-sensitive and must match the API schema exactly, and custom fields need the ScriptID (for example custcolexamplefield), never the label.
• Field names are case-sensitive, must match the API schema exactly, and custom fields must be referenced by ScriptID, not the display label.

Official docs (Census/Activations NetSuite sync troubleshooting): documents the most common source of NetSuite sync errors: sublist (line-level) fields. Field names are case-sensitive, must match the API schema exactly, and custom fields must be referenced by ScriptID, not the display label. The error Passed nil into T.must usually means a field could not be resolved. Resolved: [Official Census docs (NetSuite sync troubleshooting)]: NetSuite sync errors almost always come from sublist fields. Sublist fields must be sent as arrays of objects, names are case-sensitive and must match the API schema exactly, and custom fields need the ScriptID (for example custcolexamplefield), never the label. Use the NetSuite Schema Browser to confirm a field exists on the exact sublist (itemList, lineList, applyList), and for custom fields confirm it was created as a Transaction Line Field, not a body field. Passed nil into T.must means a configured field could not be found or resolved, usually a sublist field on the wrong record type or a recently added field not yet in the API.