I’m new to Ignition and I’m trying to create a report using a SQL query. I verified that the query works using the Database Query Browser tool, but when I run the report, it will only ever display the first project returned from the database. Each project might have multiple rows. you can see in the image below that this particular project returned 3 rows in the “Details” Row.
There should, however, be more projects displayed.
I expect the report to continue with a new Detail row starting with a new “PSI Project #” followed by the respective details rows
You can see below my design configuration and a query I ran showing there are more rows not displayed on the report even though they are returned in SQL
I’d also like to add that you’ll notice that the 3 row of data returned in the “Query Details” row are all identical data, but in the actual SQL query these 3 rows have unique data. So for some reason it’s only displaying the row data for 1 row of SQL results 3 times.
Have you tried using a nested query? Perform a select statement to return the list of IDs you would use in place of your {WhereClause}. Then your nested query would perform your select statement for EACH of those IDs. Depending on how complex your final data is, you might also have to use TableGroups in the report designer. Sorry I don’t have a concrete example but this might get you going in the right direction.
I had the same problem today where only the first row from my data was being printed on the report but the raw xml file in the right panel in Preview mode showed all rows were being returned. I followed @PGriffith 's suggestion from Report not displaying row-0 - #5 by MC2338 and re-created the table. That fixed the problem for me. I did not re-create the table to be identical to the first one though.
Looking at the original post, it looks like similar to me he has two or more groups of data (Row and query) for just one query. I imagine somewhere in the design process manipulating grouped data causes a bug, and re-creating the table without all the trial-and-error steps that went into creating it foregoes triggering that bug.
