Hello! I made a custom transaction field and i pla...
# suiteflow
k
Hello! I made a custom transaction field and i plan to store the internal id of the transaction record there after it is saved. But it seems I can't find the current record's internal id in the set field value work action. Is there a way to do that? I was thinking maybe through formula but I don't know the correct syntax.
k
Why do you need it in a custom field?
k
This is actually part if a JE approval workflow and I added a button to edit an approved JE. I was planning on using a Go to Record workflow action to go into the same record in edit mode. I don't know if it makes sense. I'm new to workflows to my ideas may be weird :))
a
try
{id}
k
If you have a lock record action in place that you are trying to bypass, that's not actually the way to do it
in this case - you probably want a button to push it to another state that doesn't have the lock record, and then when they edit it - have it go back to the lock state
or you could have the button set a field value that is set as an exception to the lock record and another action aftersubmit to uncheck the box.
(depending on if you want the JE to require approval again)
k
Awesome, {id} worked!
@KevinJ of Kansas yours worked it too, but i don't think it's possible to go directly in edit mode. So it's a 2 step process: click button to go to a state, then choose edit. What I did was when the button is clicked, it goes to a state which has Go to Record action in edit mode, so 1 step and I'm in edit mode. Works almost perfectly, just 1 issue: when the user cancels the edit, it takes forever to load what happens.
k
I'd rather have a 2 step process for this requirement anyways.
One to put it back into the pending approval queue, and another to initiate edit/save/resubmit.
Otherwise - I'd just set my lock record condition to not occur on the roles that are allowed to edit approved JEs
and just warn the user that the JE was approved via popup when they load the page
k
@KevinJ of Kansas Actually I might just do what since when loading a Go to Record action in edit form, and if the User clicks the cancel button, the page just hangs or takes forever. Yup, 2 step process should be better than a buggy 1 step process :))
k
Right.
k
Also, it's not actually the workflow locking the JE, it's Netsuite standard behavior to make the JE uneditable after being approved if the user's role only has Make JE permission and not Journal Approval permission. If both permissions are present, then there's no problem at all, an edit button will be on the record on standard.
k
Ah. I always have more complex requirements that make using the native version of approvals not work.
So I normally have a multi-stage workflow and the approval routings checkbox marked
k
Yup, most clients prefer that. Though that behavior I described holds true even with a workflow and a custom approval routing.