Duplicates on Table format view using pagination and sorting on a date field that has duplicate values for multiple rows

Hello, I had the same issue on an unformatted view, I don't think it is specific to the table format. Some entities showed up twice on page 1 and page 2 sort criteria are the same. I fixed it by adding sort on entity ID.

I also encounter this issue. My case is:

There are two different nodes (Node1 and Node2) which has a custom field 'Event date' of type Date range;
Thees nodes has the same value for 'Event date'; like

"field_event_date" => array:1 [▼
      "x-default" => array:1 [▼
        0 => array:2 [▼
          "value" => "2024-08-30T09:00:00"
          "end_value" => "2024-08-30T12:00:00"
        ]
      ]

The view has sorting by two criteria: 1) Content: Event date:end_value (asc); 2) Content: Event date (asc);
The view has a pagination;
There are some other nodes on the results: some of them before Node1 and Node2, some of them after;
When Node1 is the last node on the view page, then on the next page the same node is the first. Node2 is never shown;

This could be solved by adding an adding sort by entity ID

I have just run into this exact issue and it was driving me crazy. I thought it was the way I was rendering the View programmatically, but turns out the culprit was in the View itself.

I had the same symptoms as outlined in this issue, that when using pagination, some items were missing and some items were duplicated.

I had noticed that the content that was being queried in the View had 10 our of 15 of them had the exact same "Created/authored on" date timestamps. These same timestamps were throwing off the sort that was set, which was to sort them by the "Created/authored on" field.

The quick solution for us was to add a secondary sort to the View (Title ASC), so that if any of the items (10 in our case) has the same values, that the group of those items would then be sorted using the Title. This solved our issue.

The other option, that we didn't go down, was to manually or programmatically update these nodes to adjust their "Created/authored on" date timestamps so the sort and pagination could work as expected.

Just in case this helps anyone else in a similar situation.