Memory Tags and Custom Session Props

Ignition
5

I would handle this by making custom props on the view which run the Queries.

Then I would use an expression binding on the data prop of the table to select the data to display.

something like:

case(
    {selectedLineDropDown.props.value},
    1, line1TblData,
    2, line2TblData,
    3, line3TbleDAta,
    null
)

Personally, I avoid session props, unless the data changes infrequently and is truley needed across multiple views.

Some good reading on these here, really the wole post is a good read if you're just staring with Ignition Perspective, this just links to where the conversation turns to custom session props.