In our current table displaying all clusters in a model, we have both list view and details view. We also allow the user to click on an arrow on the row when they want to see the full view of that particular cluster. However, this can be confusing when the user is in the details view page because the arrows make the users assume that when they click on another row's arrow, they would see that rows detail page (we've seen this error in usability testing). Below I have displayed where the arrow button is positioned. * and y represent buttons to click list view and details view.
Currently, one of our solutions is to remove the button when they are on details view and have a seperate button which says "go to page" on the details section. However, this means we'll have two different tables when the front end is designing it. Which is extra work for them. Does anyone have any solutions on how else we could approach this? Thank you!