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

I get an error too <https://netsuiteprofessionals.slack.com/archives/C42JX79UZ/p1622449040036500>

I’ve raised a support ticket with NS. I’ll update this thread once I hear back from them.

<@UK402CA1H>, exactly my issue.  Thanks.  Feel free to add me to that case

<@UK402CA1H>, I think I've discovered that the 'custsecret' object xml works the same way as the integration object xml.  You cannot deploy them against the same account you created them in, but they work otherwise.

I take that back (a little).  I included the custsecret in the SuiteApp package, and it was correctly installed ... however, attempting to deploy via SDF CLI it fails

<https://github.com/oracle/netsuite-suitecloud-sdk/issues/370>

Got it. Thanks Darren.

I’ll add this to the NS support case as well.

This 'issue' is killing us now.  We can no longer support multiple developers!  <@UEU3GRP5M> <@UAA1TMMTR> any ideas?

<@U5FHY30BV>, did the answer <@UFUCXSXCJ> provided in the Github issue solved the problem?

<@U5FHY30BV>

NS got back to me. We need to explicitly define the accounts that need access to in the `Test Accounts` field for the ones that are deployed using SDF.

This is automatically taken care when installed from the market place.

I’ve asked them that this is deviating from the point of having CLI and a market place. As there are 2 different paths.

Once a NS PM(<@UDAD1DZDF>) confirmed that deploying using CLI and marketplae would always be identical. And CLI can be trusted.

I’ll try and see if I can get them to create a bug for this. Chances are they won’t fix this.

<@UFUCXSXCJ>, unfortunately, that didn't work either ... I was really hopeful.  When I added the TSTDRV account, should I not see the secret in that TSTDRV account after the update?

I performed the update ... but still cannot deploy to `TSTDRV1381486`

An error occurred during custom object validation. (custsecret_chr_secret)
Details: Referenced secret: 'custsecret_chr_secret' is not available.
File: ~/Objects/custsecret_chr_secret.xml

The test account you added in `allow on test accounts`. Is the same account you are trying to deploy to?

And to answer your question. `Shouldn't i be able to see the cust secret after i update`
You will not see the custsecret simply after updating in UI. But it's for when you deploy in the account provided, it should accept it

So, yes .. the tstdrv you see listed is the target account I'm trying to deploy to