I stucked with a report trying to set the correct start expression. I have a main “Log” table which contains working hours by employees. I want to generate a report listing all logs for a particular period.
In order to do so, I created a “report request” table. A report request contains Start date and End date columns.
I added 2 virtual columns [corresponding logs] and [corresponding employees] with an expression to select rows from the “Log” table that fit the desired report period. The list is correct :
each refer to the log table, but return lists of different column values: ID and Employee. A table can only have one key column, so one of those expressions is not returning a list of key column values.
OK thanks. Understood. I’ll keep the 1st one returning keys from the log table.
In my report I still need to group corresponding logs by Employee (which is a column of the log table) and sorted by date (also a column of the log table). I don’t get the mecanism to do it. Is that possible ? Like :
For the list of corresponding logs
Employee 1
Log 1 1st september
Log 2 2nd september
…
Employee 2
Log 1 1st september
Log 2 2nd september
…
Back-references within nested queries ([_THISROW-n]) Consider a complex App formula with “nested” SELECT() expressions (SELECT() expressions within SELECT() expressions): SELECT( table[column1], … SELECT( table[column2], … SELECT( table[column3], … ) … ) … ) Let’s call the row for which this entire expression is evaluated as its App formula the Origin Row. Within this entire expression, we can refer to column values of the Origin Row by dere…
I got the point about comparing logs with logs within a single start expression. The corresponding employee expression returning one unique log key for each employee.
The report arrives but still something wrong even if both formula selection formula look fine.