[jmcadams]

The Expected Close Date field is a standard Netsuite field that’s value defaults to today’s date. There is nowhere in the custom form or Sales preferences where I can modify this so I am trying to set up a Workflow that empties the default date in the Expected Close field when an opportunity is created. Has anyone had any luck doing this?

Thanks

Jenny
This is a cached copy. Click here to see the original post.

[khultquist]

It’s tough to get a standard field to initiate the way you want. One strategy I’ve used iscreate a custom field that you can initiate the way you want
hide the standard field on all forms
create a simple script/workflow (beforesubmit) that syncs the two fields

[jmcadams]

Thanks for the info. Just curious what would be the benefit to the 3rd step of syncing the two fields if the standard field is hidden on the form?

---

khultquist replied on 04/06/2015, 10:07 AM: The standard field is still used in searches and reports, so you want to make sure you sync it.

[dmatyas]

Hi, there is simpler way. You can use workflow SetFiledValue as you wanted, but the empty value has to be set using formula. To formula field just enter empty string represented by two quotes ”. The Event Type must not be BeforeRecordLoad. The best is Before Record Submit.

Daniel

---

jmcadams replied on 04/09/2015, 02:24 PM: thanks. I followed your suggestion but when I hit save on a new opp record I get Notice (SuiteScript) – You have entered an Invalid Field Value ERROR: Invalid Expression for the following field: expectedclosedate

just wondering if this is what should be happening? I’m looking for a way to remove the default today’s date in the Expected Close Date Field. Its a required field but it prepopulates with today’s date so our Sales Reps are by basing this field.

[carl.billings]

Expected Close date is a required field and to not use it would remove one of your key drivers of the reporting. What would be the business use of not having an expected close? You could just set it to default to one year out if its blowing up your sales forecasting.

[jmcadams]

When creating a workflow does it matter where you set the condition at the workflow level or State/action level or both? I’m experimenting with the Show Message action. I thought I would try to generate a message when user hits Save on a new opportunity when Expected Close Date is today’s date.

---

dmatyas replied on 04/13/2015, 06:53 AM: Condition can be set only on Action or Transition (not on State). Comparing dates in SuiteFlow is bit tricky. You rather use formula instead of condition builder.

[al3xicon]

The “Expected Close Date” is set after the form loads, on a bit of a delay. My team wanted it cleared but still mandatory so that they would be forced to set it themselves. I managed to accomplish this by setting the field value to the aforementioned formula of ” (two single quotes), but the KEY is to set the Trigger On to “Before User Edit”. Hope this helps someone.

---

erik@extendtech.net replied on 09/21/2016, 06:28 AM: Thank you!

[Author]

Posts