bulk-jsonata-update

Audit and bulk-update NetSuite customer JSONata mappings with backups and verification.

6|6|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/Orderful/orderful-netsuite-skills --skill bulk-jsonata-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bulk-jsonata-update
Source: https://github.com/Orderful/orderful-netsuite-skills/tree/main/skills/bulk-jsonata-update
Command: npx skills add https://github.com/Orderful/orderful-netsuite-skills --skill bulk-jsonata-update

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents risky, manual drift when you need to apply the same JSONata mapping change across many customer-enabled transaction records in NetSuite, by enforcing an audit → plan → dry-run → verified deploy → rollback workflow.

Core Features & Use Cases

  • Fleet-wide JSONata rollout with guardrails: Audits every applicable enabled transaction record for a given document type, then applies exactly one transformation with explicit user approval.
  • Full backups plus deterministic verification: Creates per-record JSONata backups, generates per-record transformed outputs for diffing, and in live mode performs PATCH then SuiteQL read-back comparison.
  • Rollback support: Restores prior JSONata from the most recent audit backups using a restore script.
  • Safe change philosophy: Refuses to deploy without a dry-run + plan approval, avoids touching records the user excluded, and surfaces side findings like empty JSONata or lowercase userdefinedfields issues.

Quick Start

Instruct the assistant to run an audit for customer folder slug, target document type and direction, then ask it to perform a dry-run bulk JSONata transformation and show a diff for approval before any live deploy occurs.

Frequently Asked Questions about bulk-jsonata-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely bulk update JSONata mappings across multiple NetSuite customer transaction records?

To safely bulk update NetSuite JSONata mappings, you must follow an audit, plan, dry-run, and verified deploy workflow. This process applies a single transformation across all enabled transaction records while requiring explicit approval before any live changes occur.

What is the process for rolling out a JSONata mapping change to all enabled NetSuite EDI customers?

Rolling out JSONata mapping changes involves auditing all matching customrecord_orderful_edi_customer_trans records for a resolved document type, applying a deterministic transformation, and verifying changes via live PATCH followed by SuiteQL byte-for-byte read-back comparison.

Can I exclude specific customer records when applying a fleet-wide JSONata transformation in NetSuite?

Yes, you can explicitly exclude specific customer records from a bulk JSONata update. The safe change philosophy honors these exclusions and refuses to deploy without dry-run diff artifacts and explicit plan approval, ensuring excluded transactions remain untouched.

How does rollback work after a bulk JSONata mapping deployment in NetSuite?

Rollback works by restoring prior JSONata from the most recent audit backups using a dedicated restore script. The system creates per-record JSONata backups during the initial audit phase to ensure rollback readiness if the verified deployment produces unexpected results.

Why does my bulk NetSuite JSONata update refuse to deploy without a dry-run?

The bulk update refuses to deploy without a dry-run to prevent risky manual drift and ensure deterministic per-record transformations. This guardrail requires generating per-record transformed outputs for diffing and catching unsafe cases before any live PATCH execution.