is it possible to have a line item field value be ...
# suiteflow
b
is it possible to have a line item field value be set that isn't shown on the form? and then if so, reference it in workflow? I can test, just curious if anyone knew off hand. I'm trying to clean up our order forms a bit since we have so many column fields.
fwiw, doesn't look like it.
l
I think you can. Can you try removing the label of the item field from the form?
b
sure, so it "shows" but doesn't have a label?
l
This way, it would hide that Item field but still stores the values being assigned.
👍 1
b
that would be slick!
testing now
nice, that totally works! thanks much!
👍 1
l
Awesome!!! 👌
y
I think that your thread might be useful regards my previous question of: "Once applying workflow condition using custom field over a SO transaction, I have noticed that the custom field must be exposed in all the forms in order to execute the condition. I thought that changing the trigger from Before Record Submit to After Record Submit will solve this issue. Currently, the condition executes only when the field is exposed in the form. Does a hidden custom fields that is not shown on the form can be set by workflow?"
b
sounds like it. my use case was the field is marked to "show" on the form, but the label for said field was cleared to be blank. Because this is blank, doesn't show up (at least in column fields which was my use case) yet this field can be accessed for workflow logic.
y
I will check it in my hand as well. It sounds terrific!
Thanks @Ben Goligowski
l
Yep, so basically, setting native/custom line field to blank will make the field "not visible" but still accessible in background. Because if you untick the "show" in the form then it would completely remove that line field which cannot be used not only by the workflow but even the suitescripts.
👍 1
y
Great, what regards a custom body checkbox field over a transaction that used as a workflow condition. it should works as well as the line fields?
l
Yep! they should behave have the same.
y
at the line field it's really remove the column. but, at the body/header field as far as I see and checked it just remove the label.
BTW I thought to myself that once using After Record Submit trigger at workflow it should not cause an error due to a missing field at the specific form. it turns out that I was wrong.
l
Oh yeah, you're right @Yadigar, well I honestly used the hidding approach on the line level. 🙂 hehe! But you're correct. So we just have to use the checkbox to hide the header/body fields and it would still be available.
y
As far as I checked, if you unmarked the "show" field at the header level and your using it as a condition to trigger a WF, your WF won't be execute.
b
no it if it's not marked to "show" the workflow can't 'see' it.
y
Yeah, it's actually make sense. In any case I'm glad that I learned the new trick of removing the label from the line fields 😁