cancel
Showing results for 
Search instead for 
Did you mean: 
Workflow Hero

Hide an exsiting field, on a new form, based on a previous selection

I have 12 "yes/no" fields that are "available slots."  Once a person selects a "slot,"  I would like the "slot" that was selected not to display anymore on subsequent new items/forms.  I know how to hide directly on the form but this is more along the lines of hiding or disabling a field that someone else has selected.

Anyone have any thoughts or ideas for the most efficient way to achieve this?

0 Kudos
Reply
12 Replies
Workflow Hero

Re: Hide an exsiting field, on a new form, based on a previous selection

Use a calculated value for each slot with formula like

Lookup("List Name","Slot field Name","Value if True", "Any Field Name")

and then add a formula to each slot so if its related calculated value is empty, hide it.

BR,

Accept as Solution Reply
Workflow Hero

Re: Hide an exsiting field, on a new form, based on a previous selection

I'm testing it today.  Will let you know how I make out.

0 Kudos
Accept as Solution Reply
Workflow Hero

Re: Hide an exsiting field, on a new form, based on a previous selection

I'm having trouble with the 4th parameter (output) in the string.  I'm selecting one of my fields/columns, that is a "single line of text" field, called "outcome," but I am not getting the results that I would have expected.

LookUpFormula

LookUpFormula1

LookUpFormula2

0 Kudos
Accept as Solution Reply
Workflow Hero

Re: Hide an exsiting field, on a new form, based on a previous selection

Did you try replacing Outcome with "outcome".

If yes and still doesn't work, please send me a screen shot of the browser dev console error since it's a REST call.

BR,

0 Kudos
Accept as Solution Reply
Workflow Hero

Re: Hide an exsiting field, on a new form, based on a previous selection

Hi Phillip,

Here is the formula:

lookup(List Name,Oct2018Slot2,"Yes","Outcome")

This is what it looks like before its checked:

LookUpFormula4

This is what it looks like when I check the box:

LookUpFormula5

Nothing on the console until after I uncheck the box and then this is what appears:

[Department Sites-d1ce0353-c428-411f-86f9-1b6c308fb03e] - Lookup runtime function is missing valid parameters. Check that the list name, filter column, filter value and return column are specified in the function. Parameters - list: Department Sites, filter column: false, filter value: Yes, return column: NWF.FormFiller.Functions.GetTypedValue('','Text')

0 Kudos
Accept as Solution Reply
Workflow Hero

Re: Hide an exsiting field, on a new form, based on a previous selection

Please try to remove the double quotes from  Outcome so it looks like:

lookup(List Name,Oct2018Slot2,"Yes",Outcome)

0 Kudos
Accept as Solution Reply
Workflow Hero

Re: Hide an exsiting field, on a new form, based on a previous selection

Hi Philip,

Thank you for your continued help with this.

I removed the qoutes and now, whether or not the box is checked, the field is not calculating at all:

LookUpFormula6

and here is the message from the console:

[Department Sites-54ab11ff-f52a-410a-b2bc-29dbfe79986d] - Lookup runtime function is missing valid parameters. Check that the list name, filter column, filter value and return column are specified in the function. Parameters - list: Bank Notes Department Sites, filter column: true, filter value: Yes, return column:

0 Kudos
Accept as Solution Reply
Workflow Hero

Re: Hide an exsiting field, on a new form, based on a previous selection

Just to make sure - "Oct2018Slot2" and "Outcome" are variables on the form containing the actual column names? I'm asking because they are look like references in the formula, but the formula actually expectes the names of the column(s).

0 Kudos
Accept as Solution Reply
Workflow Hero

Re: Hide an exsiting field, on a new form, based on a previous selection

I used the "Named Controls" fields rather than the "Item Properties."  I'll try using the "Item Property" fields since those fields are the actual column names.

0 Kudos
Accept as Solution Reply