Thanks @MiguelOrtiz
Your guidance was very helpful.
I finally got it all to work, but as is the case with programming many times, I then questioned the path I was on. I realized that this rabbit trail would keep getting longer, for example, what if a user selects a tag/drop down, then wants to back out of change… etc. All stuff that can be dealt with, but I finally backed up and went a simpler route.
I’m allowing my users to do inline editing on certain fields, but if the column value is tied to a specific tag, I pop up a modal and control it there. Ie if the tag is the partID and they try to change description. The end UI turned out clean by adding an event to the description field. I am also then using the modal for double duty and making it my add a part form.
If I end up needing a table that they can truly do what I started this thread with, I may just do something purpose built for my data in react and then make it a custom component.
Until then, trying not to swim upstream and use the UI methodology Retool has designed the IDE around.
It is an amazing product. All have short comings, but they seem to be pouring effort into it, utilize developer feedback and importantly for me, it’s very fast at api calls to sql servers hosted on AWS.
Thanks again,
Wayne