Hi Team,
"I’m facing a challenge with displaying and making interactive multiple ticket IDs that exist within a single cell in QuickSight. Here’s my specific use case:
Current Data Structure:
id
Column 2
Multi-ids
Column 4
123-456
abcd
1112-76,234-56
aaa,bcb
567-789
fefgdhh
234-678
www
234-564
gegeg
2122-56
hifhfh
2122-5656,12-345,789-10,678-23
eee,ttt,uuu,lkl
What I’ve tried so far:
Cell-level URL actions
Issue: Entire cell becomes one clickable link
Cannot distinguish between individual IDs within the cell
Displaying formatted URLs in cells
Issue: Poor visual experience
No individual click functionality
Forces users to manually copy-paste
Custom action buttons - expand/collapse
Issue: Cannot parse comma-separated values within a single cell
Unable to implement selective actions for individual IDs
Desired Functionality:
Clean, user-friendly visualization of multiple IDs
Efficient navigation to individual ticket details
Ability for users to select/click individual ticket IDs within a cell
Is there a recommended approach or workaround in QuickSight to handle this kind of data structure while maintaining good user experience? Are there any alternative visualization patterns that could better serve this use case?
Hi @avanni ,
Thanks for reaching out, You can refer below link and check the solutions:
Alternatively, You will need to perform this transformation in another tool. Take a look at AWS Glue Databrew or AWS Glue Studio if you cannot use custom SQL for it.
Thank you for the suggestion. I understand the approach of splitting the comma-separated values before the data reaches QuickSight. However, I have a specific concern:
This transformation would result in row duplication in the QuickSight analysis, as each comma-separated ticket ID would create a new row from the original record. For example:
Original row:
id ticket_ids
case-1 ticket-123,ticket-456,ticket-789
Would become:
id ticket_id
case-1 ticket-123
case-1 ticket-456
case-1 ticket-789
This row multiplication could potentially:
Impact our analysis accuracy
Affect aggregations and metrics
Create confusion in other visualizations
Is there perhaps a way to achieve the individual ticket ID functionality while maintaining the original data granularity?"
I’ve had to deal with an issue around comma separated lists in QuickSight and ultimately the best way I found to deal with it was to create a new dataset with the list broken out using SQL.
I used both datasets in my analysis. One dataset would manage the rolled up (comma separated lists) and the other was for drill downs on a specific id. This was not the ideal solution because it did add more development work but it was the most workable.
I will mark this topic as a feature request for the QuickSight team to add functionality around comma separated lists.