New User: Field disappears from the Form view

Iโ€™m a new user to AppSheet so Iโ€™m still learning. This looks like a bug to me, but I suspect itโ€™s user-error (mine) โ€ฆ

Iโ€™ve got an app and I just noticed that in my Form View when I put in any values in certain fields, other fields that follow it are reset to blanks and the field actually disappears from the form view.

It should be noted that I had been experimenting with workflows and behaviors prior to this, but Iโ€™ve deleted those behaviors and workflows and the problem still exists. The possible bug would be that deleting a behavior or workflow doesnโ€™t fully delete it. But more likely, Iโ€™m just missing something.

Here are the fields involved and the order that are in the form:

  • When
  • Prty
  • List

Here are some examples of what happens in different scenarios:

  • If I put in a value in When , both Prty and List completely disappear from the form.
  • If I cancel the update and put a value into the Prty field, the List field disappears but When still shows.
  • If I cancel the update and put a value into the List field, When and Prty still show.
  • If I cancel the update and put a value into the List field and then put something into the Prty field, the List field disappears. If I look at the spreadsheet, the correct value is in the Prty field and List is blank.

I do not have any Show If specifications (they are all set to show) . I also do not have any Reset On Edits .

Any ideas on whatโ€™s happening and how I can debug this?

0 6 819
6 REPLIES 6

Steve
Platinum 4
Platinum 4

Are you using Valid If expressions?

If a Valid If expression is used to produce a dropdown menu, โ€ฆ

โ€ฆ but the expression itself produces an empty list, โ€ฆ

โ€ฆ any value already in that column will/may be removed. (I havenโ€™t yet figured when it gets removed and when it doesnโ€™t.)

If Valid If indicates there are no valid choices (that empty list) โ€ฆ

โ€ฆ and the column value is (or has become) blank, โ€ฆ

โ€ฆ AppSheet automatically hides the column, because why show a column the user canโ€™t enter a valid value into?

Thanks @Steve โ€ฆ Iโ€™ve checked my Valid If statements and they all have a valid expression thatโ€™s returning valid values.

Please contact support@appsheet.com for help with this, then.

@Steve โ€ฆ I finally figured out what was happening โ€ฆ the fields in question are defined like this:

  • When โ€ฆ Valid If = Lookups [When Lookup]
  • Prty โ€ฆ Valid If = Lookups [Prty Lookup]
  • List โ€ฆ Valid If = Lookups [List Lookup]

Here is the relevant fields from the Lookups table

  • Key โ€ฆ Initial Value = UniqueID()
  • Lookup Type โ€ฆ Type = text
  • Lookup Value โ€ฆ Type = text
  • List Lookup โ€ฆ Virtual Column โ€ฆ Type = text โ€ฆ App Formula = If ([Lookup Type] = โ€œListโ€, [Lookup Value], โ€œโ€)
  • When Lookup โ€ฆ Virtual Column โ€ฆ Type = text โ€ฆ App Formula = If ([Lookup Type] = โ€œWhenโ€, [Lookup Value], โ€œโ€)
  • Prty Lookup โ€ฆ Virtual Column โ€ฆ Type = text โ€ฆ App Formula = If ([Lookup Type] = โ€œPriorityโ€, [Lookup Value], โ€œโ€)

It turns out it thinks they are supposed to be a dependent dropdown when I donโ€™t want a dependent dropdown. I wonder if there is a way to tell it not to make it a dependent dropdown.

A dependent dropdown can be avoided by using a SELECT() or FILTER() expression rather than a table-column reference.

@Steve โ€ฆ The Select worked perfectly. THANK YOU!!

Top Labels in this Space