I’m dealing with an issue where deploying a custom transaction body field (

INLINEHTML

type) via SDF fails when the default value contains escaped HTML, despite being able to save the exact same value via the UI. Details: • The minified HTML is 1,266 characters long, while the escaped HTML used in the XML object for deployment is 1,468 characters long. • We can successfully save the custom field with HTML using the NetSuite UI in both Sandbox 1 (Version 2024.1) and Sandbox 2 (Version 2024.2). • When we attempt to deploy the field via SDF (with the HTML included as the default value): ◦ In Sandbox 1, the deployment fails with a generic “an error occurred deploying the project.” ◦ In Sandbox 2, the deployment succeeds with no issues using the same HTML default value. We could deploy the object with empty default values and then fill them in after release, but we prefer to track the HTML values directly in the repository for version control. Main Question: • Why would a deployment via SDF fail when we can save the same HTML directly via the UI? Is there a known limitation or difference in how SDF handles

INLINEHTML

fields with escaped HTML compared to the UI? Any guidance would be greatly appreciated, as we’d like to keep the HTML tracked in the repository

It's not directly SDF deploy related, but I just ran into this with setting the quantity on the inventory assignment line of inventory detail. It wants a max of 10 chars (including decimals it seems) when entering numbers but in the UI the same number works fine. Seems like its a netsuite bug which this may be as well. If you don't hear anything I would log it as a bug.