Changing the structure of the visual type “Table”

Hello Team,

I have recently been tasked with providing daily data in the following form:


Each header is a field name from my database.

I have decided to use the visual type “Table”
And the result is something like this.

And that’s not really what it’s about.
Is it possible to make the organization as a table as required by the customer? Here I mean without repeating the merchant name/data.

Thank you Team.

Hello @weird_guy

Are you doing any filtering or sorting on the table?

For example, I made a dataset to show how it would pull into QuickSight (this is a CSV):
Original Dataset

QuickSight Table

1 Like

Hello @duncan

Thank you for your response.

Yes I do some filtering or sorting on the table.


So, the basic idea is to import the structure from a ready-made CSV file into QuickSight?
But how to combine it with another Dataset?

Hey @weird_guy

It’s possible that your filtering is affecting the end results so that you lose the blank cells. You can also tell filters to “include null values”.

You can perform joins in QuickSight during the data prep stage:

1 Like

@duncan Hello

One more thing.
How you did the “Table” like this in QuickSight without repeated client name and so on.

@duncan
p.s.: Perhaps Ive misspoken. But what I meant was that I want to leave the name of a particular merchant only in the first column. Its much clearer and prettier than repeating the merchant name in every column.

Hey @weird_guy

I see what you mean now. You only want Merchant 1 to appear once in the table with all rows associated with it to the right descending until the next merchant.

There’s no way to do this in the UI but you could try making a calculated field. You could rank the values in merchant_name(grouped by each merchant name) by histroy_creation_date. Then using an ifelse function, anywhere that rank <> 1 then ’ ’ (empty string).

This would be very hacky and not something I would recommend doing. The easier way to do this would probably be moving to a pivot table. It would be a different layout but closer to your end goal.