writing-inbound-jsonata

What problem does it solve?

Writing correct inbound JSONata for NetSuite’s Advanced Mapping is error-prone, especially when you must override defaults safely and populate custom fields using the non-obvious userDefinedFields structure.

Core Features & Use Cases

• Inbound 850 JSONata mapping authoring for the Orderful NetSuite SuiteApp, focused on Advanced Mapping for 850 Purchase Orders.
• Safe override workflow that starts from $defaultValues and overlays only the fields you intend to change using the transform operator pattern.
• Correct custom field writes via transaction.userDefinedFields (including the critical rule that the userDefinedFields object replaces rather than merges).
• Helper-powered lookups using pre-registered functions like $lookupContact, $lookupItems, and $lookupRecords to resolve contacts and item identifiers from raw Mosaic input.
• Date handling guardrails for custbody_/custentity_ date custom fields using the _textFields workaround so the Sales Order save doesn’t fail.

Quick Start

Ask for an inbound 850 Advanced Mapping JSONata expression that pulls the right contact and item details from the raw Mosaic payload and writes the needed custbody_* custom fields (including any required date fields) onto the Sales Order using $defaultValues and userDefinedFields.