This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

SCA doesn't allow cross origin requests which prevents it from integrating other third-party libraries/tools from front-end. Whenever a call is made to a cross origin, I see CORS error in the console.

Has anyone ever bypassed this issue and successfully made a request?

Make a request to a service/model/suitelet from your front-end and make your original request from the service/model/suitelet.

<@U4MF2CN20> Have you actually done this?

<@U5L945PD5> I'm integrating a third-party auto completion library that auto-corrects the keywords entered by users. The latency will go up with your suggested method as it involves 2 requests.

That's why I wantes to bypass the CORS issue directly from the website.

Thanks btw.

<@U4MF2CN20> Unless the api has changed, you cannot add server side headers without using netsuite's prefixed "Custom-Header" name.

This is from the docs: `addHeader(name, value) Adds a header to the response. If this header has already been set, this will add a new header to the response. Note that all user-defined headers must be prefixed with *Custom-Header* otherwise an SSS_INVALID_ARG error will be thrown ()`

I tried this with 2.x (a year ago) and it enforced the `Custom-Header` name even though it's not documented.

<@UBQQHJ2GG> <@UHWBKEMQ8> I took a look at the Suitelet I had created, and the header I added was for inbound requests from another domain into the Suitelet, so, No, I haven’t made any outbound requests..

FWIW, here are the headers I added for the inbound request:

`// Add CORS Headers`
`context.response.addHeader({`
  `name:'Access-Control-Allow-Origin',`
  `value: '<https://someawesomedomain.com>'`
`});`

`context.response.addHeader({`
  `name:'Vary',`
  `value: 'Origin'`
`});`

`context.response.addHeader({`
  `name:'Content-Type',`
  `value: 'application/json'`
`});`

Setting a CORS header on a Suitelet works now. I have not tried this in a SSP application.