Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
REST API POSTing a nonInventorySaleItem- Tax Schedule Required
I'm still stuck on the pricing issue with saving a nonInventorySaleItem via Restlet, so I'm trying to create it via the REST API but getting an error. The data I'm sending is below, but I'm getting this error.
400 Bad Request
"Error while accessing a resource. Please enter value(s) for: Tax Schedule."
{
"costEstimateType": {
"id": "ITEMDEFINED"
},
"includeChildren": false,
"incomeAccount": {
"id": "262"
},
"expenseAccount": {
"id": "706"
},
"isFulfillable": true,
"isInactive": false,
"itemId": "AC-TEST-ITEM-1",
"taxSchedule": {"id": "1"},
"itemType": {
"id": "NonInvtPart"
},
"price": {
"items": [{
"price": 130.99,
"priceLevel": {
"id": "1"
},
"priceLevelName": "Base Price",
"quantity": {
"value": "0"
}
}]
},
"salesDescription": "Test description for this new product"
}
I found this link that I'm hoping isn't true, because it would really stink if the API requires a field that the API won't allow to be set.
Tagged:
0