RE: REST Record Service (Beta) and REST Query Service (Beta) options removes?

The options to enable REST Record Service (Beta) and REST Query Service (Beta) in Setup > Company > Enable Features > SuiteCloud have disappeared. Have they been moved somewhere else?

RE: REST Record Service (Beta) and REST Query Service (Beta) options removes?

We’re now receiving error “The customer record is only available as a beta record. Enable the REST Record Service (Beta) feature in Setup > Company > Enable Features to work with this record”

We previously had REST Record Service (Beta) and REST Query Service (Beta) enabled

Thanks!

devmatt Rookie Asked on November 26, 2020 in SuiteCloud.

As a follow up to this, it seems to only be POST/PUT/PATCH requests that are throwing the error, GET requests to beta endpoints still work.   Can anyone provide more information on this please?   Thanks!

on November 27, 2020.

@devmatt, are your GETs still working against beta objects in Production?  If I disable the REST Record Service in the sandbox and try a GET against purchaseorder I am getting the same error as you above.  So just to confirm, based on your screenshot above you have no option to toggle Rest Record Service and yet GETs against beta endpoints are still working??

on December 8, 2020.
Add Comment
2 Answers

Hi,

There are some interesting things going on here. So, firstly, in 2020.2, NetSuite generally released REST Web Services with a tiny number of fully supported records. At the same time, they created those new features to cover the remaining Beta functionality.

In most accounts, I’m now seeing a blue information message saying that they’re no longer accepting new Beta testers for these features.

I’ve recently spoken with NetSuite who informed that this is a temporary measure whilst the Beta terms are reviewed. However, they have not provided any indication of when they might be available again nor confirmed whether they can be turned on by exception.

Thanks,

Chris

Intermediate Answered on November 27, 2020.

Thanks for the info Chris! I guess we’ll have to keep an eye out for when more functionality becomes available.

on December 3, 2020.

seems it broken for all endpoints. Even when using 2019_x it throws that error.

on December 17, 2020.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.