I am new to Application Studio and have a question regarding visibility.
I have created a new layer which has many fields–1 field is always visible (Master Display) and the others are not.
Each of the hidden fields have an event which checks if they should display.
When a user changes Master Display, the correct fields become visible.
When a user refreshes the page, or comes back to it later, the previously visible fields become invisible.
Technically, this is the correct behavior as the visibility is controlled from within the event which only runs when the DataTable Column is Changed.
The end goal is for the correct fields to display and remain visible even after a page refresh.
What is the best approach to handle this?
II suspect you’ll need to add the visibility check on an on-load event.
Do a trace via DevTools to see all the events called. Console you need to enable debug via Ctrl-Alt-8. You can also use the Kinetic UX Trace Utility from one of the EpiUsers founders
Not overly sure on your setup, but perhaps you could toggle the visibility of column bindings based on a datarule instead of an event.
You’d have to have them all visible by default… then…
Data Rule: if (Master Display) Value = value of “A”… columns X, Y, & Z SettingStyle.Invisible.
Data Rule: if (Master Display) Value = value of “B”… columns Z SettingStyle.Invisible (X & Y still visible)
The key here is… does the value of Master Display survive a refresh? Or does it reset as well?
I’ll look into Data Rules.
The value of Master Display, and all other custom fields, survive refreshes–their values get stored in UD fields/columns in the Parts table.
///
Data Rules appear to resolve this issue–I’ll get the logic swapped over and run some checks.