I'm working on building a table (v2) with 3 custom columns -> two dropdown menu columns implemented as single-select tags (let's call these c1
and c2
), and one dropdown menu column implemented as multi-select tags (let's call this c3
).
The option list for c2
depends on what value is selected in c1
.
The option list for c3
depends on what value is selected in c2
.
I have gotten the option lists to value correctly, and selection works as well:
However, I am facing issues in display when the selected value in c1
changes.
When c1
, c2
, and c3
have all been selected with values v1a
, v2
and v3
respectively, and the value of c1
changes from v1a
to v1b
, c2
resets to be unselected but c3
doesn't reset as expected. Instead, the existing selected value labels are replaced with their respective underlying IDs:
Additionally, if v1b
is changed back to v1a
(i.e. v1a
is selected again), the value of c2
reverts to v2
instead of staying unselected. (At this point, c3
still displays the v3
IDs and not their labels instead of resetting to unselected):
My questions:
- Why isn't
c3
resetting to unselected when the value ofc1
changes? I also added logic to modify the table's changeset to set the value ofc3
to[]
ornull
, but that doesn't update the UI of the table. - Why does re-selecting old values (i.e.:
v1b
tov1a
) persist the old selections forc2
andc3
, even though I am not saving changes to the table? It seems as if the changeset is maintaining its own memory state / cache, and I'm not sure where this is coming from.