I have a content type of events, and a separate content type of competitions, and want to create a combined table of both, for which this seems perfect. They would have different columns of data, so for example an event might have 5 columns and a competition only 4, however was planning to use some JS and class names to implement a colspan to make it look good.
However I decided to start simple. With a view of events from 2024 and a view of events from 2023 being combined, just to check it works. However it didn't.
I had my view, and created a duplicate view page, and I called one combine master, and one combine slave.
so the URLs for them are: /admin/structure/views/view/fixtures/edit/page_1 and page_2 as they are within the same "displays" section
In the first page, I have the filter set to year 2024 and in the second page, changed it, "this page (override)" to be 2023.
Then in the first page, I added a field "combine view" and selected the second page.
So they are the same content type, same fields, just different filter criteria, so I thought they would definitely match up. However I get an SQL error
SELECT node_field_data.nid AS "nid",
NULL AS "node_field_data_created",
:view_fixtures_page_2_fixtures_page_2 AS "_view_id",
AS "_order_0" FROM "node_field_data" "node_field_data"
INNER JOIN "node__field_season" "node__field_season"...Maybe I am not using it correctly, however this appeared to be the simplest case I could try first.
Active
1.0
Miscellaneous