A Federal awards workbook has over 400 entries, and the user declared the same finding reference number (2023-001) for most of them, with one associated finding text. Our frontend logic interprets the count based on the number of declared findings, not the uniqueness of the finding reference number. This results in approximately 400 findings being counted instead of one. This is an edge case. The user has indeed declared multiple findings if we consider the uniqueness of findings based on the tuple (award reference and finding reference number). However, since all findings share the same reference number, it can also be interpreted as a single finding from a reporting perspective (if we count only the total of unique finding reference). This ticket is to identify and implement the appropriate solution to address this issue.
Description:
A Federal awards workbook has over 400 entries, and the user declared the same finding reference number (2023-001) for most of them, with one associated finding text. Our frontend logic interprets the count based on the number of declared findings, not the uniqueness of the finding reference number. This results in approximately 400 findings being counted instead of one. This is an edge case. The user has indeed declared multiple findings if we consider the uniqueness of findings based on the tuple (award reference and finding reference number). However, since all findings share the same reference number, it can also be interpreted as a single finding from a reporting perspective (if we count only the total of unique finding reference). This ticket is to identify and implement the appropriate solution to address this issue.
Associated ticket.