You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an error has affected fields in multiple files/table the error description seems to repeat in the list for each affected file rather than once for "the error".
Although a simple "distinct errors" filter might seem an easy solution here, I would argue that where an error does legitimately occur multiple times (e.g. across several distinct episodes rather than one episode and an inter-related file) it would be useful to repeat the error description for each instance of the error (so the user knows to look for/resolve more than one).
Would it be possible to work out the distinct number of errors by calculating something like count(rows in error across all files/tables) / count(files/table with affected fields) ?
Athough that assumes duplication is always a one-to-one relationship between rows in different files.. which probably isn't true!
The text was updated successfully, but these errors were encountered:
When an error has affected fields in multiple files/table the error description seems to repeat in the list for each affected file rather than once for "the error".
Although a simple "distinct errors" filter might seem an easy solution here, I would argue that where an error does legitimately occur multiple times (e.g. across several distinct episodes rather than one episode and an inter-related file) it would be useful to repeat the error description for each instance of the error (so the user knows to look for/resolve more than one).
Would it be possible to work out the distinct number of errors by calculating something like
count(rows in error across all files/tables) / count(files/table with affected fields)
?Athough that assumes duplication is always a one-to-one relationship between rows in different files.. which probably isn't true!
The text was updated successfully, but these errors were encountered: