SDK event hooks to move data point in table up or down

Hello, I was wondering if there were any tricks anyone knew to move the data point selection for the table visual up or down?
The use case is , we have a table and a fly out and want to move to the next and preview record keeping the fly out open, and have the data update based on the datapoint selected.

thanks for any tips

Hello @halirob

I have never tried this but I don’t believe there is a way to specifically cycle through rows of a table in your fly out.

How are you setting this up now?

We are using the data point click event in the table to fly over a panel. We’d like to navigate back and forth in the table, which would trigger another datapoint click event updating the panel. We can manually do it with mouse or keyboard nav, but we’d like a next and previous button on our panel that the user could use to move up and down instead.

Hello @halirob

I’m sorry about the late reply.

I wasn’t able to find anything specific to pull a next/previous button. If I understand what you want correctly, you will just need to create a UI element that will trigger the parameter action that you are using to pull up the data from your table.

That is a good idea. Is it actually possible to trigger another parameter to update from different parameter?

Lets say I have a table with columns: sequence number, id, name.

I setup a parameter for currentSeqNum and CurId .. User clicks on a row, I set those 2 params to the row values via an action.

My flyout screen pops up with the details for the deleted id.
Now I want to go to the next row without closing my popup.
I can update the currentSeqNum to currentSeqNum +1 or currentSeqNum -1, but how do i trigger the CurId to update based on that?

thanks for an ideas…this could be pretty cool if it worked..

Hey @halirob

I looked into this more, and if I understood the documentation I think this could help:

Probably adding these columns to your dataset cloud help:

  • PrevId,
  • NextId,
  • PrevSeqNum,
  • NextSeqNum
    2 buttons could be implemented as 2 visuals with only current row shown (actually that data will be hidden and only hardcoded columns with values “Next” or “Prev” should be visible). They should assign proper pair of values to your parameters on click.

I think i see what you are saying.. if the row has the previd and nextid.. then the outside UI would know the IDs.. then on top of that.. we can even use a selected state (using a paramter) to indicate when it moves to the next one from the outside app

Yes, something like this. Window functions can easily get these next/prev values (in SQL or in QuickSight datasets or in calculated fields). Just in case, here is a very simple example from my experience:

I have a dataset with months. I have columns

  • Month
  • Next Month
  • Prev Month
  • Prev Year Month (-12 months from the current month)
    Only Month is visible. When a user clicks a row I set 4 parameters that I need to filter/calculate data. It allows me to streamline many filters and calculated fields.