<https://netsuite.custhelp.com/app/answers/detail/...
# suitescript
c
j
Although Sandbox and Production are two independent environments, this is a standard behavior and not a defect.
😆
netsuite 1
😂 1
c
Right???
But….why
s
it is a defect, no matter what they choose to say. A 'sandbox' by definition is isolated from anything else.
a
Hello! This thread got my attention. Can you guys quickly explain to me why this synchronization with Sandbox and Production is a bad idea? What are the use cases/flows that are impacted by this synchronization?
I would appreciate your feedback here so we can understand a bit more your experience
Thank you!
s
My general preference (and how every other system I've worked on over the decades handles it) is anything related to production should stay in production and not be affected by the presence (or lack thereof) of sandbox or other account(s).
I'm curious as to how this behavior is useful for any workflow? I'm struggling to think of a scenario where I'd want to update something in sandbox and have it automatically apply to production, potentially breaking production?
c
hi @Albert Margarit (NS Eng Lead)! The general rule as I understand it is that sandboxes and production are 100% isolated from one another - users can feel safe testing emails, transactions, etc, without any risk of accidentally firing something off in production. I’ve been using NS for 7 years, but this is the ONLY instance where I’ve seen the rule broken…and I initially found it when we accidentally took our entire production order fulfillment process offline by resetting the integration record in sandbox 😞 🤦🏻‍♀️ (we had a sync to a custom licensing server that would send a key to the user as soon as the sales order was processed). This happened to me right after the feature was first introduced, and it wasn’t documented in suiteanswers yet, so it took days for us to find the error and get our licensing process back online. I imagine people probably make this mistake a lot, and knock out critical production processes with what should be a ‘safe’ sandbox change
at the very least, I’d love to see a screaming “ARE YOU SURE YOU WANT TO DO THIS” type error message before resetting the records in sandbox, so users are aware of the potential for prod impact
a
I see, agreed. What was the use case for resetting the integration record?
c
users were doing some testing, I believe engineering was making changes to the staging licensing server so we were asked to reset that connection
s
@Albert Margarit (NS Eng Lead) any insight on why this one-off sandbox-sync-to-prod was put in place in the first place? What is the use case where this would be desirable?
a
unfortuantely I don't know. I think the goal was to make your life easier but that not be the case. I transferred your feedback to the corresponding team. I would recommend if you guys can create an enhancement request and get others to do the same
I know it's not the best answer but it would help us a lot if you guys do that
s
can you remind me where I create an enhancement request?
a
I guess you should create a case, explaining why this behavior is problematic.
c
thanks @Albert Margarit (NS Eng Lead)! Appreciate you taking an interest, this has always been totally mystifying to me 🙂 I definitely created a case years ago when I first found it, which was converted into an enhancement, so hopefully others can add onto that
a
Yep, do you have by any chance the case id? That would be helpful