Does

Copy to Account

work for anything anymore?

I used it about a week ago to copy a workflow from SBX to Prod, and it pulled everything over, custom fields, saved searches, and the workflow. But then the same day I tried pulling over just a saved search and it did not work. So it works, just is very temper mental at times.

I can’t remember the last time it worked for me. I’ve been trying it on custom record types, searches, workflows, scripts, etc. I feel like I’m being gaslit. Or have Stockholm Syndrome or something.

it never worked for me except few reports

I just wish they would take the link away. It’s like Lucy and the football.

SDF works for the most part but not on workflows, reports, or integration records.

I actually had it work today 😂

did it ever?

Work for me the last time I tried (last year) to copy a script, workflow, saved search and custom fields

depends on what I guess. I regularly move fields and workflows successfully.

If you keep it simple it appears to do OK. A year or two ago it was great.

be careful even when it does copy over have had workflows copy over without error but once it's in production it doesn't match with what is in sandbox

i works well when have to copy Pdf template updates. it never worked when i try it on saved searches.

Yes be careful with Workflows, I've had it drop action groups and actions from the workflow, and conditions, too, in the transferred copy. I'm not sure what makes Copy to Account fail on some things and not others, but I suspect it may be the things that cause an SDF deployment to fail, things like Account-specific values, etc. (it doesn't seem to have trouble with adding dependencies)

be VERY careful with saved searches, if you have one with the same scriptid (e.g.

customsearch1

) on the source environment it will get overridden - even if it’s a totally unrelated search.

Good point! Copy to Account must be looking at the scriptid to decide whether to create a new customization in the target account, or modify an existing one. Best practice is to never keep the default scriptid of any customization, but use specific and consistent namespacing.

images.jpeg

Hey everyone, if you have Copy To Account specific issues, please email ns-platform_mb@oracle.com with detailed issues and the product team will respond. We're going to improve it! Subject:

Copy To Account issue via NSP - {companyName}

@Nupur Tandon please support translations. That's the usual error message that I encounter.

Hi @Luis, while supporting copying of Translations is not straightforward due to many factors, we're trying this as an immediate workaround: Leave behind the Translations Collections and not blocking the object & dependencies from being copied to target account. The translations need to be added manually in the target account if needed. What do you think?

@Nupur Tandon Yes. That's better than nothing. Actually, in our case, we don't really need the translations. They were just part of the NetSuite bundles/SuiteApps installed in our account.

Awesome, that is the validation we've been receiving through our interviews so awesome! Expect to see this change starting June 2025.

@Nupur Tandon thanks!