Hey guys! I'm trying to deploy SCA 2022.2 source c...
# suitecommerce
e
Hey guys! I'm trying to deploy SCA 2022.2 source code using node.js 12.21.0. I have to update the scriptId and deployId in the
distro.json
to overcome a previous error, after creating successfully the token and choosing the SSP Application, I'm getting the following error: (The integration record was created and I setup the keys in the .
env
file) Have you solved this issue?
The error comes from:
impl_upsertList2.js
{"status":[{"$":{"isSuccess":"false","xmlns:platformCore":"urn:<http://core_2020_2.platform.webservices.netsuite.com|core_2020_2.platform.webservices.netsuite.com>"},"statusDetail":[{"$":{"type":"ERROR"},"code":["UNEXPECTED_ERROR"],"message":["An unexpected error occurred. Error ID: ldnedmgkf4ealy0h3h5s"]}]}],"baseRef":[{"$":{"externalId":"app_manifest.json_0.0023606253502710395","type":"file","xsi:type":"platformCore:RecordRef","xmlns:platformCore":"urn:<http://core_2020_2.platform.webservices.netsuite.com|core_2020_2.platform.webservices.netsuite.com>"}}]}
Something is wrong with the dev tools when trying to communicate/create file in NetSuite.
@Steve Goldberg I do not like tagging you at all, I just want to see if you could check internally if something needs to be updated on the NetSuite scripts (Restlets, suitetalk web service) since I noticed that it is stating something for
core_2020_2
but I guess that should point to something like
core_2022_2
I had to change something similar but in the
distro.json
they were pointing to an older version.
s
I will spend some time looking into this later today
So it looks like there are multiple possible causes of an issue like this so I can’t really give you an answer. 1. Sometimes it just fixes itself 2. Checking you’re using the right versions of gulp and node 3. Upgrading to a newer version of SCA (2022.2.0 had an issue where file cabinet files were locked and this was fixed in 2022.2.1) 4. The domain is not linked to the SSP
Sorry. If you still get issues, raise a case
e
Ha! Thanks so much for all your input, we will raise the issue but your feedback is helpful specially bullet 3. 💪