Dependent choice and invisible components

[Darren_Murphy]

@rleinen

I have two choice components. The choices of the 2nd one depends on the value of the 1st - using the filter setting (using the screen value of the 1st). Sometimes, but not always, the choices of the 2nd do not change when the 1st has been changed. And sometimes, when a default value of the 1st is set when the form opens, the 2nd choice component does not even appear.

Are you using Pages?
If so, could be related to the issue reported below…

PAGES: Collection items are not being filtered based on the "Screen" values

Describe the bug: Filter not working on Collection items when “Screen” values are used in the filter configuration How to replicate: *Let’s say you have 3 tabs. The first tab is Customers and 2nd one is Products that you sell. When you open the detail page of any item from Customers tab, then add a collection of Products, and set up the action when “Item clicked” to add a row to the 3rd tab which is basically a shopping cart, that contains columns: Products ROW ID, Customer email. Then in …

I believe a fix is on the way for that one.

@rleinen

Along those same lines, I’ve noticed that fields with no value do not even show up on some screens/forms, until a value has been entered for that field. Is that the intended approach?

Yes, that’s normal. If you prefer to have something always shown in the UI, what you can do is create an if-then-else column along the following lines:

• If value is empty, then “Not set”
• Else value

And then use that if-then-else column in your screen component.