Anyone know what happens when the owner of our bun...
# ask-stanley-ai
c
Anyone know what happens when the owner of our bundle is deactivated in NetSuite? Client reached out on support today saying the person who downloaded the NetAsset bundle is leaving the company and the user will be deactivated today. The user is listed as the owner of all of our custom records and transactions since they are the one that originally installed the bundle. Google says "the record will remain in the system but will not appear in lists or be selectable for new transactions as the deactivated owner will no longer be visible as an option; essentially, the record becomes "orphaned" and will need to be reassigned to an active user if further actions are required on it." Their system admin is trying to reassign all the records to a new owner, but ours are all locked so he can't update them.
c
AI generated answer (using internal Slack threads):
Based on the conversations, when a user who is the owner of a bundle is deactivated in NetSuite, the scripts, scheduled jobs, saved search reports, bundles, etc. that they deployed will continue to work. However, any jobs, for example, reports or scripts, that were scheduled by a user who is now inactive are not run. The jobs are still available, but the schedule is deleted. If the user has locked certain records or transactions, these will remain locked and cannot be updated without the user's permission. If the bundle was created in a sandbox, refreshing the sandbox could potentially cause issues. If you need to access the locked records or transactions, one workaround could be to change the email address of the deactivated user to an alias of your own and give that user access. Then you can log in as them and make the necessary changes. Please note that this is a workaround and may not be recommended by NetSuite. Always ensure to follow best practices and guidelines provided by NetSuite. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Slack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.845186055
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.843932509
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.836434901
Please provide your feedback on this answer.