@jacobstern @Tess I have partially succeeded in getting the option list within a tag or avatar column type to populate with differing option specific to currentSourceRow. It does not work well though. What I did was have the options list reference a master array of all possible values that is not part of currentSourceRow but I include a .filter() and filter out the values from the array that are not included in the array that is on currentSourceRow. It sort of works but the values do not show up right away. I have to mouse over the table, sometimes clicking on the table and then clicking somewhere else to get the options list to generate within the table. Before that, the column values act as though there value is not matching anything in the options list, like the list has rendered in as an empty array. See the little .gif. As you see, when the values come is, I have not done anything other than mouse over the table. Before I mouse over the table, I had let the table sit for minutes without touching anything to be sure the issue was not just some sort of lagging loadin or something.
The two columns seen here called catalog and category are also option lists but the are both referencing an array that is outside the scope of currentSourceRow. Because the supplier column is making use of currentSourceRow, these two column are also suffering from this loadin problem. When the suppliers column is not referencing currentSourceRow, both catalog and category columns have no issue rendering quickly.
I know its great when people can supply a json export for trouble shooting but in this case, this issue is completely reproduceable and the steps are rather simple. They are as simple as just assigning an option list within a tag, tags or avatar table column to reference an array that exists on the currentSourceRow. The testing developer will immediately see the options list not responding as expected after refreshing the app page. What the tester will see, is the behavior working as expected before refreshing the app page. Upon initially setting the options list to reference currentSourceRow, everything works fine. Its only after loading in a new instance of the app that things go wonky. Let me know if there is anything else you need from me to pin point this bug other than having me create a completely new app on my time referencing static values. I would be quite willing to examine an app a tester creates and make some adjustments to it to reproduce the bug if needed.