Hi - is it possible to use a workflow to create an Opportunity from a Sales Order or another Opportunity? We currently have a couple of subscription-like products and our renewal process is cumbersome. They're subscription-like but not auto renewed. We currently use a saved search to export orders ready up for renewal - the search includes fields/formulas for the renewal - updated pricing, start/end date - and then we do a csv import to a new sales order. We're wondering if we can use a workflow to do something similar. I tried a quick test, and it seems if we do that we have to specify each field value, but we'd want it to be based in values from the saved search.

This might be possible. How many saved search values do you need to specify ?

Going by the import file, probably ~ 25 we'd need to populate. Alternate thought is not on a saved search but triggered when current Opp or SO is x months from Expiring - Copy it into new Opp and then do field updates. The updates would fewer fields - updated order name, product start/end dates, amount.

Yeah that would be the idea. Create a scheduled WF that would create a new Opp and copy over all the data that is able to be copied Then use a few dynamically sourced fields or formulas to populate the other fields Your deal breaker might be the items. Do you need to add items to your NEW Opp that you are creating?

We do. The same ones from the current Opp.

That might be a deal breaker for workflows. You cannot manipulate the items sublist on opportunities via WF. And you can’t transfer a Opp into another Opp either Could you use a Quote (estimate) instead?

Possibly - for new biz for one of the business lines, we already use opportunities and quotes to sales orders. We were thinking of moving the renewals from sales orders to opportunities. But we can look at quotes. Thanks for your insight and help!

Couldn't you write a WorkFlow action script to deal with the lines?

Hi - maybe, possibly? We don't have much internal experience with scripts - we've only written one custom script, as part of an integration to an internal system when we launched NS in 2019. We've avoided custom scripts where we can, in favor of workflow - or manual process - initially, with the intent to automate at a later date. Currently our dev resources are focused on other things, and we would be trying to implement this without affecting other projects. In your experience, from what I've described, would a workflow action script for the lines be a better solution than scripting the entire process? Thanks for your insight!

NetSuite has mentioned many times that there is no difference in performance between WF or script only a difference in the available functions it can perform so I think either scripting or workflow would have the same effect performance wise So it really comes down to on going maintenance. If you feel this process would need to be updated or changed periodically then a Custom action might be better so you can control the process yourself without having to rely on development resources However if the process is pretty static then having it scripted is probably not a bad idea Also if there is going to be a need for a lot of user interaction during the process (like button clicking, editing fields, etc) then a WF is better there However if it is mostly going to run on a schedule or in the “background” then a script is probably the better option Just a few thoughts, hopefully they help