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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
SuiteWorld | October 25–28, 2026 | Las Vegas Where our community gets ready for what’s next!
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
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