Forum Discussion

RobbSalzmann's avatar
RobbSalzmann
Valued Contributor II
2 years ago
Solved

How To Trigger Dashboard Refresh from SQLTableEditor Save Data Server Task (Save button)

The SQLTableEditor in question is used for user interactive CRUD pertaining to Rates used in a calculation. Use Case: I have a SQLTableEditor that holds rates.  When the table Save button is clic...
User Interface
  • RobbSalzmann's avatar
    RobbSalzmann
    2 years ago

    Thanks db_pdx 

     I do have an extra button to refresh my table.  This extra button confusing to the users.  Its not a natural UX action to click a Save button and then have to click an update button.  Save should do the updating.  The point of this is I should not need an extra button to refresh the ui after clicking a save button.  

RobbSalzmann's avatar
RobbSalzmann
Valued Contributor II
2 years ago

Same here, bummer.  I had hope for minute there ... ðŸ˜†

The problem is the TaksResult objects.  The XFSqlTableEditorSaveDataTaskResultTaskResult lacks these two properties needed for this to work:
XFSelectionChangedUIActionInfo? ModifiedSelectionChangedUIActionInfo { get; set; }
bool ChangeSelectionChangedNavigationInDashboard { get; set; }

The SQLTableEditor seems to be a one-off component in dashboards, like a brother from another mother.  It also uses a different TaskResult type than everything else.

db_pdx's avatar
db_pdx
Valued Contributor
2 years ago

Its not your exact requirement but... what about putting that first table in a pop-up dialog box via a button?  That way when you close the dialog you can have it trigger a refresh as buttons have 'Open Dialog, Apply Changes, and Refresh' as an option.

  • RobbSalzmann's avatar
    RobbSalzmann
    Valued Contributor II
    2 years ago

    Thanks db_pdx 

     I do have an extra button to refresh my table.  This extra button confusing to the users.  Its not a natural UX action to click a Save button and then have to click an update button.  Save should do the updating.  The point of this is I should not need an extra button to refresh the ui after clicking a save button.  

    • db_pdx's avatar
      db_pdx
      Valued Contributor
      2 years ago

      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's avatar
        RobbSalzmann
        Valued Contributor II
        2 years ago

        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.