Hello, I have an After Field Edit action (no cond...
# suiteflow
s
Hello, I have an After Field Edit action (no conditions) that looks for changes to a custom long text field (notes), and appends the employee name to the end; however, I appear to be stuck in an infinite loop. Any suggestions for fixing this formula:
{custbody_notes}.concat('Test Name')
 (edited)
k
Ok - so if I'm guessing correctly - your goal here is to store within the field itself the last person to edit that field?
couldn't you create a separate field for storing that - and then on after field edit populate your seperate field
Your after field edit is infinite looping because the act of editing it - causes it to have another field change
until the workflow bombs out
s
Yes, and that makes sense. I will chart your suggested course.
@KevinJ of Kansas is it possible to inject the current user/employee into the "separate field" After Field edit action via formula?
{custbody_notes} + ' ' + {user}
I'm getting null.
k
why not just make your custom field an employee list - and then "current user" becomes an option
s
@KevinJ of Kansas Okay, I've sort of been tip toeing: The Long Text field is a Notes field that I need to include a user timestamp for after each edit to the note... Note 1 [Suite Deal - 7/12/21 @ 1:00p] Note 2 [KevinJ Of Kansas - 7/14/21 @ 1:01p]
Perhaps at this point, I should just jump into a workflow action script?
k
If you really need something that does exactly that (and I'd question the actual need for it)
I'd have a field: "New Note"
and a field: "Note History"
s
Yes, sir, been down that path - I'm just recreating behavior that already exists natively in NetSuite...LOl
k
my workflow would be a before submit - and it would say "hey new note field isn't empty - set note history field equal to:
{newnotefield} || ' ' || {userfields.name} || ' ' || {today} ||' '|| '{Note history field}
and then clear new note field after submit.
s
Done. I really appreciate your help.
k
of course -that's just a loose concept.
and you probably want carriage returns in there.
but realisitcally - it feels like you are using a body field when you really should be using LITERALLY the user notes functionality
which does ALL OF THE THINGS YOU ARE LOOKING FOR
haha
s
I'm just an order taker.
LOL
k
Right - either way - I've only provided a loose framework there - you'll have to fix all your field references appropriately