I just reviewed the email that Oracle sent out “Reminder: SuiteCommerce Developer Tools Require Updates for Token-Based Authentication” and reviewed the help article “Token-Based Authentication Updates for Developer Tools” https://nlcorp.app.netsuite.com/app/help/helpcenter.nl?fid=article_9132912150.html. It appears that with this latest update, the .nstba file is being replaced with a .env file that lives in the SCA folder. Has anyone implemented the changes and can confirm this? The use of the .nstba file was convenient for switching between sandbox and production accounts. The use of the .env file will be like going backwards to the old .nsdeploy file.

@Keith Fetterman Great Info! I have not implemented myself but reading the article, it seems you are right, since we are gonna need to link manually the keys in the new .env creating a integration record (in the previous versions it was done automatically by the dev tools)

Hey @Keith Fetterman, I implemented this, and yeah, it seems like we're going backwards. In the .env file I keep two sets of keys and comment them back and forth. This is the same pattern as the "NetSuite Upload" extension that used to be available in vscode.

Hey @Chris, been a while. Thanks for confirming my suspicions. I use to keep two copies of the .nsdeploy before TBA was used. One was named .nsdeploy_prod and the other was .nsdeploy_sandbox. Then I would rename them to .nsdeploy when I was working with one or the other. I liked the TBA .nstba file better. 😞

I just stepped through the article--it appears that

~/.nstba

is still required. The last step in the process is to generate a new token for authentication. i.e. the new process requires

.env

+

~/.nstba