Solved
Forum Discussion
db_pdx
2 years agoValued Contributor
Yup, I'm with you on that. I wonder if you could do the opposite. Remove the button from the SQL Table Editor, create a separate dashboard button that performs the save action, as well as, doing the refresh. Again, haven't tested it but feels like an avenue to explore.
RobbSalzmann
2 years agoValued Contributor II
Yup, thought about that too. Here's the catch: You have no reference to the SQLTableEditor in the UI, so no way to see what data the user just added to it prior to his clicking the external Save button, so we're stuck there too.
Related Content
- 2 years ago
- 2 years ago
- 4 years ago