Hey Guys, Scratching my head on this one ... Looking for a Workflow method to capture the existing (Old Record) Exp Ship Date from an Item Line on a Sales Order into a Custom Trans Line Field - Previous Exp Ship Date. However, you aren't able to Set Field Value in a Sublist Action Group triggered by Before Record Load, Old Record is only available as a Condition, and Workflow Fields and State Fields appear to only be at Record level, not one per Line Level. From this I can then compare the (Current Record) Exp Ship Date != (Current Record) Previous Exp Ship Date, and send the Customer an email "Your Exp Ship Date has been updated from [old date] to [new date]".

Can you just make a custom field called previous ship date On create have an action to set previous ship date = ship date Then on edit if previous ship date != ship date then create a transition to a new state In the new state send an email for ship date changed then set previous ship date to equal ship date (both on entry)

I feel there's a gotcha in there I've encountered, but given I'm now cross-eyed maybe not. Will give it a go.

I think the transition based on line level data might be problematic but if you make a saved search criteria for the transition that should do it

gotcha might be that whatever is changing your exp. ship date potentially not triggering the workflow? Then workflow only gets triggered (and sends email to customer) when a user next edits/saves the sales order

@MGBC @David B it's retrieving the prior ship date (red) that's getting me confused (gotcha'd)...

are you still trying to do this in beforeload? in a UE, only beforeSubmit and afterSubmit have access to the old record, presume workflows are the same/similar

All BeforeSubmit

I've done what MGBC's suggested, which is to create a custom transaction line field to hold the previous ship date.

Yep, also got that - but how to populate is the conundrum

right, with workflow.... you're having trouble setting a column field

Can reference Old Record in Condition, but not as target of Set Field Value

wait, you're trying to set the 'prev. ship date' field in the old record?

Nope. Retrieve the value of the old record ship date to populate current record prev ship date.

right, I think I've got it now. *brb

My original idea, was the last point However I don't think that workflow / state are per line, only per record

so, I don't think you need to touch beforeLoad or old record at all. The way I've done it, and the way I believe MGBC was saying, is to just update the custom line field at the end of beforeSubmit every time you save. You can then check that field at the start of beforeSubmit and do your email logic.

Old:Ship != Ship is to identify if a change has been made, else exit

will ttyl about this if MGBC isn't back first. I think I understand better the requirements. I didn't realise that the workflow was changing the native shipdate, I thought it was the user/another automation

Appreciate it DBoT

that's brilliant

Thanks, will be a useful technique for many use cases ... ETA Updated is a real custom body field, was originally line, but didn't see a need (just yet).

Create a saved search showing the contacts assigned to the transactions Use NS_CONCAT to make them into one comma separated value Use that to source a non stored custom field on the SO Use that custom field as the recipients of your send email action

nice article, so recent too 😄

Legend @MGBC. Thanks so much!

Haha yeah I’ve been seeing a lot of this need lately so thought I’d throw some ideas out there on it. Hope it helps

@MGBC they're not ecstatic about the customer email appearing in the CC: line instead of the TO:, did you ever manage to come up with any workarounds?

@CraigR yes here is how you can workaround that. 1. When you get to this step in the Blog post make this field as an Email Address type field instead of long text. Also keep the Store Value box checked. Lastly do not set the sourcing from the summary search on this field just yet.

@MGBC my friend you are dead cert a legend! Worked a treat,thanks heaps!

wow, what an ingenious workaround. I'm floored

👍glad it helped....

@MGBC I have identified one flaw in the Saved Search I haven't resolved yet - if the Contact is attached to multiple Customers but the primary Company is not that of the Sales Order, it isn't picked up

instead of doing "Company" as the available filter, does it work if you instead use "Customer"?

Unfortunately not

got it

wow it works, great pickup Dave !!!!!

this is an issue that has eluded me before, so I'm very happy to have found it

@David B great call out. The filter does take a little playing around. Especially when it comes to customer/company/entity tables which are always confusing to work with

I do agree with DBoT, it is a great experience collab'ing with you guys, my sincere thanks for helping making me look good ;-)